Repository navigation
fix: release unrun distillation claims after a batch failure - #71
Conversation
|
Sentinel 已审核此变更,未发现需要报告的问题。 开发 agent 查询详情: 调用 MCP 工具 由 Sentinel 审核 · 目标提交 f057bf72e49d |
|
Sentinel 已审核此变更,未发现已核验问题,但发现需要人工确认的风险。 另有 1 个需要人工确认的风险;黄色 advisory 不阻塞合并,建议开发 agent review advisory 评论并逐条确认。 开发 agent 查询详情: 调用 MCP 工具 由 Sentinel 审核 · 目标提交 5060eefd0766 |
|
Sentinel 保留了 1 个尚未确认的审核候选。这些黄色条目不阻塞合并;红色 P0/P1 与其他独立硬门禁不受影响。 单一猜测、缺少变更行证据或纯 checklist 的候选会统一降为 P3。
需要完整证据时,可用行末 由 Sentinel 审核 · 目标提交 5060eefd0766 |
The captured-owner change targeted lib/app/native-turn.js, which EvoMap#68 removed; main's shared late-terminal flow takes precedence, as the PR description anticipated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A run that threw already settled its own claim, and earlier runs settled theirs; releasing those again relied on the claim guard alone and could drop a claim this process took again meanwhile. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bugbot is paused — on-demand spend limit reachedBugbot uses usage-based billing for this team and has hit its on-demand spend limit. A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue. |
|
Merged with maintainer changes: main merged in (dropping the owner-retention commit superseded by #68), and the catch path now releases only the claims that never ran ( |
|
Sentinel 已审核此变更,未发现需要报告的问题。 开发 agent 查询详情: 调用 MCP 工具 由 Sentinel 审核 · 目标提交 b196e2603565 |
Summary A failed background distillation could leave later sessions in the same batch claimed by the still-running host. They then stayed busy even after the write failure was repaired. Return every still-matching claim when the batch throws, using the existing range identity guard inside one locked state update. A retry can process the remaining work. ## Evidence - The regression first reproduced a second range still owned by PID 7 after a corpus write failure. - With the fix, both claims are released, neither attempt counter increases, and a retry processes each session once. - Relevant distillation and architecture tests passed 61/61 on Windows Node 22.23.4 and 26.13.0. - The patch also applies to #68 at 119f901. ## Merge Danger Two-way. Scope is background batch failure cleanup. Releasing claims still requires the candidate state file to be writable.
Includes the captured-null owner fix also on #70 so the existing Kimi Windows hook stays within its budget during CI.