Repository navigation
[PR] ci: stop runner-queue pileups (serialize release trio, protect theorem lane, starvation alert) - #5333
Conversation
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.7528-pr.5333.39e48abThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr5333.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm-qwen/qwen3.8-27b) 查重:不重复(open+closed 全量检索无同类签名;这是 dsh-plugin-hub 安装器自动立项的首例该签名)。 DiagnosisThis is not a billion-context packaging defect. The auto-filer blamed Evidence:
Mechanism: What to do
If you paste the full Hub log (Notifications → the failed record → Copy) or your One more thing: the hub's auto-filer attributing a failure to the target plugin when the failing resource is a sibling git dep is misleading (it'll burn maintainer time on non-bugs like this). I can relay that observation to the dsh-plugin-hub maintainers if you want — that's an external submission, so I'll only do it with your explicit go-ahead. 中文结构化八问
判定:非本仓库缺陷,属「环境/网络 + 第三方 git 依赖」问题;已给出可执行绕行与确认路径,等你回传完整日志或 profile 清单即可 100% 定位到具体条目。 |
2ea9f1a to
b5f19f6
Compare
…(+ dead loop fix) Rebased onto post-fix master: overlapping product/doc repairs (promptPack docs, PackInstallOptions export, npm.cmd spawn, family-gate allowlist, CodexWindowSource, store adopt, refusal-remedy pin) already landed upstream while this branch was in flight, so they are dropped here. This PR is now CI-infrastructure only: - release-trio + master-build + theorem lanes get concurrency groups - default-6h timeout-minutes closed out on every release/advisory/pages/plugin gate - ci-janitor: sweep loop actually reads its input now (previously the whole zombie-cleanup rule set was dead code), plus a backlog breaker (starvedQueuedMaxMinutes) that drains stale queued runs under depth overload.
638b9d6 to
f571b60
Compare
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.961-master.f08e298 # this exact build
npm install -g billion-context@master # always the newest merged build
|
Three-way merge onto f08e298 (post-#5333 master). Four true conflicts, all additive-union: - web/page.ts: pck-notice-banner (mainline #5079) + autoreview-banner (#4634) - web/client.ts: #5079 banner handler kept verbatim first, #4634 handler after - server/handle.ts: #4634 local-answer early-return stays above the intent set; the #5135 ccTitleSidecar const supersedes the branch copy - server/admin.ts: status payload carries both mainline fields (origin, resolverWedge) and the #4634 autoReviewBlock block
What this fixes (human words)
On 2026-10-31 the queue clogged for ~3.5h: every job actually runs 2–8 min, but waited up to ~3.5 h just to get a runner (GitHub hosted allocation throttling on a day we triggered 800+ runs). The pile-up that made it worse had three structural holes, all fixed here:
cancel-in-progress: falsebecause two real back-to-back releases must publish in order, never cancelled mid-publish.-skipgroup so non-ci:fulllabel events can't kill a real run.done, notread— binding it toreadreopens the file at offset 0 every iteration and infinite-loops on line 1; verified locally before pushing). Plus two new tripwires, both tuned via dispatch inputs: when more thanstarvedQueueLimitruns (default 30) sit queued at once the job emits a loud::warning::with the per-event breakdown, and queued runs older thanstarvedQueuedMaxMinutes(default 60; 0 disables) get cancelled — after 2026-10-31 we know backlog depth itself stalls dispatch for this repo, so waiting out the old 120-min rule only snowballs further. Master push runs stay exempt either way (head's required checks).Plus
timeout-minuteswhere the GitHub 6 h default was still in effect: release(90), release-kernel(90), release-bugfix(90), release-manual(90), advisories(30), ci-gate-plugins(30), pages(30), theorem gate(10)/theorem(45).Also fixed here: three pre-existing master reds (found while optimizing)
Master tip itself was failing these three guards when this PR opened; fixing them on the branch so review/merge sees green (verified byte-exact diffs against master before pushing):
1fe5d4a0lifecycle-ledger-guard: registerBILI_SPAWN_FINGERPRINT([PR] Two installations differing by one version no longer deadlock on the same port; traffic is no longer sent in the clear ( | 两份安装差一个版本不再死锁在同一端口上,流量不再裸奔(#4125) #5303) andBILI_SESSION_CONTENT_STORE_PIN([PR] fold idle session content stores between requests (#4788 phase 2) #5292) in LIFECYCLE.md §2 — both introduced today without ledger entries. Pure doc insertion.a5934a94unused-exports:CodexWindowSourceis INTERNAL_ONLY (zero references outside its own file) — drop the leadingexport. One token, no waiver needed, no build surface change (no dts emit).923486eb+fe4cf2efdocs-sync: PR [PR] feat: Built-in chat prompt compression package — default compression rules for long-term companionship / multi-session m | feat: 内置 chat 提示压缩包——长期陪伴 / 多会话记忆场景的默认压缩规则(#5319) #5320 hand-edited the generatedcompress.promptPackindex line (added "chat") without updating thewebsite/config-reference/compress.yamlseed → revert both files' line to exactly what the generator emits. Durable fix = seed yaml + regenerate, filed as follow-up note (chat really exists but lives in the shipped-pack layer, not builtin).Once those gates went green the
testmatrix ran for the first time since the reds started, surfacing two more latent master failures (same hide mechanism):403bcf5elaunch refusal: today's [Bug] Plugin bootstrap spawns a new instance while the old one still holds the port and drops proxying (goes direct): la | [Bug] 插件 bootstrap 在旧实例仍占端口时新起实例并放弃代理(goes direct):大会话随即以未压缩历史撞上游上限(400 Range of input length / 413) #4125 rewrite of the attach-refusal message dropped the qualifierto the same versionthat the Oct 29 promptCache.routing is ignored by relay-affinity stamping; no way to persist per-endpoint prompt_cache_key abatement (0.1.209) #5103 suite asserts; restored in code (no test pins the shortened form — the new issue4125 suite only assertscode-fingerprint-mismatch).ef748200store flushAll retry test: [PR] fold idle session content stores between requests (#4788 phase 2) #5292 now folds a content store into a lazy proxy once its save lands; the test destroyed the envelope before its last read of the folded store, so the re-materialization threw by design (CCR content-store companion write is non-atomic — a crash mid-write silently destroys all retrievable originals #2674 discipline intact). Moved the fault injection to the actual write site (scheduleSave, synchronous attempt); every assertion unchanged.Baseline numbers (why the long tails are structural too)
Healthy day (Oct 30, n=144): e2e lanes median 19–57 min each, Release Kernel/Release/ci-image ~54–55 min, windows overlay ~31 min. With 15 cron lanes ticking every 30 min, any busy merge day easily outstrips hosted supply — which is exactly what happened.
Not changed here (owner decisions wanted)
Product-code surface: only the one-token export drop in
src/codex-models.ts(type visibility only, no behavior change). No config surface, no kernel/pi-subagents changes. Workflow YAML validated (safe_load); the janitor sweep script was smoke-tested locally against fixture runs (overload / breaker-off / normal-depth scenarios).