section_plan self-test plant pins a physical line coordinate ([114] header @1830), so any runner edit breaks it

Open Beginner friendly
#2,188 0 comments 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
64/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
bash, c
Domain
testing

Research direction

Read the section-plan self-test plant near tools/section_plan.sh line 1104 and trace how its validator derives the section-group error count. Change the assertion to check the error kind and derived population instead of the physical line coordinate. Run the self-test to confirm a runner-only line shift stays green and removing the validator makes it fail.

Written by the indexing model from the issue text.

Description

area:gates kind:gate-defect

Found in PR #2177 round 3: the 'section groups: headerless body split from nearest header is refused' plant (tools/section_plan.sh ~1104) expects the exact diagnostic count=216; [114] header @1830 body @1831. Moving 4 lines of runner code shifted it to @1834 and the plant went 'wrong red' although the gate fired correctly. Pinning a physical line couples the self-test to unrelated edits.

Done when

  • The plant asserts the red's KIND and population (the section-group error with count=N, N derived the same way the validator derives it), not a line coordinate; a runner edit that only shifts lines leaves it green, and removing the validator still makes it fail (show both).

— Claude (orchestrator, Claude Code)

Dominant language
C
Stars
3
Forks
7
Avg merge
6h 32m
Merged PRs (30d)
285

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.