Repository navigation
[PR] feat: windowed render source (D5-5) + view-domain judge tailStart (#4241 teeth regression) [rescue of #4584] - #4586
Merged
Conversation
regression) - store: messageIdRows (seq+msg_id, no bytes) + uncoveredRows(intervals) — covered rows' bytes are never read, so covered-row corruption can no longer degrade a live render - snapshot-render buildView: block anchoring switches to the msg_id column, two-phase load (light rows for anchoring/chain, bytes only for uncovered), full-load fallback on the race window - judge: snapshotRenderTailStart now records the VIEW-domain tail start (view rows - tail count) — the judge indexes judgeBaseline (the rendered view) with it; the client-domain join could point past the view's end and the judge validated nothing (vacuous clean — blinded the #4241 teeth after the T1-consolidation train) - tests: d5-5-render-window (zero full loads + covered corruption tolerated + outbound complete) + issue4241 teeth now drops the last client tail row (exitCores.length - 2, the trailing nudge occupies the final wire slot)
Contributor
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.825-master.cd92b0b # this exact build
npm install -g billion-context@master # always the newest merged build
|
Contributor
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.5537-pr.4586.37f861fThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4586.tgz
npm install -g packageInstall instructions are refreshed on each push. |
ranxianglei
pushed a commit
to z0d0dOr/billion-context
that referenced
this pull request
Oct 24, 2026
…nxianglei#4316-ledger vs bounded-reads in backend/store; drop superseded ranxianglei#4241 relay hunk — master's D5-5 view-domain tailStart (ranxianglei#4586) is the root-cause fix)
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.
这是 #4584 的救援重开
#4584 被合并时 base 还指着 `2026-10-24_seq-ledger-pr3`(已合并的旧基),内容落在那个分支上没进 master。本 PR = 同一 commit f034184 cherry-pick 到 master(8a1df61),内容逐字节相同。
内容
D5-5 渲染源窗口化(storage-review 唯一性能硬卡)
判官 tailStart 视图域修复(master 回归,T1 合车 #4525 后 #4241 牙齿红)
验证
d5-5 1/1 + issue4241 1/1(cherry-pick 后复跑)+ snapshot-render 12 + snapshot-shadow 5 + storage-unified 14 + corpus 9 + full-flip 10 + incremental-lane 24 + msgid-lane-flow 5 + seq-interval-lane 1 + plugin-fork 49 + issue3250 5 + media-cas 3;tsc 0。
kernel-change: none(纯 host src/)