[RCA] Create a reviewable evidence-selection plan
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Ambito
- cli, observability
Direzione di ricerca
Start by checking the prerequisite issue #14223 and the existing bydbctl command structure under bydbctl/internal/cmd; the issue says the final test paths depend on the prerequisite seam. Implement and test the proposed selection operation through its real CLI entry point, covering budget refusal, pinned evidence, exact ledger reasons, coverage, unchanged raw hashes, and output conflicts. Done means the acceptance scenarios pass with focused behavioral tests and documented fixture provenance.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Umbrella: #14222
Blocked by: #14223
Summary
Create a reviewable evidence-selection plan. Deliver one usable operation, not a framework-only foundation.
Boundary
Proposed activation caller: bydbctl rca curate --workspace … --selection …. Command names are proposed, not existing APIs.
Reporter collection runs with read-only source access; offline steps use local files only.
No source storage/wire-format changes are requested. The incident format is separately versioned.
Requirements
R1. Generate a candidate selection by incident interval, components, sources and byte budget; never mutate raw evidence or claim the selection is public-safe.
R2. Keep a selection ledger naming every included/excluded artifact, reason and coverage consequence. An over-budget selection is refused with the exact excess and an explanation; it is never silently reduced.
R3. Apply explicit reporter inclusion/exclusion rules and pins for contradictory evidence and control samples. No automatic relevance ranking. If the resulting selection exceeds the budget, refuse it with the excess and require a revised selection; never silently discard pinned evidence.
R4. Show size and source/time/component coverage before and after selection, including omitted crash/profile artifacts. Persist the approved selection separately from raw data.
Acceptance criteria
- A fixed inventory contains a small error log, a healthy control log, a contradictory event and a large profile. A budget too small for pinned evidence fails with the exact excess, not silent removal.
- Re-run with sufficient budget and check the exact selected IDs and ledger reasons; raw hashes remain unchanged.
- Use hand-authored or independently captured fixtures with documented provenance; do not generate expected values using the code under test.
- Add focused behavioral tests before implementation and record the actual RED command/failure, then GREEN results.
- Keep existing CLI/API behavior compatible. Never overwrite unrelated user files; output conflicts must be refused.
Scope and readiness audit
- Boundary and behavior: the single operation above; independently observable output and refusal behavior.
- Production activation: the named CLI or skill entry point above, included in the same PR.
- Packages/callers: workspace inventory and artifact metadata; local deterministic selection command.
- Dependencies: #14223
- Classification: planned blocked leaf; revalidate prerequisite seams after merge.
- RED evidence: not executed during this planning task; no claim of passing or failing implementation tests.
- End-to-end proof: the real command/skill scenarios above, not source-text assertions.
- Formats/lifecycle/fixtures: private workspace or public archive only; artifact-specific fixture family above.
- Focused tests: CLI leaves should add
TestRCA…coverage underbydbctl/internal/cmdand/or the introduced collector package;
rungo test ./bydbctl/internal/cmd -run TestRCA -count=1plus the new package tests. Skill leaves must add a replayable evaluation harness
with an exact command documented in the PR. Final test names/paths are fixed when the prerequisite seam merges. - Resource/concurrency checks: cancellation, bounded reads/output and cleanup on failure; use repository panic-aware goroutine wrappers if concurrency is introduced.
- Decision: one proposed PR. If the named behavior requires an unimplemented server API or another lifecycle change, stop and split that prerequisite.
Required-only scope audit
Reporter-controlled reduction is required to make large collections reviewable; relevance ranking is not.
Removed/deferred: Automatic relevance scoring, AI-selected publication, automatic incident detection and report dashboards.
Out of scope
LLM judgment as a safety gate, redaction, archive publication, auto-upload.
- Lingua principale
- Java
- Stelle
- 25k
- Fork
- 6.6k
- Merge medio
- 12h 1m
- PR unite (30g)
- 43
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di apache/skywalking
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
apache/skywalking#14239 ·
I maintainer di solito rispondono entro 1 giorno
-
AI Assistant database enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 24/100
apache/skywalking#14237 ·
I maintainer di solito rispondono entro 1 giorno
-
database enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
apache/skywalking#14236 ·
I maintainer di solito rispondono entro 1 giorno
-
AI Assistant database enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
apache/skywalking#14235 ·
I maintainer di solito rispondono entro 1 giorno
-
database enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 30/100
apache/skywalking#14234 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di apache/skywalking
Issue simili
-
account bug exercise lecture modeling programming
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
I maintainer di solito rispondono entro 1 giorno
-
Re-executed query with IN condition on an index column returns deleted rows (stale IndexCursor)Forse già presa @dbusche l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
h2database/h2database#4580 ·
I maintainer di solito rispondono entro 1 giorno
-
vips-drift
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
Stirling-Tools/JPDFium#300 ·
I maintainer di solito rispondono entro 1 giorno
-
hermes-queue
Difficoltà 1/5 1-3 ore Idoneità per principianti 85/100
chrisalunlloyd2-sudo/mindpalace#403 ·
I maintainer di solito rispondono entro 1 giorno
-
component:core regression
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
jenkinsci/jenkins#27783 · 3 commenti ·
I maintainer di solito rispondono entro 2 giorni