Repository navigation
[PR] docs: record the memory & render three-mechanism stack (#4788/#3756/#5418) + correct stale droppable-fields text - #5475
ranxianglei wants to merge 3 commits into
Conversation
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.8938-pr.5475.23c4e27This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr5475.tgz
npm install -g packageInstall instructions are refreshed on each push. |
eb3a55d to
2d10415
Compare
(ai: vllm-qwen/qwen3.8-27b) 查重:不重复——本线程是 [PR] 审核帖(对应 GitHub PR #5475),检索 open/closed issue 与近期 PR 无并行的同类文档工作项;本 PR 本身即 #5474/#5403/#5418 讨论的文档收敛产物。 标签: 审核结论:可合(等 CI 绿)逐条核对了新节与 CONFIGURATION 更正在代码/版本线上的每一处事实断言,发现 1 处事实错误 + 1 处悬空引用,均已直接修进 PR 分支(两个独立标注 commit,见下)。其余断言全部验证通过:
已推送到 PR 分支(rebase 到当前 master
分支头现为 结构化八问
收工判定:内容正确性已过审(含两处勘误修复),等新头 CI 绿即可由 owner 合并;agent 不合并不关单。 |
|
(ai: vllm-qwen/qwen3.8-27b) APPROVE — docs-only PR, and every load-bearing claim was re-verified against Correctness (verified, not assumed)
Behavior / regression: none — pure wording correction + missing-row completion + a new doctrine section; no logic / config-semantics / wire change. 已顺手修: 记录为评论而非正式 Approve 按钮:GitHub 禁止批准自己开的 PR(本 PR 作者即执行审查的账号)。上方结论 APPROVE 有效,待 owner 正式 approve/merge。 |
(ai: vllm-qwen/qwen3.8-27b) review-worker-r1 独立终审完毕:APPROVE。逐条重核了全部事实断言并对照 |
(ai: vllm-qwen/qwen3.8-27b) 这条是我上面那条 APPROVE 审查结论经 upstream-sync 回灌到本线程的镜像,不是新指令。状态不变:终审完成、APPROVE,顺手修 commit |
… text into docs/ layout (#5920 move)
4480ed6 to
186fe8b
Compare
(ai: vllm-qwen/qwen3.8-27b) Conflict resolved & pushed (attempt 1/3). Branch Why it conflicted. The branch was cut 2026-11-01 at How each hunk landed (all in the relocation commit
No behavior change: comment-only code edit + documentation text. No config surface, wire, or persistence touched. Check states come from the mirror cache (its entry for this PR pre-dates today, so I live-read PR state once via the API rather than assert from memory); CI verdict on the new head is still pending — if any lane goes red, the next auto-fix attempt handles it. 七问(CI 冲突处理)
判定:冲突已清零,PR 可进入正常 CI/评审流程;无新增配置、无需决策项。 |
(ai: vllm-qwen/qwen3.8-27b) Status after restart — nothing outstanding. The conflict fix completed before this session dropped: branch CI now verified live (mirror cache, fetched 21:20 local, head |
[ework] CI fix verified green ✓ |
(ai: vllm-qwen/qwen3.8-27b) Status: conflict already resolved & pushed — this run verified it. When I woke, the PR head (
Nothing left for me to push. Awaiting CI completion + human review/merge (merge is human-only). 七问(中文)
判定:冲突已解决、最终提交已推送、CI 在新 head 上运行中(44/55 绿、11 个测试分片进行中); |
三层成本来源(生产/呼吸/组装)此前散落在代码注释与各自的 issue 里,#5403 的讨论过程证明混读会带偏 triage。本 PR 只写文档,不动任何代码/配置语义:
sessions.hardMaxBytes(Windows, 0.1.210) #5403 关闭所需的两条腿写明。BILI_SESSION_RESIDENT_HARD_MAX_BYTES说明块里「media content store are non-droppable by design」一句已过期([Performance] v0.1.208 long sessions exceed 2 GiB memory and spend 14–22 seconds in local processing #4788 phase 2 起 content store 可卸、sessions.contentStorePin是逃生门),更正并补上已知局限指向 [Bug][dsh] #4788 D2 disk-proof gate never aligns while saves keep lagging — hard-cap warning fires but reclaim stays zero (#5403 symptom 1) #5474。BILI_SESSION_RESIDENT_HARD_MAX_BYTESWhy-it-exists 条目(en/zh 对齐)。config surface:无新增/改名/改语义字段,仅文档措辞更正与补齐。
References #5474 (p1, disk-proof gate 缺陷跟踪)、#5403、#5469。