Repository navigation
fix: sparse-ref unknown semantics + actionable compress failure receipts (#3302) - #3533
Conversation
…erations, name failing endpoints (#3302) - resolveAnchorIndex: a byRef miss at/below the highest allocated ref is reported as an unallocated-or-pruned sparse-space hole, not '(typo or wrong session)'; above the highest it names the frontier - tombstoned dead refs (state.deadRefs) resolve by snapping to the nearest visible message instead of failing outright; no neighbor => honest consumed/DEAD classification - all-unknown gate names each failing endpoint (startId=/endId= per range) and stops inviting numeric probing; diagnostics state the ref space is sparse - danglingMessageRefs counts tombstoned endpoints as dangling so the #2362 DEAD path covers host-pruned refs kernel-change: #3302 — host-side pruning (session.ts pruneRefsToLiveIds) makes the ref space sparse, but kernel error semantics assumed absence means cross-session/typo; models then probed endIds one number at a time, each probe a full round. Host alone cannot fix the error semantics or the gate wording. Bumps acp-kernel to 0.0.128.
…tionable (#3302) - pruneRefsToLiveIds records pruned refs into state.deadRefs (deduped, sorted) so both producers (compaction archive, zombie reap) feed the kernel tombstone path - failure receipt falls back to the last nudge's compressible-range table when no live decision exists, instead of 'Call acp_status before retrying' - loop logs a one-shot warning when a fixed-endpoint/varying-endpoint compress probe family is detected (#370 breaker stays identical-args only) - stale-ref cause text and FOLD BASE GENERATION MISMATCH body no longer assert cross-session origin
74455b0 to
4745333
Compare
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.4205-pr.3533.6e5aa5cThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr3533.tgz
npm install -g packageInstall instructions are refreshed on each push. |
4745333 to
5a6f07d
Compare
(ai: vllm-qwen/qwen3.8-27b) PR 分支已与最新 master 对齐:rebase 完成并已推送,冲突解除,PR 恢复可合并状态(等待新 head 上的 CI)。 冲突来源:master 在分支切出后合入了 132 个提交,其中多次 kernel 版本递进(0.0.127 → 0.0.128 → … → 0.0.130)与本 PR 自带的 kernel 版本 bump(0.0.127 → 0.0.128)在三个版本字段上正面相撞: 解决方式:rebase 两笔提交到当前 master(3f513c2),版本字段统一取 acp-kernel 0.0.131(master 现值 0.0.130 的下一个;Kernel Boundary 规则要求 kernel/src 变更必须 bump 版本)。顺带修掉一个 master 存量小漂移: 验证(最终树 5a6f07d,本地定向跑过):
结构化八问:
收工判定:冲突已解除,PR 回到正常 review/CI 流程;全量结论以远程 CI 在新 head(5a6f07d)上的结果为准。 |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) 查重:不重复。 本 PR 是 #3302(human-opened,owner 已接单)的唯一实现 PR;检索 open+closed 的 issue/PR(按失败签名:sparse-ref 错误语义、compress 失败回执、tombstone/probe-family 关键词),无其他在途工作项针对同一机制。#3302 的六个 Ask 与本 PR 的八项改动一一对应,无第二份平行修复。 状态:这是早前会话已完成的工作([PR] 工单),我不重做——按 [PR] 规则拉分支核对代码 + 确认 CI + 给出审核结论。当前进度:
正在本地定向跑新增回归测试做最后验证,随后给出结构化八问结论。kernel 变更属 human-only review 层级,最终合并需要你拍板。 |
…3533 review nit) The rebase hand-edit of the version field left packages."".version at 2-space indent instead of the npm lockfile's 6-space level. Whitespace-only.
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) PR #3533 审核结论(独立审 diff,未复用 issue 侧结论)已做的核验:逐段读完全部 12 个文件的 diff(kernel src/tests ×5、host src ×4、host tests ×1、版本字段 ×2);对每个改动点回读改动前的完整函数与消费方(grep 全仓旧文案、golden/wire-contract pin、startsWith 匹配方);本地定向复跑新增回归 + 相邻标记消费方套件 62/62 绿(kernel:issue3302-sparse-ref-unknown + compress.test.ts = 38;host:issue3302-sparse-ref-tombstones + issue2360-compress-receipt + issue2432-breaker-awareness + issue2592-rebase-floor = 24);CI 在 顺手修掉一处小瑕疵(独立 commit 结构化八问:
测试有效性:两份新测试都是真测试——kernel 侧驱动真实 分支状态:新 head 收工判定:代码、测试、CI、回归审计四项全过,我这边可合。注意 kernel 变更属 human-only review 层级(Kernel Boundary 规则 3,§7.4 不可 auto-merge)——请 owner 过目后自行合并:#3533 |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.559-master.eda8fb7 # this exact build
npm install -g billion-context@master # always the newest merged build
|
Closes #3302
kernel-change: host-side pruning (session.ts pruneRefsToLiveIds on the compaction-archive and zombie-reap paths) makes the session ref space SPARSE, but kernel error semantics treated every byRef miss as cross-session/typo ("(typo or wrong session)"). Models then probed endIds one number at a time — each probe a full round (up to 102s in the reporter's log). The error wording and gate message live in the kernel, so the host alone cannot fix them. #3302 is the declaration thread (human-opened, owner accepted with 接单).
What changed
Kernel (acp-kernel 0.0.130 → 0.0.131)
failing endpoints: endId=m10750per range; drops the two false assertions ("cannot come from an earlier compress in this session…"); adds "Do not probe for valid numbers." The marker phrase "every ref is unknown to this session" is kept verbatim — host detection (stream.ts, plugin.ts) and tests depend on it.session highest ref=(which invited upward probing) becomessession highest allocated ref=mNNNNN (the ref space is sparse — numbers at or below it are NOT necessarily allocated, so probing numbers will not find a valid one; use only refs acp_status lists).Host
Behavior changes (old → new)
endId="m10750" does not exist in this session (typo or wrong session) — run acp_status for current refs.→ three-class wording (above-frontier / in-band sparse gap / dead-snapped). Same tool-call shape, same errors[] positions.[warn] [acp-loop] compress probe family at round N: …log line (observability only, no control-flow change).Tests
Rebased onto current master (#3526/#3524/#3519/#3516 merges): only lockfile version-echo conflicts; kernel bump renumbered 0.0.128 → 0.0.131 to sit above master's 0.0.130, and the kernel lockfile drift left on master (0.0.129) is synced in the kernel commit. Re-verified on rebased head: typecheck clean, kernel targeted 49/49 (incl. dead-ref-split), host targeted 52/52.