Repository navigation
[PR] storage: GC archive as one append-only JSONL log (follow-up to #3911) - #3927
Merged
Merged
Conversation
Sessions are small and numerous — one export file per archived session would spray tiny files across the archive dir. One archive.jsonl holds every archived session as one JSON line: append on archive (crash = at most one truncated line, which the restore reader skips), rewrite without the restored session's lines on restore. Docs + test updated.
Contributor
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.4670-pr.3927.0c85568This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr3927.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Owner
Author
(ai: vllm-qwen/qwen3.8-27b) 查重: 不重复。检索 open+closed issue/PR 均无其他条目覆盖「archive 单文件 JSONL 日志」这一格式变更;本 PR 是 #3911(已合并)在合并边界处漏掉的后续提交,与 #3911 本身不重复——#3911 已落地的是 per-session 导出文件方案,本 PR 将其替换为单一 append-only 收到 [PR] 通知,这是已完成的工作,我不重做:正在拉取分支 |
added 2 commits
October 20, 2026 15:31
…g format (#3927 review) The JSONL switch updated CHANGELOG/CONFIGURATION(en)/yaml seeds but left three spots describing the old <archiveDir>/<sessionId>.json layout: the archiveSession docblock (now also orphaned above the method by the ARCHIVE_LOG_NAME insertion), process.yaml desc_zh, and the matching CONFIGURATION.zh-CN.md row. No behavior change.
…estores (#3927 review) The single-log design promises a crash mid-append leaves at most one truncated line which the restore reader skips, but only the happy path was staked. Negative case now pinned: a partial trailing line does not block restoring another session, the restore rewrite drops it (safe — the append precedes the DB sweep, so its rows were never released), and restoring the crashed session itself honestly reports export-missing.
Contributor
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.652-master.8f98078 # this exact build
npm install -g billion-context@master # always the newest merged build
|
This was referenced Oct 20, 2026
This was referenced Oct 20, 2026
Closed
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.
Follow-up to #3911 (merged without this commit — it was pushed right at the merge boundary): the storage-review change to the GC archive format.
What: archive/GC no longer writes one export file per archived session. Sessions are small and numerous; a file per session would spray tiny files across the archive dir. Archiving now appends ONE JSON line per session to a single append-only
archive/archive.jsonl(a crash mid-append leaves at most one truncated line, which the restore reader skips), and restore rewrites the log without the restored session's lines. No per-session files, ever.UnifiedStore.ARCHIVE_LOG_NAME = "archive.jsonl";archiveSessionappends,restoreArchivedscans lines (skips malformed) and rewrites without the restored ids, re-archive appends fresh.Everything else in #3911 is untouched. CI runs the full matrix on this PR.