check-authoring-no-io.sh ignores CARGO_TARGET_DIR
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 86/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- build-system
Research direction
Start with products/evidence/scripts/check-authoring-no-io.sh, especially the target lookups at lines 187 and 198. Run the gate with CARGO_TARGET_DIR set, then verify the target directory is resolved via that variable, cargo metadata, or the target fallback without relying on a symlink; check the registry-evidencectl production_build tests afterward.
Written by the indexing model from the issue text.
Description
products/evidence/scripts/check-authoring-no-io.sh looks for compiled rhai under $repository_root/target/debug/deps, at lines 187 and 198. When CARGO_TARGET_DIR points elsewhere, as it does in the agent worktrees on /Volumes/CodexWorktrees, the gate refuses with "No compiled rhai was found under target/debug/deps".
The workaround is a target symlink. That breaks registry-evidencectl's production_build tests: they create tempdirs under <workspace>/target, and 17 of them fail with evidence.package.failed.
Done when: the gate resolves the target directory from CARGO_TARGET_DIR, or from cargo metadata --format-version 1 | jq -r .target_directory, and falls back to target.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- Avg merge
- 7h 22m
- Merged PRs (30d)
- 213
Getting set up
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 registrystack/registry-stack
-
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
registrystack/registry-stack#1748 ·
Maintainers usually reply within 1 day
-
area:casework bug criticality:p3 triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
registrystack/registry-stack#1729 ·
Maintainers usually reply within 1 day
-
area:breg bug criticality:p3 triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
registrystack/registry-stack#1682 ·
Maintainers usually reply within 1 day
-
area:casework bug criticality:p3 triage:needs-implementation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
registrystack/registry-stack#1669 ·
Maintainers usually reply within 1 day
-
agent-ready area:platform criticality:p3 documentation triage:needs-implementation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
registrystack/registry-stack#1639 ·
Maintainers usually reply within 1 day
All issues in registrystack/registry-stack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
software-challenge/player_rust#22 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
foundry-rs/foundry#17175 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
state:triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
github/copilot-sdk#2793 ·
Maintainers usually reply within 1 day