Repository navigation
[PR] chore(branch): land 40 single-purpose fixes as one history-preserving batch (wave 5) - #6677
Merged
Merged
Conversation
Register the process-spawning zstd regression in LIVE_FILES so the CI runner can start the test matrix. Append the entry to preserve existing zone slots; the child changes only its own zlib exports and binds no sockets. The actual CI runner's global registration check and all 7 zstd cases pass locally. Typecheck, build and diff checks also pass.
Retain the upstream pack-install and CI-janitor entries at their existing slots, then append the zstd fallback regression. The original decoder, benchmark and regression test blobs are unchanged. On the merged tree, the actual CI runner passes its global registration check and all 7 zstd cases. Full typecheck, production build and net diff checks pass.
…st (#6502) The null-body test boots the full inline engine (config + sqlite state) but, unlike its sibling inline-streaming.test.ts, did not redirect the XDG dirs, so a developer run would touch the real ~/.config/billion-context and state. Pin the same hermetic pattern and restore the env in the after hook.
…operty idiom) The fix (#6500) added Object.hasOwn to the intermediate-segment traversal but left the adjacent leaf check on Object.prototype.hasOwnProperty.call. Both are functionally identical own-property checks in the same function; normalize to the single modern idiom so the deletion path reads uniformly.
…ent limit (#6490) Same mechanism as the reconciliation fix in this PR: Math.max(...ptrs) spreads the session's full canonical-pointer list (one entry per settled canonical message) into a single call, which trips V8's argument-spread limit (~125K-130K args on Node 22/24 x64) -> RangeError. The error is caught and only logged as a warn, so the failure is silent: the pointer list stops advancing and every later turn re-parses rows from the stale max pointer instead of the fresh tail. Replace the spread with a two-argument reduce (initial 0 - pointers are verified non-negative by readCanonicalPointers) and export the function for the regression test, which pins 150,000 pointers: pre-fix it fails with the RangeError warn, post-fix it passes and the upkeep reads rows after the highest pointer.
The CI preload selects legacy storage, so the canonical-pointer fixture must opt into the unified store before setting session extension data. Restore the prior mode and close the SQLite handle before removing its temporary directory, including on Windows. Retain the existing canonical-pointer fix and integrate current master.
This was referenced Nov 14, 2026
Contributor
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.1195-master.3858b69 # this exact build
npm install -g billion-context@master # always the newest merged build
|
This was referenced Nov 14, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
One history-preserving batch landing Afloat16's 40 open single-purpose fix branches (each was a 1-commit PR with its own hermetic test). Each branch is pulled in as a real merge commit — original authors, commit messages, and history stay intact; no squashing, no cherry-pick rewrites.
Merge order follows the review sequence; the one textual conflict (
scripts/live-files.mjs, two adjacent live-file registrations) is resolved as the union of both entries.Contents (branch → issue)
Verification
node:testcoverage).tsc --noEmit: clean.sessions.hardMaxBytes(Windows, 0.1.210) #5403/[Bug][dsh] Plugin lane performs a full re-parse and resends the entire body every round (81 MiB → hundreds of MB AST), w | [Bug][dsh] plugin 车道每轮全量解析重发 body(81 MiB→数百 MB AST)是 #5403 OOM 的生产者:用水位线断言替换逐条复核,服务端只解析新增尾段 #5418 watermark suite, run locally on node 22.23.4 with the exact CI preload set: 376/376 pass.Closes #6483 #6486 #6488 #6490 #6493 #6495 #6497 #6499 #6501 #6503 #6555 #6558 #6562 #6565 #6570 #6573 #6576 #6578 #6580 #6582 #6584 #6590 #6594 #6596 #6598 #6600 #6601 #6605 #6607 #6609 #6610 #6613 #6616 #6614 #6620 #6621 #6624 #6625 #6628 #6629