nsys-ds41: self-test stub tree omits gate-bound.sh
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- shell
- Domain
- testing-qa, tooling
Research direction
Inspect the self-test that builds the temporary tree and the startup sourcing in tools/ref/nsys-ds41.sh; the missing entry point is tools/gate-bound.sh. Copy that file into the stub tree's tools directory before invoking the runner, then rerun the self-test and confirm the ok, cap, gone, and journal cases reach their expected exit codes.
Written by the indexing model from the issue text.
Description
The self-test copies nsys-ds41.sh into a temporary tree without tools/gate-bound.sh. The copied runner sources that file at startup and exits 70 before any two-card check runs. The ok, cap, gone and journal cases expect exit codes 42, 78, 69 and 69, so all four fail before reaching their intended paths. Copy tools/gate-bound.sh into the stub tree's tools directory before invoking the runner, then rerun the self-test.
Evidence (at the base of #465):
Filed by Shingler, the review bot, while reviewing #465; the defect is outside that pull request.
- Dominant language
- Rust
- Stars
- 21
- Forks
- 4
- Avg merge
- 2h 31m
- Merged PRs (30d)
- 828
Getting set up
- No 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 midagedev/bloomery
-
good first issue hardware help wanted no-box serve
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
good first issue hardware help wanted no-box
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
midagedev/bloomery#863 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 10/100
midagedev/bloomery#1165 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
midagedev/bloomery#1163 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
midagedev/bloomery#1162 · 8 comments ·
Maintainers usually reply within 1 day
All issues in midagedev/bloomery
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
pop-os/cosmic-applets#1619 ·
Maintainers usually reply within 3 days
-
binding:python bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
coollabsio/orbit#72 ·
Maintainers usually reply within 1 day
-
swc_common: Mark::least_ancestor never returns when the answer is the root mark (ANT-2026-JYDQGGRT)Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
swc-project/swc-ai-issues#137 ·
-
Synth suite fails unless run from the repo root: signal_flow's default machine path is cwd-relativeOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Nimblesite/osprey#370 ·
Maintainers usually reply within 1 day