tui: hours of historical output vanish from the view while the rows are still in the DB, under a sibling session id
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- sqlite, typescript
调研方向
Start in the TUI session-selection and binding code that maps the rendered view to a session id, then trace how a model/provider switch can rebind or drop that id. Use the two SQLite sessions and the session_message table as the reference: session A has the gap while session B holds the missing rows. First reproduce on a long-running TUI with a provider switch; done means the view stays bound to the original session and its full history remains visible.
由索引模型根据 Issue 内容生成。
描述
Version
opencode 2.3.2 (channel latest), Linux, TUI.
What happened
While working in a single TUI, output that had been on screen for hours is no longer
visible. The current session's message history contains a hole of 21,356 s
(5 h 55 m 56 s) — 10:56:34 -> 16:52:30 — and the turns that were rendered during
that window are not in it at all. They are still on disk, in a sibling session in the
same project and the same directory, which is what makes this a view/binding problem
rather than data loss.
Measured (sqlite, read-only, both sessions)
| session A (the one the TUI shows now) | session B (holds the missing output) | |
|---|---|---|
| id | ses_e07a922f3ffe15Qu06K0bHbGU7 |
ses_e0763c5b5ffelNqQoTsGuwDjCv |
| project / directory | a3b70b365cae50c572407228dc7cd6ea9ae6eb8f / /home/user |
same / same |
| model | opencode-go/mimo-v2.6-flash |
opencode-go/glm-5.3-flash |
rows (session_message) |
119, 09:43:24 -> 17:21:24 |
453, 10:59:10 -> 16:55:21 |
| rows inside A's hole | — | 451, 10:59:10 -> 16:50:20 |
parent_id / fork_session_id |
None / None |
None / None |
time_compacting |
null |
null |
Gaps in session A larger than 180 s: 307 s, 1046 s, 210 s, 21,356 s, 637 s.
Because time_compacting is null on both and neither session is a parent/fork of the
other, this is not a compaction or a fork that the user asked for — the TUI simply
stopped being bound to the conversation it was displaying.
Expected
Historical output stays visible in the TUI for the session that produced it.
Actual
The view switches to a different session id (or drops the earlier one), so hours of
output disappear from the screen even though session_message still holds every row.
The user has no way to get that transcript back from the UI.
Notes
- Both sessions are readable and unmodified, so nothing was deleted.
- The model differs between the two (
mimo-v2.6-flashvsglm-5.3-flash), which is the
only obvious difference; a model/provider switch around that time may be the trigger. - Repro steps not yet determined — observed on a long-running TUI (opened 09:43, still
running).
- 主要语言
- TypeScript
- 星标
- 227k
- 派生
- 30.7k
- 平均合并
- 3 小时 57 分钟
- 30 天内合并 PR
- 484
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
anomalyco/opencode 的其他 Issue
-
[Site] Active section detection should respect scroll-margin-top可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭area/web reproduced type/bug
难度 2/5 1-3 小时 新手友好度 65/100
anomalyco/opencode#65384 · 1 条评论 ·
维护者通常 1 天内回复
-
area/cli type/feature version/v2
难度 2/5 1-3 小时 新手友好度 68/100
anomalyco/opencode#65379 · 1 条评论 ·
维护者通常 1 天内回复
-
Shell tool: no upper bound on the timeout a model can ask for, so one call can hold a turn for hours未关闭area/core platform/linux type/feature version/v2
难度 2/5 1-3 小时 新手友好度 75/100
anomalyco/opencode#65254 · 1 条评论 ·
维护者通常 1 天内回复
-
inference/go type/feature
难度 1/5 1-3 小时 新手友好度 72/100
anomalyco/opencode#65148 · 1 条评论 ·
维护者通常 1 天内回复
-
area/providers type/feature version/v2
难度 2/5 1-3 小时 新手友好度 68/100
anomalyco/opencode#64845 · 1 条评论 ·
维护者通常 1 天内回复
查看 anomalyco/opencode 的全部 Issue
相似的 Issue
-
[Provider] antigravity-acp catalog omits gemini-4-hydrogen and gemini-4-neon that agy acp offers未关闭catalog provider provider-compatibility
难度 2/5 1-3 小时 新手友好度 62/100
lidge-jun/opencodex#9037 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 62/100
slavakurilyak/awesome-ai-agents#1005 ·
-
kind/bug triage/unresolved
难度 2/5 1-3 小时 新手友好度 60/100
维护者通常 1 天内回复
-
effort:S P3 refactor
难度 2/5 1-3 小时 新手友好度 72/100
nightscout/nocturne#3735 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
wpilibsuite/systemcore-blocks-interface#641 ·
维护者通常 2 天内回复