ui.submit resolves before the TUI snapshots the composer, so back-to-back submits merge into one prompt
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
Start with the ui.submit and ui.enter implementation in the driver, then submitInner in packages/tui/src/component/prompt/index.tsx, where the deferred handler reads input.plainText. Reproduce by running two ui.submit calls in a row and checking that the server gets two separate messages. Done means /undo runs as its own command, or the driver waits for the composer snapshot before resolving and a test covers that. If the fix is not practical, the docs should say a wait is needed between submits.
由索引模型根据 Issue 内容生成。
描述
Drive 2.1.3 (source checkout at 8feac04). OpenCode V2 at 5cfe3b4271, run from source with opencode: { dev }.
What happens
Two ui.submit calls in a row are admitted as one prompt:
yield* ui.submit("ALPHA first prompt")
yield* ui.submit("/undo")
The server received a single user message with text ALPHA first prompt/undo. /undo never ran as a command. This happened on the home screen and also in a session that had already finished a turn.
Why
ui.submit returns once ui.enter is dispatched. The TUI handles Enter through a deferred submit (submitInner in packages/tui/src/component/prompt/index.tsx reads input.plainText when the deferred handler runs). The next ui.type reaches the composer before that handler runs, so the snapshot holds both texts.
Expected
Either ui.submit resolves after the composer has been snapshotted and cleared, or the docs say that a second ui.submit needs a wait first.
Workaround
Wait until the focused editor no longer contains the first text before the next ui.submit:
yield* ui.waitFor(() => Effect.map(editorText, (text) => !text.includes("ALPHA")), { interval: 10 })
editorText slices the focused editor element's rows from ui.capture().
- 主要语言
- TypeScript
- 星标
- 41
- 派生
- 9
- 平均合并
- 39 分钟
- 30 天内合并 PR
- 9
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
anomalyco/opencode-drive 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 69/100
anomalyco/opencode-drive#142 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
anomalyco/opencode-drive#141 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
anomalyco/opencode-drive#107 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
anomalyco/opencode-drive#102 · 2 条评论 ·
维护者通常 1 天内回复
-
llm settlement waits on a reply whose request an interrupt already aborted可能已有人在做 @mikemikimike 于 4 天前认领。 未关闭bug
难度 3/5 1-2 天 新手友好度 55/100
anomalyco/opencode-drive#135 ·
维护者通常 1 天内回复
查看 anomalyco/opencode-drive 的全部 Issue
相似的 Issue
-
bug from-app needs-triage
难度 2/5 1-3 小时 新手友好度 72/100
nightly-labs/openbot#7447 ·
维护者通常 1 天内回复
-
Team:ResponseOps technical debt
难度 2/5 1-3 小时 新手友好度 76/100
elastic/kibana#304569 · 1 条评论 ·
维护者通常 1 天内回复
-
security
难度 2/5 1-3 小时 新手友好度 64/100
IBM/ibmi-mcp-server#256 ·
维护者通常 7 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
egonSchiele/agency-lang#1444 ·
维护者通常 1 天内回复
-
e2e-failure ready-to-code
难度 1/5 1 小时以内 新手友好度 84/100
redhat-developer/rhdh-plugin-export-overlays#4746 · 1 条评论 ·
维护者通常 1 天内回复