Sessions can clear a remembered conversation's working mark
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start at internal/tui3/place_sessions.go:373-385 and follow tasksPlace.filtered, then inspect the row consumer in internal/tui3/tasksplace.go:755. Reproduce the filtered-reading fixture with a saved working conversation and another window's live task. Done means the unit and two-window e2e cases keep the row working, with the Sessions manual updated and the former false mark recorded in invalidates.
由索引模型根据 Issue 内容生成。
描述
Seen on dev@debffabf6. Surfaced while verifying #1426; not introduced by it.
What happened
When this window has no watcher for a remembered conversation, the Sessions place rebuilds chatViews from this window's tab list and calls homeChatState. That call can return working: false, overwriting the saved working state even while another window's task is running. The row then looks idle until a later refresh restores the work reading.
Replication
Deterministic (no model). Seed a Sessions reading with a saved conversation marked working and a live task owned by another window. Give the current app a tab for that conversation but no local watcher, then call tasksPlace.filtered. Inspect r.chatViews[transcript].working: today it is false. A same-window watcher is the control.
Where
internal/tui3/place_sessions.go:373 at dev@debffabf6, tasksPlace.filtered, recreates chatViews; :385 substitutes homeChatState for the saved state. The row painter consumes that value in internal/tui3/tasksplace.go:755.
The fix
Combine live local state with the remembered and cross-window work reading, preserving true until the underlying task has actually settled.
Acceptance
- e2e: two
codeaf chatwindows viewing the same home keep the Sessions row marked working while one window's task runs and the other has no watcher. - Unit: the filtered-reading fixture above preserves
working: true. - Update the Sessions manual and record the former false mark in
invalidates.
- 主要语言
- Go
- 星标
- 115
- 派生
- 14
- 平均合并
- 9 小时 38 分钟
- 30 天内合并 PR
- 749
环境准备
我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Agent-Field/CodeAF 的其他 Issue
-
area:chat feature
难度 2/5 1-3 小时 新手友好度 88/100
Agent-Field/CodeAF#1510 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
Agent-Field/CodeAF#1489 ·
维护者通常 1 天内回复
-
area:chat bug good first issue sev:papercut
难度 2/5 1-3 小时 新手友好度 78/100
Agent-Field/CodeAF#1470 ·
维护者通常 1 天内回复
-
area:chat bug good first issue sev:papercut
难度 2/5 1-3 小时 新手友好度 85/100
Agent-Field/CodeAF#1469 ·
维护者通常 1 天内回复
-
area:chat bug sev:papercut
难度 2/5 1-3 小时 新手友好度 88/100
Agent-Field/CodeAF#1468 ·
维护者通常 1 天内回复
查看 Agent-Field/CodeAF 的全部 Issue
相似的 Issue
-
enhancement low priority
难度 2/5 1-3 小时 新手友好度 85/100
eugenioenko/ttt#674 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 92/100
GoogleCloudPlatform/k8s-config-connector#13462 ·
维护者通常 1 天内回复
-
bug good first issue
难度 2/5 1-3 小时 新手友好度 85/100
vavallee/bindery#2793 · 1 条评论 ·
维护者通常 1 天内回复