section_plan --print-weights accepts a runner with zero section labels (label floor collapses to 0)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- shell
- Domain
- testing-qa, tooling
Research direction
Start with tools/section_plan.sh and run the supplied Python reproduction to confirm the zero-label case. Inspect the script's --print-weights and --selftest paths; done means a zero-label runner or log below the fixed floor returns rc 1 with "vacuous", and a selftest covers the zero-label runner.
Written by the indexing model from the issue text.
Description
Found by a blind critic on PR #1310. The same result on main 7706607: this is pre-existing.
tools/section_plan.sh --print-weights derives its distinct-label floor from the runner. When the runner has zero section labels, the threshold collapses to zero. A fabricated 50-row timing log is then accepted, and a weights table is emitted for a runner with nothing in it.
Repro: python3 /tmp/sp-critic/repro_vacuity.py tools/section_plan.sh (rc 0 on head and on base).
Done when:
-
--print-weightsrefuses (rc 1, "vacuous") when the runner yields zero labels, or when the log matches fewer than a fixed floor of the runner's labels - a
--selftestcase plants the zero-label runner and names this check
- Dominant language
- C
- Stars
- 3
- Forks
- 7
- Avg merge
- 3h 56m
- Merged PRs (30d)
- 102
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from InauguralSystems/EigenScript
-
area:lint-tooling bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
InauguralSystems/EigenScript#1340 ·
Maintainers usually reply within 1 day
-
area:stdlib found-by:code-review kind:silent-wrong
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
InauguralSystems/EigenScript#1338 ·
Maintainers usually reply within 1 day
-
area:lint-tooling found-by:critic kind:docs-drift
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
InauguralSystems/EigenScript#1335 ·
Maintainers usually reply within 1 day
-
area:ci found-by:critic kind:gate-defect
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
InauguralSystems/EigenScript#1311 ·
Maintainers usually reply within 1 day
-
enrolment: decide test_gc_runner_controls.py (exempt vs enrol) and whether floors need a ratchetOpenarea:gates found-by:critic kind:decision
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
InauguralSystems/EigenScript#1280 · 1 comment ·
Maintainers usually reply within 1 day
All issues in InauguralSystems/EigenScript
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
johnsonjh/emu2-cpm86#68 · 1 comment ·
Maintainers usually reply within 1 day
-
Zenmap CrashOpenZenmap
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
fastfetch-cli/fastfetch#2619 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Template: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
betaflight/betaflight#15759 ·
Maintainers usually reply within 1 day