Skip to content

[PR] fix: restore lost config-docs seed for rollout.features.pluginLaneServerHistory (docs-sync red on master) - #4534

Closed
ranxianglei wants to merge 1 commit into
masterfrom
2026-10-24_docs-sync-missing-seed
Closed

ranxianglei wants to merge 1 commit into
masterfrom
2026-10-24_docs-sync-missing-seed

Conversation

@ranxianglei

@ranxianglei ranxianglei commented Oct 24, 2026 •

Copy link
Copy Markdown
Owner

What & why

Since merge aeea173a4 (PR #4505, 2026-10-24 ~10:06Z), master itself fails the docs-sync gate: CONFIGURATION.md / CONFIGURATION.zh-CN.md carry the hand-written rollout.features.pluginLaneServerHistory row, but the matching seed entry was never added to website/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 (the test job needs docs-sync under if: !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 head a7fd378 carries no seed entry). Tracked in #4533.

Fix

Cherry-pick 4d9ff5a1f verbatim 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 cell 0(关) -> 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_HISTORY already exists in src/rollout.ts). The seed file feeds gen-config-docs only; zero runtime effect.

Verification (CI-parity commands, local)

  • node tools/gen-config-docs.mjs generate -> "wrote 10 blocks from 294 seed entries", i18n ok
  • git diff --exit-code -- CONFIGURATION.md CONFIGURATION.zh-CN.md website/main.js website/docs/index.html -> clean
  • node tools/gen-config-docs.mjs check-coverage -> pass (env name lands in the expected dynamic-names notice column)

Full regression = remote CI.

Fixes #4533

…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.
@ranxianglei ranxianglei changed the title fix: restore lost config-docs seed for rollout.features.pluginLaneServerHistory (docs-sync red on master) [PR] fix: restore lost config-docs seed for rollout.features.pluginLaneServerHistory (docs-sync red on master) Oct 24, 2026
@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-24_docs-sync-missing-seed (62c301a)

Latest build — install this exact version

npm install -g billion-context@0.0.5470-pr.4534.4446c8f

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Recent builds (commit → version)

commit version build
62c301a billion-context@0.0.5470-pr.4534.4446c8f build

Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr4534.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

查重: 不重复 —— 本 PR 正是 #4533 下立项的修复 PR(分支 2026-10-24_docs-sync-missing-seed @ 62c301a5d,#4533 floor 1 已贴链接);按失败签名(docs-sync 红 / rollout.yaml 缺 seed)检索 open+closed,仅 #4533/#4505/#4509 相关且均已互相链接。

这是对我自己先前所立 PR 的复核唤醒:正文缺 ework-agent-pr 标记(稍后补上),按 [PR] 流程处理——拉分支核对代码、确认 CI 状态、报告结论,不重做。

注意:master 已前进(c81c17d93 → 8ae56a010),我会复核该 diff 在最新 master 之上是否仍然干净(尤其生成文档四件套与 seed 文件是否被后续提交触碰),必要时 rebase。

标签: bug + scope/ci + p2(CI 门禁缺陷:阻断所有 PR 合入流水线,不影响终端用户使用)。

@ranxianglei ranxianglei added bug Something isn't working p2 scope/ci duplicate This issue or pull request already exists labels Oct 24, 2026
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

结论:duplicate of #4524 —— 本 PR 的修复已经原样合入 master,合并本 PR 是纯 no-op,建议直接关闭、不要合并。

核查结果(全部实测)

  1. 内容逐字节相同:本 PR 触碰的 3 个文件(website/config-reference/rollout.yaml、CONFIGURATION.md、CONFIGURATION.zh-CN.md)在 PR head(62c301a5d)与当前 master(8ae56a010)之间 diff 为空。master 上的对应修复来自 PR [PR] docs: restore dropped pluginLaneServerHistory seed row — unblocks docs-sync on master #4524(commit 8daae6716,「docs: add missing pluginLaneServerHistory config seed」)。
  2. 模拟合入 = 空操作:把 PR 分支 merge 到当前 master(未提交),merge 后树对 HEAD 的 diff 为空——合并只会产生一个零变更的 merge commit。
  3. master 现已全绿(CI-parity 命令,本地 master tip 实测):node tools/gen-config-docs.mjs generate → "wrote 10 blocks from 294 seed entries" + i18n ok;git diff --exit-code -- CONFIGURATION.md CONFIGURATION.zh-CN.md website/main.js website/docs/index.html → clean;check-coverage → pass(BILI_ROLLOUT_PLUGIN_LANE_SERVER_HISTORY 落在预期的 dynamic-names notice 列)。docs-sync 红灯已解除,被级联跳过的 test matrix 不再受影响。
  4. 本 PR head 的 CI:docs-sync / docs-coverage 均 success(test matrix 检查时仍在跑,但既然 no-op 已无意义)。
  5. 时间线:同一红灯被两个会话独立立项——docs-sync has been all red on master since the merge of #4505: the rollout.features.pluginLaneServerHistory seed entry i | docs-sync 自 #4505 合并起在 master 全红:rollout.features.pluginLaneServerHistory 种子条目丢失 #4520(10:56Z,另一会话)先行,其修复经 [PR] docs: restore dropped pluginLaneServerHistory seed row — unblocks docs-sync on master #4524 先合入;本 PR 所属的 CI docs-sync gate red on master: missing config-docs seed for rollout.features.pluginLaneServerHistory (fix lost in #4505 merge) #4533(11:22Z)查重时漏掉了 docs-sync has been all red on master since the merge of #4505: the rollout.features.pluginLaneServerHistory seed entry i | docs-sync 自 #4505 合并起在 master 全红:rollout.features.pluginLaneServerHistory 种子条目丢失 #4520(其正文写「Dup screen: none」),[PR] fix: restore lost config-docs seed for rollout.features.pluginLaneServerHistory (docs-sync red on master) #4534 开出来时(11:27Z)修复已在途。两修内容逐字节一致,先来后到以 [PR] docs: restore dropped pluginLaneServerHistory seed row — unblocks docs-sync on master #4524 为准。

