Repository navigation
[PR] Fix #4311: Block summary and compress call parameters rendered twice — no longer duplicated when the call is present | 修复 #4311:块摘要与 compress 调用参数双份上线 — 调用在场时不再重复渲染 - #4314
Conversation
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.5164-pr.4314.8dbcad4This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr4314.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm-qwen/qwen3.8-27b) 查重: 同家族整合分支——本 PR 内容 ⊇ #4310(其又 ⊇ #4291/#4293 的修复面)+ #4311,但 base 取的是过期中间态(详见发现 A),与在途 PR 的关系需在合并前处置。 标签: bug, p1, pi, scope/kernel(压缩残渣只增不减 = 缓存泄露类一律 p1;事故会话为 pi 车道;修复全部落在 kernel/)。 审核方式说明未复读 PR 描述与 issue 结论,从代码独立重推:逐文件读了本分支相对 origin/master 的全部 kernel diff、宿主侧回执发射点、prune/compressCallId 数据流,并与 #4291/#4310/#4293 三个在途 PR 的真实 head 做了树级对比(
|
ce9a56a to
61da38f
Compare
… call is already on the wire The summary text of every fold reached the model twice: once as the block's acp_summary render at the fold point, and once inside the originating compress call's arguments (the exchange is permanently protected, so it never folds). On residue-heavy sessions that duplication is pure dead weight. Composing the snapshot now skips the anchor render for blocks whose compressCallId resolves to a tool-call visible in the SAME view — the exchange itself is the model-visible recap. Blocks whose call is gone (folded away, gateway-dropped) or that never had one (system folds, codex/dsh forged-summary lanes) keep their render, so a summary never disappears. Stale renders from previously-pruned views are dropped by the existing knownSummaryIds path and not re-injected. Storage is untouched (blockContents / payloadJson / message rows). Companion orphan rule from the issue discussion (doom receipt-less calls with no block) was dropped: the receipt-loss premise was a census misclassification — 239 calls vs 239 receipts in 1639 real request dumps (#4307 investigation), receipt-less shapes in practice are in-flight pending calls, which #4289 keeps protected. kernel 0.0.155 → 0.0.156. Fixes #4311
61da38f to
8c9e33f
Compare
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.743-master.8fbf2b9 # this exact build
npm install -g billion-context@master # always the newest merged build
|
Fixes #4311
kernel-change: skip duplicate acp_summary render when the originating compress call is visible in the composed view (prune anchor filter, #4311)
改了什么
组合快照时,若折叠块的
compressCallId能对上当前视图里可见的 compress 工具调用,则跳过该块的acp_summary渲染注入 —— 调用参数本身就携带完整摘要草稿,且交换按设计永久保护,再渲染一遍就是同一份文本发两遍。调用不在视图里(已被折掉/网关丢弃)或根本没有调用来源(系统折叠、codex/dsh 伪造渲染车道)的块照常渲染,摘要永远不会凭空消失。存储零变化。有意不做的事(以及为什么)
issue 里讨论过的"孤儿子规则"(回执丢失、无块的调用按死处理)没有实现:#4307 调查对 1639 份真实请求转储逐个核对 tool_call_id,239 次调用对应 239 条回执,零丢失 —— 我早前普查里的"22 条无回执孤儿"是把渲染拆分误读成的假象。真实线上不存在回执丢失孤儿;线上仅有的"无回执"形态是当回合进行中的 pending 调用,而 #4289 明确要求 pending 保持保护。给一个不存在的形态加折叠通道,反而会碰 pending 契约(实现中 5 个既有测试红灯验证了这一点),遂整体回退该部分。
测试
cc @ranxianglei