evidencectl doctor: opaque error for a relative --runtime-config path
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Start in crates/registry-evidencectl/src/doctor.rs around line 875, where relative --runtime-config path handling is documented. Reproduce the doctor command with the relative and absolute runtime.yaml paths, then verify that the relative form resolves or is accepted and exposes the underlying configuration problem instead of returning the opaque failure message.
Written by the indexing model from the issue text.
Description
Running evidencectl doctor --runtime-config hosts/staging/candidate-1/runtime.yaml (a relative
path) gives error[evidence.doctor.failed] ... Evidence could not inspect the selected runtime configuration. Running the identical check with the absolute path reveals the real cause (in this
repro, a TLS CA bundle file that was writable, fixed with chmod 444). doctor's path handling lives
in crates/registry-evidencectl/src/doctor.rs, which already documents its intent to resolve a
project-relative path where possible (around line 875).
This only affects an operator running doctor interactively; it does not block anything already
running, since the absolute-path form of the same command already works.
The audit recommended accepting or resolving relative --runtime-config paths so this class of
opaque failure does not happen at all.
Found in the 2026-09-24 lifecycle audit (EVID-21); the detailed finding is in the internal audit
report.
- 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:evidence criticality:p3 triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
registrystack/registry-stack#1620 ·
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
All issues in registrystack/registry-stack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
leptos-rs/leptos#4885 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
longbridge/gpui-kit#3276 ·
Maintainers usually reply within 1 day
-
A-Migration Guides D-Straightforward S-Ready-For-Implementation X-Uncontroversial
Difficulty 1/5 Under an hour Newbie friendliness 88/100
bevyengine/bevy-website#2607 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
bytecodealliance/wasmtime#14433 ·
Maintainers usually reply within 1 day