Repository navigation
[PR] fix: restore lost config-docs seed for rollout.features.pluginLaneServerHistory (docs-sync red on master) - #4534
ranxianglei wants to merge 1 commit into
Conversation
…aneServerHistory (docs-sync gate) The PR hand-wrote the pluginLaneServerHistory row into the generated param-ref blocks of CONFIGURATION.md / CONFIGURATION.zh-CN.md without adding the matching entry to website/config-reference/rollout.yaml, so gen-config-docs regeneration deleted the rows and git diff went red. Add the seed entry (the sanctioned source of truth), regenerate, and commit the generated state. Regeneration normalizes the ZH default cell from 0(关) to 0 (off) — the generator has one default field per entry, and every sibling ZH row already carries its English default — and drops backticks from the descriptions, which the seed validator forbids. Also adds the BILI_ROLLOUT_PLUGIN_LANE_SERVER_HISTORY row to both env-map tables.
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.5470-pr.4534.4446c8fThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4534.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm-qwen/qwen3.8-27b) 查重: 不重复 —— 本 PR 正是 #4533 下立项的修复 PR(分支 这是对我自己先前所立 PR 的复核唤醒:正文缺 注意:master 已前进( 标签: bug + scope/ci + p2(CI 门禁缺陷:阻断所有 PR 合入流水线,不影响终端用户使用)。 |
(ai: vllm-qwen/qwen3.8-27b) 结论:duplicate of #4524 —— 本 PR 的修复已经原样合入 master,合并本 PR 是纯 no-op,建议直接关闭、不要合并。 核查结果(全部实测)
结构化八问
本次执行的动作
收工判定:#4534 冗余,可关;master docs-sync 绿灯已由 #4524 恢复,无需任何进一步代码动作。 |
(ai: vllm-qwen/qwen3.8-27b) 重复判定:duplicate of #4519(等价修复已在 #4519 分支上)。
|
(ai: vllm-qwen/qwen3.8-27b) 补充一条(供 owner 判断,不另立项——按规则这属于自动立项 issue 分析中的发现,先写评论等人决定):本 PR CI 里红的 7 个 test shard 与本 PR 内容无关,是 CI runner 侧既有的非确定性 flake。 证据:
是否把「#3325 守卫在 CI 里误触发」单独跟踪,由你决定;本 PR 侧无动作(等关闭即可)。 |
|
(ai: zhipuai-lb/glm-5.3) 目标 issue #4533 已关。列车审查确认不再需要,关单。 |
What & why
Since merge
aeea173a4(PR #4505, 2026-10-24 ~10:06Z), master itself fails the docs-sync gate:CONFIGURATION.md/CONFIGURATION.zh-CN.mdcarry the hand-writtenrollout.features.pluginLaneServerHistoryrow, but the matching seed entry was never added towebsite/config-reference/rollout.yaml, so regeneration deletes the rows and the drift diff goes red. Consequence: every open PR's merge commit fails docs-sync and its full test matrix cascade-skips (thetestjob needsdocs-syncunderif: !failure()) — e.g. PR #4509, where every other gate was green.The fix for exactly this red was prepared during #4505's PRE-MERGE review (commit
4d9ff5a1f, validated there with the CI-parity commands — see #4505 floor 9) but was dropped by the final re-cut of the branch before merge (merged heada7fd378carries no seed entry). Tracked in #4533.Fix
Cherry-pick
4d9ff5a1fverbatim onto current master: add the seed entry (key/type/default/env/group/desc_en/desc_zh — the sanctioned single source of truth) + commit the regenerated doc state. Regeneration normalizes the ZH default cell0(关)->0 (off)and drops backticks from descriptions per the seed validator — the same normalization already disclosed in the #4505 thread.Config surface
No change — this only repairs the documentation ledger for an EXISTING key/env (
BILI_ROLLOUT_PLUGIN_LANE_SERVER_HISTORYalready exists insrc/rollout.ts). The seed file feedsgen-config-docsonly; zero runtime effect.Verification (CI-parity commands, local)
node tools/gen-config-docs.mjs generate-> "wrote 10 blocks from 294 seed entries", i18n okgit diff --exit-code -- CONFIGURATION.md CONFIGURATION.zh-CN.md website/main.js website/docs/index.html-> cleannode tools/gen-config-docs.mjs check-coverage-> pass (env name lands in the expected dynamic-names notice column)Full regression = remote CI.
Fixes #4533