Antigravity: "Running view_file" never gets a completed status mid-turn, so the UI shows it hanging for minutes and the trail log records fake durations
维护者通常 1 天内回复
还没有人认领这个 Issue。
- #31 来自 @warhammered —— 已关闭,未合并
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 55/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
Start by tracing the ACP adapter’s handling of session/update messages and how it matches tool call IDs to open view_file calls; the issue does not name source files. Enable DUSK_DEBUG_ACP=1 and reproduce by asking Antigravity to read several workspace files. Done means read calls emit their completion before bot.turn.end, covered by a test for an Antigravity read.
由索引模型根据 Issue 内容生成。
描述
Version
0.2.15 (also seen on 0.2.12 before the update)
Platform
Own server (Windows 11 + WSL2 Ubuntu 24.04)
Engine
Gemini 4 Hydrogen via Antigravity ACP (agy_acp_server.par in bwrap)
What happened
Expected: each view_file tool call is marked done when Antigravity finishes it, like Read on the Claude engine.
Actual: the chat shows "Running view_file" for minutes (users see "Digging around" for 10 to 14 minutes). In logs/trail-server.jsonl (16 Nov 22:32 to 17 Nov 18:33 WIB):
| count | |
|---|---|
Running view_file events |
393 |
logged ok:true, all within 2 s of bot.turn.end |
195 |
logged ok:false mid-turn |
189 |
ok:true logged mid-turn |
0 |
| completions sharing the same second with others | 358 (bursts up to 20) |
Median logged duration 52 s, p90 366 s, max 957 s. Claude engine Read in the same period: 119 calls, median 0.2 s, 97% ok. Running client_view_file: 10 calls, 3 ok.
So a view_file is never closed when it actually finishes. It is closed in a batch, either as failed when the next step starts or as ok when the turn ends. The status the user sees and the durations in the log are both wrong, which makes every Gemini turn look stuck and makes the "slow model" notice fire.
Steps to reproduce
- Bot on Antigravity / Gemini 4 Hydrogen, ask it to read 5 files in its workspace and summarize them.
- Watch the chat: each "Running view_file" stays until the turn ends.
grep 'view_file' ~/.duskbot/logs/trail-server.jsonland comparetswith the turn'sbot.turn.end.
Likely cause (hypothesis, not confirmed in source)
The ACP adapter does not match Antigravity's tool_call_update with status: completed to the open view_file call (different toolCallId, or the update arrives without the status field the adapter checks), so the call is only settled by the end-of-step or end-of-turn sweep.
Suggested fix
Log the raw session/update messages for one view_file with DUSK_DEBUG_ACP=1 and settle the call on the first update that carries completed/failed or content for that toolCallId. Add a test that bot.tool for an Antigravity read is emitted before bot.turn.end.
- 主要语言
- TypeScript
- 星标
- 277
- 派生
- 27
- 平均合并
- 2 小时 47 分钟
- 30 天内合并 PR
- 1
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
DuskBotAI/duskbot 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 63/100
维护者通常 1 天内回复
-
After uninstalling an own server, the desktop app stays on it and shows Cloudflare's Error 1033 page未关闭
难度 3/5 1-2 天 新手友好度 65/100
维护者通常 1 天内回复
-
install.sh --tailscale replaces whatever the host already serves on tailnet port 443可能已有人在做 @viniciusbregoli 今天认领。 未关闭
难度 4/5 3-5 天 新手友好度 25/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
维护者通常 1 天内回复
查看 DuskBotAI/duskbot 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
inabagumi/shinju-date#7406 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
umami-software/umami#4787 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复