Repository navigation
[PR] gate: add a one-time warmup round to the opencode lane to absorb the v1 CLI sqlite storage migration (guaranteed to trig | gate: opencode 车道加一次性 warmup 回合,吸收 v1 CLI 的 sqlite 存储迁移(容器每跑必中) - #3497
Conversation
…storage migration Fresh hermetic XDG (every container run) makes opencode v1 print 'Performing one time database migration, may take a few minutes...' inside the first timed turn — r5 lost the whole lane to it (13/13 red, zero upstream requests) while host calibration stayed green only because its storage dir was reused across runs. A disposable long-timeout turn before t1 absorbs the migration; failure is logged, non-fatal.
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.6200-pr.3497.e499995This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr3497.tgz
npm install -g packageInstall instructions are refreshed on each push. |
…lout) Bare cpSync of the billion-context package left zod unresolved once #3425's jimp made dist/index.js import it at module load: the lane's self-spawned proxy exited code 1 on every attempt and traffic silently went direct (uncompressed), failing 8 assertions. npm install --no-save of the tarball installs the candidate and its deps while keeping the dsh profile manifest untouched.
…ist-level P0s 8a772ac made the dsh setup npm-install the candidate tarball so its runtime deps (zod, pulled into dist by #3425's jimp) resolve. That is not a gate fix, it is burying the defect: the bare cpSync deliberately reproduces the real thin-install shape (no dependency tree beside the package), which is exactly how production dsh plugin installs ship. If dist/index.js requires an external package at module load, the lane must go red (self-spawned proxy dies, fold/nudge assertions fail) — that is the gate doing its job, not a lane bug to be absorbed. Reverting to the bare copy until the product-side fix (runtime dynamic import of jimp + dist "no static zod" build assertion) lands; after that, this lane doubles as the regression proof.
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) 查重: 不重复。 检索了 open+closed issue 与 PR(opencode 车道 / warmup / sqlite 迁移 / gate 矩阵等关键词):无其他条目修同一问题。相关但不同:#3416(车道矩阵跟踪 issue,本 PR 是它的修复项)、#3425/#3511(产品侧 dist 静态依赖 zod 的 P0——本 PR 里 dsh 裸拷 revert 指向它们,机制不同)。 开始审核 PR #3497(branch |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) 审核完成。查重结论见上一条(不重复)。以下是结构化结论。 1. 是什么问题:opencode v1 车道在容器里每次全红(13 条断言全灭、上游 0 请求)——全新 XDG 存储目录上,v1 CLI 首个回合前要跑一次它自己的 sqlite 一次性迁移("Performing one time database migration"),把 t1 的整个计时预算吃光。宿主机标定一直绿,是因为宿机存储目录跨次复用、迁移早就跑过。 2. 什么原因导致的:迁移开销是宿主 CLI 自己的启动成本,与 bili 无关;gate harness 隐含假设「第一个回合 = 纯净计时回合」,这个假设在全新容器里不成立(宿主机场景才成立)。修的是 harness 的假设,不是产品——层次正确。 3. 影响范围与严重程度:只动 4. 怎么修复的:runLane 加通用 5. 是否有回归问题:无。逐项审过既有行为:①其他五个车道都不定义 warmup → 钩子不触发,零变化;②opencode 车道下游消费点逐一核对——sid 捕获取 storage 里最新 6. 是否破坏缓存:不涉及(纯测试装置变更,不碰缓存/重试/游标/去重键逻辑)。 7. 是否改了设计方向:不涉及。 8. 是否引入了新的配置:没有。复用既有 有意的行为变更(披露):opencode 车道旧行为 = t1 即宿主首回合(容器里必被迁移吃光预算、车道恒红);新行为 = t1 之前多一个丢弃回合 → 车道恢复有效,代价是多 1 个上游请求 + 墙钟时间增加(实测 ~63s,最坏 ≤600s)。这是本 PR 的目的所在,PR 描述已披露。 审核中顺手修掉的小缺陷(独立 commit 状态备注:head 上标准 CI 全绿(test×5 shard、static-gates、各 guard、build-artifact、12 个 gate e2e workflow);plugin-lanes 矩阵本身是 workflow_dispatch-only( 判定:可合(等 GitHub 算完 mergeable 状态;建议 owner 直接合并,CI 与本次审核均通过)。 |
master window commits 293ae65/de5e03659 bumped kernel/package.json to 0.0.165 without regenerating the lockfiles; lock-sync re-resolution then rewrites the stale recorded versions (root 0.0.163, kernel 0.0.164) and fails. Pure recorded-version sync via npm install --package-lock-only; no dependency or semantic change.
…TS.md and the ranxianglei#5904 first-byte budget Upstream delta 48ee6a7..3ac3e95 (83 files, 20 commits). The substantive ones: - e3434a3 fix(ranxianglei#5904): phase-1 first-byte budget for upstream summary calls + watchdog/preflight logging - b4a4026 docs(ranxianglei#5904): regenerate config artifacts for upstreamFirstByteMs + ledger entry - 9492212 docs(ranxianglei#5904): align first-byte-knob comments and docs with shipped values - c7db020 fix(opencode): route host console chatter to bili.log and teach the config key (PR ranxianglei#5710, closes ranxianglei#5706) - 984d3dc fix(gate): opencode lane one-time warmup round for fresh storage dirs (PR ranxianglei#3497) - 8f1fca8 docs: live architecture hub + module pages + file-map CI guard - 2a15b5a docs: all 8 architecture module pages live - 44faff0 docs: slim AGENTS.md (KDD text to reference/design-decisions.md, triage table to reference/triage.md) - 6f4f248 docs: add docs/README navigation landing page, en+zh - 3ac3e95 Merge pull request ranxianglei#5917 Conflict surface: only the four generated artifacts, all auto-merged. The lane's chat row is still in the regenerated docs/configuration.md (line 294) after `node tools/gen-config-docs.mjs generate`, and the docs fixed point holds. kernel stayed at 0.0.187 and was rebuilt before measuring. Lane anchors intact: src/server/relay.ts:2070 still calls `pipePluginJson(toClient, res, undefined, prepared.protocol, ...)`, src/storage/mysql.ts:77 still exports MYSQL_SCHEMA_VERSION, symbols unchanged (stripDriftResidue 6, isDraftDump 6, containsRenderTagText 21, mayStartDegenerateRenderTag 6, DRIFT_BARE_MISMATCH 3, DRAFT_CLOSE_TAIL 3). Gates: tsc 0, four guards 0, gen-config-docs fixed point. Tests: issue5175 58/0, tag-echo 79/0, issue2190-degen-close 32/0, golden-storage-render 5/0, storage-engine-proofs 12/0, native-compact-terminal 1/0, issue4666 2/0, and the three new upstream suites: issue5904-upstream-first-byte 4/0, issue5706-opencode-host-console 2/0, issue1815-unknown-top-level-keys 5/0.
ai: zhipuai-lb/glm-5.3
两个 gate 车道修复,一个方向纠正(撤销自己上一版里的坑):
1. opencode 车道加一次性 warmup 回合(887ab70)
opencode v1 CLI 在全新存储目录上首跑要先建自己的 sqlite 会话库("Performing one time database migration…"),把第一个计时回合的预算整个吃光(容器里全灭、0 上游请求;宿主机绿是因为存储复用)。现在正式计时前先跑一个丢弃成绩的热身回合(600s 上限、失败非致命),实测 63s 吸收完毕。
2. dsh 车道撤销 npm-install 改回裸拷(1a9e8cd,撤销 8a772ac)
上一版曾把 dsh setup 从裸 cpSync 改成
npm install带依赖,理由是 #3425(jimp)让 dist/index.js 模块加载即 import zod、裸拷的自起代理起不来。owner 指正:这不是修复是埋坑。裸拷就是真实 dsh 插件安装的形状(包旁边没有依赖树),gate 车道就该红——dist 破了车道红 = gate 在干活。装上依赖把症状吸收掉,产品级 P0(dist 静态依赖 zod,违反「dist 零外部依赖」)就被藏住了。已改回,等产品侧修复(jimp 运行时动态 import + dist 禁静态 zod 断言,见 #3511 P0)落地后,这条车道正好当回归证明。影响面:只动 scripts/gate/(gate 测试装置),不碰产品代码。