结构化八问

  1. 是什么问题:[PR] feat: plugin-lane server-owned history — msgid pinning + transcript render endpoint | 插件车道服务端正史:msgid 钉身份 + 正史渲染端点 #4505 合并后 master 的 docs-sync 门禁红(配置文档种子缺条目导致再生成漂移)——该问题已随 [PR] docs: restore dropped pluginLaneServerHistory seed row — unblocks docs-sync on master #4524 合入而解决。
  2. 什么原因导致的:该配置项的文档行是 Plugin lanes: pin identity to client msgids, render outbound from the server-owned history | 插件车道服务端正史:消息身份钉在客户端 id 上,出站前缀由正史渲染 #4491/[PR] feat: plugin-lane server-owned history — msgid pinning + transcript render endpoint | 插件车道服务端正史:msgid 钉身份 + 正史渲染端点 #4505 手改文档直接写进 CONFIGURATION.md 的,单源 website/config-reference/rollout.yaml 从没有过对应条目,生成器重跑必删该行 → 漂移红。本 PR 与 [PR] docs: restore dropped pluginLaneServerHistory seed row — unblocks docs-sync on master #4524 是同一根因的两个独立修复。
  3. 影响范围与严重程度:当时阻断所有 PR 合入(docs-sync 为 required,test job 级联跳过);现在无影响,master 已绿。
  4. 怎么修复的:无需本 PR 再修——[PR] docs: restore dropped pluginLaneServerHistory seed row — unblocks docs-sync on master #4524 的修法(补 seed 条目为单一事实源 + 提交再生成后的文档态)与本 PR 内容逐字节一致且已在 master 生效。
  5. 是否有回归问题:无。模拟合入产生空 diff,零行为变化;高危模式(语义漂移/fail-fast 变吞错/阈值时序输出格式漂移)均不涉及。
  6. 是否破坏缓存:不涉及(纯文档台账文件,零运行时代码)。
  7. 是否改了设计方向:否。
  8. 是否引入了新的配置:否(仅登记既有 key/env,BILI_ROLLOUT_PLUGIN_LANE_SERVER_HISTORY 早已存在于 src/rollout.ts)。

本次执行的动作

  • 拉分支核对代码 + CI 状态 + master 现状 + no-op 模拟合入(上述 1–4);
  • 未 rebase/未 push:内容既已在 master,rebase 只会留一个空提交,无可推之物;
  • 给 PR 正文补了缺失的 ework-agent-pr 标记(此前缺失导致本 PR 触发了一次自我唤醒复核;补齐后不会再自唤醒);
  • 打上 duplicate 标签(duplicate of [PR] docs: restore dropped pluginLaneServerHistory seed row — unblocks docs-sync on master #4524)。按规则我不关闭 issue/PR——请 owner 直接关闭本 PR;若误点合并也无害(空 merge commit),但关闭更干净。

收工判定:#4534 冗余,可关;master docs-sync 绿灯已由 #4524 恢复,无需任何进一步代码动作。

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

重复判定:duplicate of #4519(等价修复已在 #4519 分支上)。

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

补充一条(供 owner 判断,不另立项——按规则这属于自动立项 issue 分析中的发现,先写评论等人决定):本 PR CI 里红的 7 个 test shard 与本 PR 内容无关,是 CI runner 侧既有的非确定性 flake。

证据:

  • 每个失败 shard 恰好只有 1 个失败测试:storage-render golden (chat)(tests/golden-storage-render.test.ts),报错是 test: rebaseline storage-render goldens after remove-absorb (#3309) #3325 的 stale-kernel-dist 守卫:node_modules/acp-kernel/dist is older than kernel/src … Rebuild first: npm run build;
  • 同一 shard 家族在本分支存在之前就红过(PR [PR] fix: redact storage diagnostics at the publish boundary #4499 的 matrix:ubuntu 22 s1/s3、ubuntu 24 s1、windows 22 s2/s3);
  • 本 PR 仅改文档台账(seed yaml + 再生成的文档四件套),不可能影响 kernel dist 的 mtime;同 OS 下 shard 随机过/挂(ubuntu 22 s2 绿、s1/s3 红)→ 指向 mtime 竞态而非内容回归。

是否把「#3325 守卫在 CI 里误触发」单独跟踪,由你决定;本 PR 侧无动作(等关闭即可)。

@ranxianglei

Copy link
Copy Markdown
Owner Author

(ai: zhipuai-lb/glm-5.3)

目标 issue #4533 已关。列车审查确认不再需要,关单。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working duplicate This issue or pull request already exists p2 scope/ci

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CI docs-sync gate red on master: missing config-docs seed for rollout.features.pluginLaneServerHistory (fix lost in #4505 merge)

1 participant