Repository navigation
[PR] fix(codex): Codex lane minor fixes roundup #3 — WS error object + marketplace containment + Google part ordering | fix(codex): codex 车道小修合集第三辑 —— WS 错误对象 + marketplace 收容 + google part 序 - #5971
Conversation
…gle targets (for #5397, closes #5392) kernel-change: make normalizeGoogleUserPartOrder/coreToGoogle model-aware so Claude-through-Google targets keep tool_result-first part order. The host side cannot solve this: the offending reorder happens INSIDE the kernel codec (coreToGoogle's flushUser), and the stable text-first partition is non-invertible, so no host-only workaround exists. Owner approval via decision request #5393 (option A). Kernel version 0.0.188 -> 0.0.189 (master was already at 0.0.188 past this PR's 0.0.175->0.0.176 base bump).
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.8690-pr.5971.59b6df5This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr5971.tgz
npm install -g packageInstall instructions are refreshed on each push. |
The PR bumps kernel/package.json 0.0.188 -> 0.0.189 (required by the Kernel Boundary for the kernel/src/wire/google.ts change) but left both lockfiles at 0.0.188. Regenerated with npm install --package-lock-only (matching the lock-sync CI job) so the embedded kernel entry in the root lock and the kernel lock's own version line agree. Mechanical lockfile sync only — no dependency or source change. Fixes #5971
(ai: vllm-qwen/qwen3.8-27b) Fixed the Root cause: the PR bumps Fix: regenerated both lockfiles with the exact command the job uses (
No dependency, source, or behavior change — pure lockfile sync. Pushed to Verification: reproduced locally first (ran the job's exact commands → identical 3-line drift), then confirmed live: on head 审查结论(结构化)
判定: |
(ai: vllm-qwen/qwen3.8-27b) [PR] #5971 审核结论:代码与行为均通过,已就地修复 2 处引用错误;剩 CI 重跑 + owner 人工合并(kernel-change = human-only 档)。 查重不重复 —— 本 PR 是该批工作的唯一 open PR;三个来源 PR(#4624 / #5586 / #5397)均已 closed-not-merged,被本合集 superseded(正常)。 独立审核过程(未复用 issue/来源 PR 侧结论)
发现并已就地修复的问题(不只报告)
行为变更清单(old → new,全部有意,Deliverables 第 4 条披露)
八问
合并判定代码层面 ready,剩两件事:① CI 在新 head |
(ai: vllm-qwen/qwen3.8-27b) CI 更新(实时核查):head PR 现态:open / mergeable,只等 owner 人工合并(kernel-change = human-only 档;合并前请顺带确认 #5391 option A 批准)。 |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.1098-master.ec4b9f7 # this exact build
npm install -g billion-context@master # always the newest merged build
|
…sis, ranxianglei#5949 relocated fold summaries, ranxianglei#5971 codex lane fixes, ranxianglei#5961 compress-burst loop fix Advances the base from 848f59b to 33d4951 (20 commits, 43 files). The only overlap with this lane is src/pipe-free relay.ts; upstream touched the WS oversize diagnosis, outbound stamping and continuation refetch paths, while the lane's non-streaming compact egress sits at src/server/relay.ts:2103. Both survive — the auto-merge needed no manual resolution. Notable upstream commits adopted: - cc1e240 kernel: relocate-compress v2 — summary text moves to the fold point - e03cc4b Stop the compress-burst loop: ack fold-point pointer echoes - 725084b feat: context analysis — init size, nudge cadence, harvest acceptance - 3fcf41e fix(codex): answer WS-lane failures with object error frames (ranxianglei#4601) - 86aae0d fix(google): keep tool_result-first part order for Claude-through-Google - d3fab0d fix(codex): keep marketplace Git repos inside the codex overlay tmp - 50e4cdc fix(ci): sync root + kernel lockfiles to acp-kernel 0.0.189
三个已评审小修合并送审(一 PR 一合)
kernel-change 声明(#5397 携带,原文)
kernel-change: make
normalizeGoogleUserPartOrder/coreToGooglemodel-aware so Claude-through-Google targets keep tool_result-first part order. The host side cannot solve this: the offending reorder happens INSIDE the kernel codec (coreToGoogle's flushUser), and the stable text-first partition is non-invertible (an interleaved[fr,text,fr,text]collapses to[text,text,fr,fr]), so no host-only workaround exists. Owner approval via decision request #5393 (option A).冲突处理(合入 master 848f59b 时)
src/server/relay.ts:master 已在 5 处 continuation-retry 调用加model: throttleModel(KeyRing 隔离),[PR] fix: keep tool_result-first google part order for Claude targets (#5392) #5397 在同批调用加model: prepared.model ?? prepared.google?.model(nudge 保序)。取并集:model: throttleModel ?? prepared.google?.model(p 变体同式),单键;throttleModel 已含 prepared.model/body 派生,google 兜底垫底,两个消费方都满足。kernel/package.json:本 PR 基线是 0.0.175→0.0.176,master 已到 0.0.188 → 按纪律 bump 到 0.0.189。预检(本地,2026-11-09)
npm run buildOK,tsc --noEmit0 错Closes #4601
Closes #5584
Closes #5392