The task rail counts interrupted and stopped runs as done
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 75/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- go
- 领域
- cli, documentation, testing
调研方向
Start in internal/tui3/task.go at railGroupOf around line 2459 and reproduce the deterministic interrupted and stopped task-node cases. Add coverage for every rail group, including stopped and interrupted, then verify the e2e acceptance that neither produces “1 done” as its only footer account. Update the rail manual and record the former count in invalidates.
由索引模型根据 Issue 内容生成。
描述
Found on santos/dev2 at 008363c98 (#1410). On dev@debffabf6 too.
What happened
After a run was interrupted, the rail footer said 1 done. The same final fallback groups a stopped run under done. The individual state can read interrupted or stopped, but the group total tells a different story. This grouping code is also present on dev.
Replication
Deterministic (no model). In internal/tui3, construct task nodes whose taskStatus states are interrupted and stopped, then call railGroupOf. Today both fall through to railDone. Inspect the rendered rail footer for one such node; it reads 1 done.
Field (real models). Start a long /task in codeaf chat --no-host, quit and reopen. The run reads interrupted while the rail totals it as done. Use OPENROUTER_API_KEY and deepseek/deepseek-v4-flash; allow a few minutes and a small charge.
Where
internal/tui3/task.go:2459, railGroupOf, returns railDone for every state not handled earlier. The same fallthrough appears at origin/dev:internal/tui3/task.go:2459.
The fix
Give stopped and interrupted runs their own honest rail grouping or a neutral completed-work group whose label does not claim they are done.
Acceptance
- e2e: a stopped or interrupted
/tasknever produces1 doneas its only footer account. - Unit: a state table pins every rail group, including stopped and interrupted.
- Update the rail manual and record the former count in
invalidates.
- 主要语言
- Go
- 星标
- 115
- 派生
- 14
- 平均合并
- 9 小时 35 分钟
- 30 天内合并 PR
- 752
环境准备
我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Agent-Field/CodeAF 的其他 Issue
-
area:chat bug sev:papercut
难度 2/5 1-3 小时 新手友好度 86/100
Agent-Field/CodeAF#1592 ·
维护者通常 1 天内回复
-
area:headless bug sev:critical
难度 2/5 1-3 小时 新手友好度 88/100
Agent-Field/CodeAF#1566 ·
维护者通常 1 天内回复
-
area:chat bug sev:critical
难度 2/5 1-3 小时 新手友好度 82/100
Agent-Field/CodeAF#1548 · 1 条评论 ·
维护者通常 1 天内回复
-
area:chat feature
难度 2/5 1-3 小时 新手友好度 88/100
Agent-Field/CodeAF#1510 ·
维护者通常 1 天内回复
-
area:tests bug
难度 2/5 1-3 小时 新手友好度 82/100
Agent-Field/CodeAF#1489 ·
维护者通常 1 天内回复
查看 Agent-Field/CodeAF 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
siderolabs/terraform-provider-talos#414 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
JuliaComputing/jh#63 · 1 条评论 ·
-
area/proxy kind/bug priority/backlog triage/accepted
难度 2/5 1-3 小时 新手友好度 68/100
lexfrei/cloudflare-tunnel-gateway-controller#840 ·
维护者通常 1 天内回复
-
Priority: Normal Type: Bug
难度 2/5 1-3 小时 新手友好度 78/100
cloudflare/cloudflared#1747 ·