Repository navigation
[PR] chore(branch): land 14 single-purpose fixes as one history-preserving batch (waves 7+8) - #6758
Conversation
…into batch8-wave8
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.10023-pr.6758.20f615eThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr6758.tgz
npm install -g packageInstall instructions are refreshed on each push. |
… test buildSessionCacheReport stamps generatedAt: Date.now() at build time. The batch/individual parity test deepEqual'd two reports built 1ms apart, so it flaked whenever the two builds straddled a millisecond boundary (CI red on ubuntu 22/1 and windows 22/4: generatedAt ...904 vs ...905). Normalize generatedAt to 0 before the comparison — it is a generation-time marker, not part of the ledger/report parity being asserted. All ledger data already matched; only the wall-clock field differed.
(ai: vllm-qwen/qwen3.8-27b) Review of batch8-wave8 — 14 single-purpose fixes (waves 7+8) 查重: Not a duplicate. This supersedes #6723 (batch7-wave7→master, still open — needs owner close, I can't close PRs) and #6755 (accidentally merged into batch7-wave7, already closed). All 14 source PRs (#6715 #6717 #6721 #6724 #6726 #6732 #6734 #6736 #6737 #6740 #6741 #6744 #6746 #6749) are open and auto-close on merge via their Structure verified: branch Code review — all 13 source files verified, each fix is single-purpose and correct:
CI was red on 2 shards — diagnosed and fixed (not a code regression):
8问 (structured review):
行为变更披露(有意,非回归): 判定: 14 个修复全部正确、行为保持(或有意修复);唯一 CI 红是 flaky 测试,已修并 push。新 head CI 转绿后即可合。待办:#6723 仍需 owner 关闭(我无权关 PR)。 |
(ai: vllm-qwen/qwen3.8-27b) CI update: now fully green on the fixed head PR is ready to merge. Only remaining item: #6723 still needs owner close (I can't close PRs). |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.1199-master.f21b601 # this exact build
npm install -g billion-context@master # always the newest merged build
|
…fted-name-leak Syncs the lane onto master f21b601 (PR ranxianglei#6758, batch8-wave8: 30 commits, 32 files). One file overlapped with the lane and auto-merged cleanly: - src/storage/mysql.ts: upstream batched the `content` hydration in `readMessagesWithHashes` behind a CHUNK of 500 and inlined the bytes into the metadata SELECT via `LEFT JOIN content c`. The lane's only touch there is the `export` on MYSQL_SCHEMA_VERSION (consumed by the migration-dedup test), which survives unchanged at line 77. Verified on the merged tree: kernel build 0, tsc --noEmit 0 errors, all five gates 0, config-docs fixed point holds (no drift), and the suites are green (issue5175 66/0, tag-echo 79/0, issue2190-degen-close 32/0, issue3905-announcement-tail 19/0, issue2303-draft-tail 14/0, notice-registry 5/0, persist-zstd 17/0, plugin-fork 58/0).
Supersedes #6723 and #6755 (which was accidentally merged into the batch7-wave7 branch instead of master). Head contains both waves: 14 of Afloat16's single-purpose fixes, each merged in with a real merge commit so every original commit and author is preserved in the first-parent history.
Wave 7:
| #6716 | 2026-11-14_linear-coverage-timestamps | #6715 | compression-receipt coverage times: the covered-id dedupe scanned the array per id (
covered.some, O(n²) on stamped 20k-message folds) → Map, boundary-ref resolution and "never invent a range" semantics unchanged || #6718 | 2026-11-14_frozen-message-whitespace | #6717 | frozen-snapshot message re-parse stripped ALL trailing blank lines from every body (content at the end of a message was silently eaten) and lost the ref marker when a body started with a blank line → only the single separator newline before the next header is removed; leading/trailing blanks survive verbatim |
| #6722 | 2026-11-14_linear-cache-usage-alignment | #6721 | cache-diff usage alignment: each usage sample re-scanned every request from the back (O(samples×requests) on 10k-request logs) → single forward pointer over the two sorted lists, same 50 ms admission boundary and stable ordering |
Wave 8:
| #6725 | 2026-11-14_jsonl-historian-null | #6724 | historian JSONL export crashed on a stored content of literal JSON
null(message.texton a non-object) → non-object rows now stay verbatim in full exports || #6727 | 2026-11-14_jsonl-ccr-originals | #6726 | full JSONL export dereferenced CCR placeholders to the indexed ENTRY metadata instead of the stored original bytes → resolve byRef→byHash, disk store fills gaps, corrupt/missing mirror keeps the placeholder |
| #6733 | 2026-11-14_join-message-content | #6732 | message readers decoded content with one content-store lookup PER ROW → metadata query stays separate, bodies fetched in bounded 500-row batches (sqlite JOIN for pointer reads, same on the mysql backend) |
| #6735 | 2026-11-14_keepalive-body-failures | #6734 | keepalive pings swallowed every
resp.text()error (a 200 with a truncated/gzip-mangled body was treated as a normal miss) → body read errors now use the fail-streak budget, 429 keeps first-response disarming, an old response cannot spend the replacement snapshot's budget || #6739 | 2026-11-14_keepalive-rotated-timers | #6737 | credential rotation deleted the registry entry but never cancelled the scheduled ping — the dropped snapshot stayed referenced until its old cadence fired →
disarm(..., "credential-rotated")|| #6738 | 2026-11-14_cache-diff-insertion-boundaries | #6736 | cache-diff "mid-insert append" misclassified inserting a WHOLE message between existing ones as a semantic append (byte shape is identical) → require same element count with exactly one span growing by the insertion; growth before the root array now reports preArray divergence |
| #6742 | 2026-11-14_usage-log-attribution-tags | #6740 | usage-log parsing attributed samples to the new logger's
[v=]/[sess=]tags (or a request scope) instead of the explicit session → strip logger tags, require the session tag directly before[acp-usage], never invent one || #6743 | 2026-11-14_nested-upstream-error-codes | #6741 | upstream alert errno extraction only read the outer
error.code— native fetch failures nest the errno incause→ walk the cause chain (depth-capped, cycle-safe), outer nonempty code keeps precedence || #6747 | 2026-11-14_linear-fold-registration | #6744 | batch fold registration re-scanned the whole fold list to close open records per block (O(folds×blocks)) → closeFrom cursor; batch/individual parity kept |
| #6748 | 2026-11-14_linear-handoff-capture | #6746 | handoff reply metering re-encapsulated the entire accumulated text on every delta (O(n²)) → incremental byte accounting with surrogate-pair junction correction; exact UTF-8 budget boundaries kept |
| #6750 | 2026-11-14_diagnostics-unicode-bounds | #6749 | diagnostics truncation used plain
slice, which can split a surrogate pair at the bound →safePrefixeverywhere the bound applies (log tails, config, conflict detail, topic) |Verification: as reported in #6723 and #6755 (per-PR added-line audits clean, tsc clean, 297 test assertions passing across all 14 touched test files on node 22.23.4 with the CI preload chain).
After this merges, the 14 source PRs become branch ancestors of master and close with their Closes keywords.
Closes #6715 #6717 #6721 #6724 #6726 #6732 #6734 #6736 #6737 #6740 #6741 #6744 #6746 #6749