Classify failures versus unknown outcomes after partial apply
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- javascript
- 领域
- devtools
调研方向
Start by reading dependency issue #22 (B04-01) and the roadmap item B05-01 to understand the existing apply and recovery design. Then identify the mutation entry points and tests for timeout-after-send and hard-error-before-send outcomes. Done means each mutation has a stable id and is recorded as applied, failed, or unknown, with unknown outcomes never replayed; the classification rules and uncertainty boundary still need approval.
由索引模型根据 Issue 内容生成。
描述
Goal
Detect and classify partial-apply outcomes as confirmed failure versus unknown, so recovery never replays an uncertain mutation.
Observations
- A partial apply can leave the API in an unknown state (for example, a timeout after send).
- Treating unknown as success or failure both risk duplication.
Decision gate
Approve the classification rules and the uncertainty boundary before implementing recovery.
Acceptance criteria
- Each mutation outcome is classified as applied, failed, or unknown.
- Unknown outcomes are never assumed applied or failed.
- Classification is recorded per mutation with a stable id.
Verification
- Injected timeout after send -> outcome recorded as unknown, no replay attempt.
- Injected hard error before send -> outcome recorded as failed.
Release checkpoint
Remaining risk: unknown is a real state, not a bug to hide. No auto-rollback as a workaround.
Tracking
Roadmap item: B05-01. All acceptance criteria remain pending; publication does not grant approval or release authority.
Dependencies
- Depends on #22 (B04-01).
- 主要语言
- JavaScript
- 星标
- 22
- 派生
- 3
- 平均合并
- 27 分钟
- 30 天内合并 PR
- 27
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
egdev6/github-repository-bootstrap 的其他 Issue
-
status:approved type:chore
难度 5/5 一周以上 新手友好度 25/100
egdev6/github-repository-bootstrap#57 ·
维护者通常 1 天内回复
-
type:docs
难度 1/5 1 小时以内 新手友好度 20/100
egdev6/github-repository-bootstrap#50 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 22/100
egdev6/github-repository-bootstrap#49 ·
维护者通常 1 天内回复
-
status:approved type:chore
难度 5/5 一周以上 新手友好度 25/100
egdev6/github-repository-bootstrap#30 ·
维护者通常 1 天内回复
-
status:approved type:chore
难度 5/5 一周以上 新手友好度 42/100
egdev6/github-repository-bootstrap#29 ·
维护者通常 1 天内回复
查看 egdev6/github-repository-bootstrap 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 70/100
gkjohnson/three-mesh-bvh#933 ·
-
scope: curriculum status: waiting triage
难度 2/5 1-3 小时 新手友好度 72/100
freeCodeCamp/freeCodeCamp#71076 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
HarperFast/harper#3275 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
documentation good first issue help wanted
难度 2/5 1-3 小时 新手友好度 75/100
steerion-labs/bounded-agent-runtime#93 ·
维护者通常 1 天内回复