Repository navigation
[PR] feat: observability root cause — nudge recovery rate in web chart/report + first-request dsh coverage readout (#6729 #6770) - #6779
ranxianglei wants to merge 0 commit into
Conversation
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.10508-pr.6779.9b9caccThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr6779.tgz
npm install -g packageInstall instructions are refreshed on each push. |
[bot] 🏷 Status report — PR #6779 (root-cause aggregation: #6729 nudge-recovery visibility + #6770 first-request dsh coverage readout). I pulled head Commits (5, on current master
Diff: 14 files, +879/−19. No CI (live, head Labels: Conclusion: the branch matches the PR description, CI is green on the current head, and the base is current master. Nothing to fix — ready for you to merge. After merge, #6745 and #6772 can be closed (yours to close). |
8612cab to
41a113e
Compare
(ai: vllm-qwen/qwen3.8-27b) PR #6779 — merge conflict resolved (rebased onto current master), pushed. What I did this run:
Reviewer follow-up (non-blocking, for the PR author): one semantic interaction between this PR and master's newer #6531 (rejected-nudge re-arm). 七问:
收工判定: 冲突已解决并推送,PR 恢复可合并状态(待人工 review/merge);CI 在新 head 上运行中,结果出来前不宣称绿。 |
41a113e to
42edd38
Compare
(ai: vllm-qwen/qwen3.8-27b) Conflict resolved — PR is mergeable again (head Master moved 68 commits since the last rebase, and the decisive change: member PR #6745 was merged into master (merge commit Resolution (union of intent):
What the PR now carries (diff vs master, 4 files, +154/−9):
Verified locally on the pushed head: Live state (mirror cache was 2 days stale, so verified with a single GitHub API GET, as permitted): Note for you (no action taken by me): the PR body still says "supersedes #6745 and #6772 (both left open; closing is yours)". #6745 is now closed (merged). #6772 is still open carrying the same #6770 content — after this PR merges it becomes a duplicate; closing it is yours to do. Also, the #6531×#6729 ledger-interaction finding I flagged in the previous run (a 4xx-rejected nudge keeps its prepare-time "n" event in the recovery ledger) now lives in master's merged #6745 code, not in this PR's diff. 八问
收工判定:冲突已解、本地验证通过、PR 恢复可合(待人工 review + CI 全量),本 lane 工作完成。 |
(ai: vllm-qwen/qwen3.8-27b) No action needed this run — the "dirty" blocker is stale; the PR is live-verified clean. I verified against live sources in this run (the mirror cache for this PR is 2 days stale,
No conflict exists between the branch and its base, so there is nothing to rebase or fix. The wake appears to have been generated from a pre-rebase snapshot. CI is running its one full pass on 八问
收工判定:核实完毕,PR 无冲突、无待办;等待 CI 全量结果与人工 review,本 lane 本轮无事可做。 |
42edd38 to
04ecbb4
Compare
Root-cause fix: observability (aggregation of #6729 + #6770)
This PR is the single root-cause fix for the observability root-cause batch — two "diagnostic data exists but has no usable exit" gaps:
Feature: show nudge-recommended vs actually-folded tokens per fold (recovery rate) in the web panel chart and session report | 功能:web 折线图与 session 报告显示每次压缩「推荐 vs 实际折叠」回收率 #6729 — nudge-recommended vs actually-folded (recovery rate) is invisible.
The Every compression only trims a little: the post-fold floor ratchets up and a 1M-window session ends at 212K without recovering | 每次压缩只降一点:压缩后的地板越压越高,1M 窗口会话涨到 212K 不回落 #6720 investigation showed the model often folds only part of a nudge-recommended range, so the "post-compression floor" ratchets up turn after turn — but the recommended amount and the actually-folded amount had no visualization anywhere, so it took 30+ lines of log reading plus source reconciliation to pinpoint. This adds, per fold:
Persistence goes through the existing sqlite unified storage (session.metadata ledger JSON blob, sparse — the field is absent until the first nudge injection after upgrade); no backfill for pre-upgrade sessions; no new config; kernel/ untouched.
[Diagnosis] Compression coverage reading for #3962 is unavailable on device: profileContext.startedBundles not detected | [诊断] #3962 的压缩覆盖读数在设备上取不到数:profileContext.startedBundles 探测不到 #6770 — the dsh.bundle.patch.yml gates four preset ids that may not exist — the miss is only visible in the loader log #3962 compression-coverage readout had no reachable exit.
dshCompactionGateTelemetry().coveredonly ever rode the durable profile-bundle note, which stays silent whereverprofileContext.startedBundlescannot be read (observed on both a desktop dsh build and the dsh-go runtime) — the reading was unreachable on every host checked. This emits the reading once per process on the first routed request via the already-confirmed[dsh-client]channel. The shared formattercompactionCoverageText()keeps the profile note byte-identical.Provenance
Cherry-picked with
-x(authorship preserved) from the two CI-green member PRs, whose directions match the owner's 2026-11-14 rulings:[dsh-client]line in bili.log, once per process (dsh.bundle.patch.yml禁用自动压缩在 web profile 下静默失效 #1772 paradigm), plus the once-per-process flag reset hook.This PR supersedes #6745 and #6772 (both left open; closing is yours).
Verification
Behavior changes
None beyond the new observability surfaces: one new
[dsh-client]log line per process on the first routed dsh request; a new recovery section in the web session chart and the downloadable session report. No config surface, no wire/protocol change, no kernel/ change, no persistence migration (the recovery fields ride the existing session.metadata ledger blob).Fixes #6729
Fixes #6770