Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Make some of the longer-running code void R_CheckUserInterrupt-ible?

Open
#91 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
c, r
Domain
backend

Research direction

Start in src/access.c at addEdges(), using the linked reference around line 574, and inspect the main loop and other functions that may process long inputs. Review how R_CheckUserInterrupt() is used, then add periodic checks such as every thousand iterations where appropriate. Done means long-running operations can be interrupted without changing their intended results.

Written by the indexing model from the issue text.

Description

For example, in addEdges(), the main loop

https://github.com/statnet/network/blame/769972a6d377e608143d8a05a3df8d6bb3de56be/src/access.c#L574

could call R_CheckUserInterrupt(); every thousand (?) iterations. It's similar with other functions that might take long inputs.

Dominant language
R
Stars
20
Forks
7
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from statnet/network

All issues in statnet/network

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.