scrub-at-rest: surface the wrapped failure category instead of a bare scrub-failed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 74/100
Research direction
Grep the repo for scrub-failed to locate where the scrub-at-rest CLI maps any non-ScrubAtRestError to reason=scrub-failed with detail=null, and read that handler plus the exception definitions (ScrubAtRestError, MaintenanceAbort and whatever carries the gate name). Check existing tests covering the refusal JSON output before changing anything. Done when the refusal JSON includes the exception class name and, for MaintenanceAbort, the gate name, with no values leaked, and the CLI tests pass.
Written by the indexing model from the issue text.
Description
The scrub-at-rest CLI maps any non-ScrubAtRestError to reason=scrub-failed with detail=null; the underlying category (e.g. MaintenanceAbort from the pre-quiesce gates) is only in the exception message, which is not printed. On 2026-10-07 this made two provider failures opaque until a lead re-ran them through a wrapper. Proposal: include a fixed, value-free cause category (exception class name, and the gate name for MaintenanceAbort) in the refusal JSON. Size XS. — brainlayerClaude-90982d09
- Dominant language
- Python
- Stars
- 9
- Forks
- 7
- Avg merge
- 4h 50m
- Merged PRs (30d)
- 404
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 EtanHey/brainlayer
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
EtanHey/brainlayer#1431 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
EtanHey/brainlayer#1428 ·
Maintainers usually reply within 1 day
-
test(BrainBar): inject synthetic observabilityCadence in BackupsHealth/one-page fixtures (DCI-1)Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
EtanHey/brainlayer#1367 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 78/100
EtanHey/brainlayer#1364 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
EtanHey/brainlayer#1362 ·
Maintainers usually reply within 1 day
All issues in EtanHey/brainlayer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
google-agentic-commerce/AP2#388 ·
-
area:codegen backend:cuda backend:hip bug direction:input
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CrossGL/crosstl#3061 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
rlaope/oh-my-hermes#2304 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
mochan-tk/agentic-dev-kit-for-codex#64 ·
Maintainers usually reply within 1 day
-
bug docs performance
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 3 days