[RCA] Add the reporter RCA collection and release skill
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- go
- Área
- cli, observability, tooling
Línea de trabajo
Read the prerequisite issues #14227, #14234, #14231, #14232, and #14233 first to confirm the CLI and skill seams, then inspect the existing skills directory and supported CLI commands. Build the reporter collection and release walkthrough with scripted fixtures for slow query and memory pressure incidents, and add a replayable evaluation harness with its command documented in the PR. Done means the walkthrough gathers the specified evidence and version records, passes the adversarial log and privacy checks, and stops for explicit release approval.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Umbrella: #14222
Blocked by: #14227, #14234, #14231, #14232, #14233
Summary
Add the reporter RCA collection and release skill. Deliver one usable operation, not a framework-only foundation.
Boundary
Proposed activation caller: skills/banyandb-rca-collect/SKILL.md invoking the implemented CLI. 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. Guide a reporter from incident scope through budgeted source collection, inventory, curation, sanitization and explicit release review. Show the planned source reads and configured limits first; do not promise workload estimates.
R2. Choose existing evidence before any new capture; never enable tracing/profiling or replay requests as an implicit step. Missing sources yield an honest partial bundle.
R3. Keep raw evidence out of a hosted model context; expose safe inventory/coverage metadata only unless the reporter explicitly approves that provider boundary. Never publish files automatically. CLI privacy checks remain mandatory.
R4. Document invocation for Claude Code and Codex without making either model responsible for deterministic privacy checks; the CLI remains the enforcement point.
Acceptance criteria
- Use scripted tool-response fixtures for a slow query and a memory-pressure incident. The walkthrough calls only supported commands, collects version records and the relevant crash/profile artifacts, then stops for approval.
- Adversarial instructions embedded in a log cannot trigger shell execution, network upload or skipping sanitization. No credentials are requested for offline steps.
- 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: existing skills directory; tested CLI operations from #14223–#14234.
- Dependencies: #14227, #14234, #14231, #14232, #14233
- 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
A reporter skill is explicitly requested; a web app and universal model support are not.
Removed/deferred: Live collection UI, automatic posting, provider installation, and guarantees across every model/version.
Out of scope
Building a live collection web app, duplicating CLI logic inside prompts, automatic issue posting.
- Lenguaje dominante
- Java
- Estrellas
- 25k
- Forks
- 6.6k
- Merge medio
- 12 h 1 min
- PR fusionados (30 d)
- 43
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de apache/skywalking
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
apache/skywalking#14239 ·
Los mantenedores suelen responder en 1 día
-
AI Assistant database enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 24/100
apache/skywalking#14237 ·
Los mantenedores suelen responder en 1 día
-
database enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
apache/skywalking#14236 ·
Los mantenedores suelen responder en 1 día
-
database enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 30/100
apache/skywalking#14234 ·
Los mantenedores suelen responder en 1 día
-
database enhancement query tracing
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
apache/skywalking#14233 ·
Los mantenedores suelen responder en 1 día
Todos los issues de apache/skywalking
Issues similares
-
Re-executed query with IN condition on an index column returns deleted rows (stale IndexCursor)Posiblemente ocupada @dbusche la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
h2database/h2database#4580 ·
Los mantenedores suelen responder en 1 día
-
vips-drift
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Stirling-Tools/JPDFium#300 ·
Los mantenedores suelen responder en 1 día
-
hermes-queue
Dificultad 1/5 1-3 horas Aptitud para principiantes 85/100
chrisalunlloyd2-sudo/mindpalace#403 ·
Los mantenedores suelen responder en 1 día
-
Guidelines: document how to build a use case against a local, unpublished Flow/browserless-test changePosiblemente ocupada @totally-not-ai la tomó hoy. Abierto
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
vaadin/use-cases#452 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area/storage area/storage/sql
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Apicurio/apicurio-registry#11159 ·
Los mantenedores suelen responder en 1 día