Repository navigation
[PR] fix(dsh-drift): name the oversized top-level field in the egress-fuse breakdown + document the market-disable brick (#6957 #6956 #6968 #6972) - #6984
Conversation
The probe anchor PROXY_TOOL_AT=6 was calibrated on 2026-10-31 for #4521 (schedule {4,6,8,9}). The nudge scheduling has shifted again — nudge now lands at {3,5,11,14}. Re-calibrate the anchor to the next nudge-carrying request pair (5 → tool round, 6 → fold round). The fold/proxy-tool-round mechanics under test are unchanged. Closes: master-red on test (windows-latest, 22, 3) and (ubuntu-latest, 22, 1).
The probe's hardcoded request-index anchors (PROXY_TOOL_AT/FOLD_AT) broke every time the nudge gate's schedule shifted. The last recalibration (245ecb1) was measured on a direct local run (timestamps ON by default since #4313), but CI runs the suite preload pin BILI_MESSAGE_TIMESTAMPS="0" (timestamps OFF) — a different wire shape, a different schedule (no nudge at index 5) — so it passed locally and failed on every CI shard. Root-cause fix instead of another anchor whack-a-mole: - Arm the fold on the first request carrying the ephemeral nudge with >=11 tagged refs; fold on the re-request after the acp_status round. The probe now materializes the #2929 scenario wherever the schedule places it. - Pin compress.messageTimestamps:false so the probe's wire shape is hermetic regardless of how the suite is launched (matches the CI preload pin). Supersedes the 245ecb1 recalibration. Verified: passes with and without the preload pin, same deterministic schedule (nudge at inputs[7], fold at inputs[8]).
…6957) The #554 guard meter splits the outbound body into messages/tools/system/other, but the 'other' bucket was an opaque aggregate — a 1.6M-token 'other' (#6957, the dsh→official-DeepSeek wire put the mass in a top-level field bili's messages-only compression can never touch) told the operator a dimension was oversized without saying WHICH field, so the doom message's 'trim the oversized dimension' was unactionable and the session sat in an egress-fuse dead loop. estimateRawBodyBreakdown now tracks the top-level field(s) carrying the 'other' mass (otherTop, sorted desc, exhaustive over the bucket) and measuredBreakdownClause names the top-3 in the fuse/doom messages when 'other' carries real mass. Additive: total/messages/tools/system/other are unchanged, so the existing bucket tests and the regex-anchored doom-message tests keep passing. Also documents the #6956 market-disable path in dsh.bundle.patch.yml: the dsh plugin-market 'disable' toggle kills BOTH entries (bili-native AND the gate) at once, so the gate service never registers, the presets' inject latch is unsatisfiable, and the host reports preset-ptc as not-found, bricking new-conversation init. That is a DSH-side defect (an unsatisfiable inject must degrade, not hang); the supported off-switches are disabling bili-native only (#3662) or removing billion-context from bundles (#6972). Closes #6957
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.10502-pr.6984.1bddb3fThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr6984.tgz
npm install -g packageInstall instructions are refreshed on each push. |
[bot] 🏷 查重: 不重复 — 镜像 open [PR] 行中仅本条指向 dsh-drift 聚合,无并列 PR;上游 PR #6984 即本线程唯一修复 PR。 Review of PR #6984 (head
|
[bot] 🏷 CI 状态更新(head |
Summary
Root-cause batch for the dsh-drift aggregation (e-work #6983 / GitHub #6980): the dsh lane does not survive host-side state changes (plugin disabled, supplier switched, panel fallback, uninstall). This PR lands the in-repo fixes and documents the DSH-side asks.
Per-issue breakdown
otherbucket was an opaque aggregate. A 1.6M-tokenother(the dsh→official-DeepSeek wire put the mass in a top-level field bili's messages-only compression can never touch) told the operator a dimension was oversized without saying WHICH field, so the doom message's "trim the oversized dimension" was unactionable and the session sat in an egress-fuse dead loop.estimateRawBodyBreakdownnow tracks the top-level field(s) carrying theothermass (otherTop, sorted desc, exhaustive over the bucket) andmeasuredBreakdownClausenames the top-3 in the fuse/doom messages whenothercarries real mass. The bricking itself (the huge top-level field) is a DSH-side wire issue — the diagnostics make it identifiable.inject [biliBasicCompactionPolicy]latch is unsatisfiable, and the host reportspreset-ptc(the default) as not-found, bricking new-conversation init. That is a DSH-side defect (an unsatisfiable inject must degrade, not hang). The in-repo surface is a note indsh.bundle.patch.ymldocumenting the supported off-switches (disable bili-native only, [dsh] Disabling the plugin permanently bricks dsh session creation - the bundle patch inject gate has no fallback (0.1.199 / dsh 0.2.1-rc.2) #3662; or remove from bundles, DSH: uninstalling billion-context permanently bricks existing long sessions — no downgrade path from bili-only history #6972).sessionOursgate reado.viaFallbackbut the server sendsfallback; the field never matched, so the gate never fired and the iframe navigated to the most-recently-active session. [PR] fix(dsh): read the status wire field fallback, not the internal viaFallback #6971 corrects the client read.Behavior change
(other: <field> ~N, …)suffix when theotherbucket carries real mass. This is operator-facing (the dsh UI error), not model-facing. No wire, config, or persistence change. Thetotal/messages/tools/system/otherbreakdown values are unchanged (additiveotherTopfield).Verification
tests/side-request-isolation.test.ts: newotherTop+measuredBreakdownClausetests (both directions: field named when mass present, no suffix when absent).tests/raw-body-walk-depth.test.ts:otherTop: []added to the deepEqual expectation.tests/issue4079-egress-window-fuse.test.ts+tests/issue4185-identified-fresh-forward.test.ts: pass (regex-anchored doom-message assertions unaffected).tsc --noEmitclean.Related #6956 #6957 #6968 #6972