[RCA] Seal a human-reviewed public incident archive
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 30/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github, java
- 领域
- cli, observability
调研方向
Read the prerequisite issue #14230 and inspect the candidate release tree, transformation report, selection ledger, and archive writer after their seams are available. Start by adding focused behavioral tests with independently prepared fixtures; document and run the actual RED command before implementation. The work is done when the real bydbctl rca seal operation binds approval to the candidate digest and policy version, validates inputs, writes the bounded archive atomically, and passes the listed refusal and cancellation scenarios.
由索引模型根据 Issue 内容生成。
描述
Umbrella: #14222
Blocked by: #14230
Summary
Seal a human-reviewed public incident archive. Deliver one usable operation, not a framework-only foundation.
Boundary
Proposed activation caller: bydbctl rca seal --candidate … --approval … --output …. 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. Bind explicit human approval to the candidate content digest and policy version. Any later candidate edit invalidates approval.
R2. Validate the supported public manifest, allowed file types, coverage/omission summary and absence of private workspace paths/keys before packaging. Reject unresolved required reviews.
R3. Write one bounded archive format with per-file hashes and a format version; finalize atomically. Canonicalize the reviewed file inventory for its approval digest, but byte-for-byte reproducibility of compressed archives is not required.
R4. Include a minimal local incident/coverage summary and archive only. Do not upload, post or change file sharing permissions.
Acceptance criteria
- Approve a fixed candidate, alter one byte, and assert sealing is refused. A clean candidate produces the independently expected file list and hashes without raw siblings.
- Reject symlinks, duplicate paths and unsupported schema versions. Cancel during archive writing and verify no completed release exists.
- 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: candidate release tree, transformation report, selection ledger and archive writer.
- Dependencies: #14230
- 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
Human approval, integrity and a transferable archive are required; reproducible compression bytes and GitHub integration are not.
Removed/deferred: GitHub templates/API integration, signatures, multiple archive formats and reproducible compressed bytes.
Out of scope
GitHub API integration, signing infrastructure, automatic approval, binary-profile sanitization.
- 主要语言
- Java
- 星标
- 25k
- 派生
- 6.6k
- 平均合并
- 12 小时 1 分钟
- 30 天内合并 PR
- 43
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
apache/skywalking 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
apache/skywalking#14239 ·
维护者通常 1 天内回复
-
AI Assistant database enhancement
难度 5/5 一周以上 新手友好度 24/100
apache/skywalking#14237 ·
维护者通常 1 天内回复
-
database enhancement
难度 5/5 一周以上 新手友好度 25/100
apache/skywalking#14236 ·
维护者通常 1 天内回复
-
AI Assistant database enhancement
难度 5/5 一周以上 新手友好度 25/100
apache/skywalking#14235 ·
维护者通常 1 天内回复
-
database enhancement query tracing
难度 5/5 一周以上 新手友好度 35/100
apache/skywalking#14233 ·
维护者通常 1 天内回复
查看 apache/skywalking 的全部 Issue
相似的 Issue
-
Re-executed query with IN condition on an index column returns deleted rows (stale IndexCursor)可能已有人在做 @dbusche 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
h2database/h2database#4580 ·
维护者通常 1 天内回复
-
vips-drift
难度 2/5 1-3 小时 新手友好度 74/100
Stirling-Tools/JPDFium#300 ·
维护者通常 1 天内回复
-
hermes-queue
难度 1/5 1-3 小时 新手友好度 85/100
chrisalunlloyd2-sudo/mindpalace#403 ·
维护者通常 1 天内回复
-
Guidelines: document how to build a use case against a local, unpublished Flow/browserless-test change可能已有人在做 @totally-not-ai 今天认领。 未关闭
难度 1/5 1-3 小时 新手友好度 88/100
vaadin/use-cases#452 · 1 条评论 ·
维护者通常 1 天内回复
-
area/storage area/storage/sql
难度 2/5 1-3 小时 新手友好度 78/100
Apicurio/apicurio-registry#11159 ·
维护者通常 1 天内回复