Skip to content

[PR] fix(update): Add advisory gate before managed channel refresh — dsh/pi replicas no longer pull back defective versions | fix(update): 托管通道刷新前补 advisory 闸门 — dsh/pi 副本不再拉回缺陷版本 - #4027

Open
ranxianglei wants to merge 5 commits into
masterfrom
2026-10-21_managed-lane-advisory-gates

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Fixes #4026

#4003 评审 auto-update 域 F2。

改动(3 文件):

为何要修: 宿主通道(dsh plugin add / pi update)拉进来的副本在 advisory watcher 回滚范围之外——闸门是宿主副本唯一的防线。

验证: dsh-self-refresh + pi-self-refresh 25/25;update-policy + advisory 74/74;tsc 干净。

⚠️ 载重文件: 动了 src/update.ts——按仓库规矩需要先有 no-op 验证发版再合并,请 owner 拍板顺序。config 面未动。

@github-actions

github-actions Bot commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-21_managed-lane-advisory-gates (135eb12)

Latest build — install this exact version

npm install -g billion-context@0.0.6195-pr.4027.c754b65

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
135eb12 billion-context@0.0.6195-pr.4027.c754b65 build
05e5a92 billion-context@0.0.6106-pr.4027.5fe2e4b build
b6b8c3a billion-context@0.0.6014-pr.4027.80fe44b build

Download artifact

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

Install instructions are refreshed on each push.

@ranxianglei ranxianglei changed the title fix(update): 托管通道刷新前补 advisory 闸门 — dsh/pi 副本不再拉回缺陷版本 [PR] fix(update): Add advisory gate before managed channel refresh — dsh/pi replicas no longer pull back defective versions | fix(update): 托管通道刷新前补 advisory 闸门 — dsh/pi 副本不再拉回缺陷版本 Oct 20, 2026
@ranxianglei
ranxianglei force-pushed the 2026-10-21_managed-lane-advisory-gates branch from 44cb842 to 676cb14 Compare October 21, 2026 03:05
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

已 rebase 到当前 master 并复审完毕。

…ory gates before driving dsh/pi channels
@ranxianglei
ranxianglei force-pushed the 2026-10-21_managed-lane-advisory-gates branch from 676cb14 to 6ead4a7 Compare October 21, 2026 10:02
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

CI 已修绿:PR 分支 rebase 到当前 master tip 7790bea91 后,新 head 6ead4a777 全矩阵通过——之前红的 5 个分片全部转绿,无一例外。diff 内容零改动。

八问

  1. 是什么问题:PR 自身代码没有问题。CI 红是因为分支基座太旧——它基于的 master 上存在几个当时已知的红(verif 测试写死开发机路径、SMT solver 缺失时抛错而非跳过、Windows 文件锁 EBUSY、Windows 分片上 plugin-fork 挂起),这些在基座切出之后都已陆续修掉,但 PR 还站在旧基座上跑。
  2. 什么原因导致的:上一轮 rebase 只到了 56a0f5a46,其后 master 又合入了 [PR] fix(verif): drop dev-machine absolute paths in wire harnesses + gate solver-dependent anthropic round-trip tests #4084(两个 commit:去掉 verif 里的开发机绝对路径 + 把 solver 依赖的 wire/induction 测试改为无 solver 时正确 skip)和 [PR] fix(ci): close store1 before dropping index.db in #3769 pooled-bare-load — Windows EBUSY #4087([Bug] MCP failed compression record rotation prematurely rewrites the history prefix, triggering expensive cache recompu | [Bug] MCP 失败压缩记录轮换提前改写历史前缀,触发大额缓存重算 #3769 pooled-bare-load 在 Windows 上先关 store 再删 index.db,消 EBUSY)。逐分片对照:
  3. 影响范围与严重程度:仅本 PR 的 CI 信号,对用户和线上行为零影响。
  4. 怎么修复的:纯机械 rebase 到当前 master tip(含上述全部修复)。没有写任何新代码,diff 仍精确为 3 个文件 +144 行(src/update.ts 的 advisory 闸门 + 两个 self-refresh 测试文件)。
  5. 是否有回归问题:无。零内容变更 = 零行为面变化。已验证 PR 触碰的 3 个文件自基座以来没有被任何 master commit 修改过(不存在语义交互的可能)。本地定向验证:typecheck 干净、PR 自带 2 个测试文件 25/25 通过;远程 CI 新 head 全部 job 绿(ubuntu/windows × node 22/24 各分片 + static gates + kernel-guard 等)。
  6. 是否破坏缓存:不涉及(纯 rebase)。
  7. 是否改了设计方向:无。
  8. 是否引入了新的配置:无。

收工判定:CI 侧已闭环,可合并状态。唯一未决项不变且与本次修复无关:本 PR 触碰 src/update.ts(load-bearing),按 §5 需要先走一次 NO-OP 验证发版再合入——该决策项仍在 #4026 线程等 owner 拍板,批准即执行。

ci-check added 4 commits October 26, 2026 10:19
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.

This branch has not been deployed

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

Projects

None yet

1 participant