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

enrolment: decide test_gc_runner_controls.py (exempt vs enrol) and whether floors need a ratchet

Open Beginner friendly
#1,280 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
testing

Research direction

Read tests/GC_TRAVERSAL.md to understand the purpose of test_gc_runner_controls.py. Examine tests/enrolment_exemptions.txt and the test file itself. For the floors, look at the relevant test sections that track child-script sites and docs-claims populations to see how slack is printed. Decide on enrolling the test or keeping the exemption, and whether to add a periodic floor-raising step.

Written by the indexing model from the issue text.

Description

area:gates found-by:critic kind:decision

Two small decisions left out of #1264 (PR-B):

  1. tests/test_gc_runner_controls.py is run by nothing in CI. It is a manual control described in tests/GC_TRAVERSAL.md, and is currently the only entry in tests/enrolment_exemptions.txt. Either enrol it as a suite section, or keep the exemption with its reason.
  2. The floors that replaced exact counts (child-script sites, docs-claims populations) have no ratchet, so they can drift far below the live count as the suite grows. Slack is printed on every pass line. Decide whether a periodic "raise floors to live minus a margin" step is worth it; it is not a gate.
Dominant language
C
Stars
3
Forks
7
Avg merge
3h 58m
Merged PRs (30d)
105

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 InauguralSystems/EigenScript

All issues in InauguralSystems/EigenScript

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.