fix(evidencectl): doctor accepts a relative audit.path that evidence rejects
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
Research direction
Start in crates/registry-evidencectl/src/doctor.rs and read the committed test doctor_passes_a_relative_audit_path_from_the_default_current_directory_project. Run the declared audit.path through shared runtime validation before filesystem inspection, while retaining the resolved path for inspection. Update the test to expect validation refusal, then run the relevant test.
Written by the indexing model from the issue text.
Description
Raised in review of #1560 (crates/registry-evidencectl/src/doctor.rs).
evidencectl doctor resolves a relative audit.path against the project directory before checking it, so the audit check passes, while RuntimeAuditConfig::validate requires the declared value to be absolute and evidence check and serve refuse the same runtime file. The committed test doctor_passes_a_relative_audit_path_from_the_default_current_directory_project encodes the mismatch.
Fix: run the declared path through the shared runtime validation first and report its refusal; use the resolved path only for the filesystem inspection. Update that test to expect the refusal.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- Avg merge
- 5h 13m
- Merged PRs (30d)
- 176
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
-
area:casework bug criticality:p3 triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
registrystack/registry-stack#1623 ·
Maintainers usually reply within 1 day
-
area:docs area:render bug criticality:p3 triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
registrystack/registry-stack#1618 ·
Maintainers usually reply within 1 day
-
agent-ready area:platform bug criticality:p3 rust triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
registrystack/registry-stack#1583 · 1 comment ·
Maintainers usually reply within 1 day
-
docs(breg): configure/breg.mdx lists stages for a request_lifecycle when, which bregctl refusesOpenagent-ready area:breg area:docs criticality:p3 documentation triage:needs-implementation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
registrystack/registry-stack#1574 ·
Maintainers usually reply within 1 day
-
area:docs area:release criticality:p2 documentation triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
registrystack/registry-stack#1474 ·
Maintainers usually reply within 1 day
All issues in registrystack/registry-stack
Similar issues
-
`categorize_command` has no `uv` arm, so every `rtk uv …` row counts as `other` in the ecosystem mixOpenarea:api bug good first issue priority:low
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
area/cli kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
good first issue open-endedness: low type: new feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100