Repository navigation
[PR] fix(ci): leak guard probes must not die under set -e + pipefail — wrap the is-ancestor chain in if (#4695) - #4696
ranxianglei wants to merge 1 commit into
Conversation
…p the is-ancestor chain in if (#4695)
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.5728-pr.4696.11a4711This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4696.tgz
npm install -g packageInstall instructions are refreshed on each push. |
🔶 需要决策 This PR is now obsolete — the file it fixes was deleted from master by an owner-directed takedown. This is not a mechanical merge conflict I can resolve; it needs your call. Diagnosis (verified live this run):
Options:
Default if undecided: A (close as obsolete) — re-adding the file contradicts the takedown, and with the file deleted the PR would be empty. Label |
[bot] 🏷 Outcome: escalated to a human decision — nothing was pushed. (Full diagnosis is in the Done this run:
Verified (live):
Label: Decision needed (detail in the
Risk: none from my side — the branch is untouched, nothing pushed. The PR simply sits open until you decide. Note: my earlier re-dispatch attempts hung on a network operation; per the lane's anti-loop rule I stopped re-checking and am reporting with the evidence already gathered. Awaiting your decision. |
[bot] 🏷 State unchanged — still awaiting your decision (options in the New, verified live this run via the mirror cache — the PR now shows 6 red test shards:
(All gates / static-gates / lock-sync / version-guard are green; the e2e lanes are skipped.) Why this doesn't change my recommendation: the PR is a single commit touching only So: awaiting your A/B/C decision (default A — close as obsolete). No further action is possible on my side until you decide. |
[bot] 🏷 Post-restart check — state is unchanged (my last status is the floor above; no owner decision has been posted since).
I'm blocked on that decision. No further mechanical action is possible on my side: I can't resolve the conflict without either re-creating the takedown's file (B) or emptying the PR (A). Nothing has been pushed; the branch is untouched, and I will not re-loop on checks. A one-word "A" unblocks this and lets the lane stop re-dispatching. |
[ework] auto-fix stalled: test (windows-latest, 22, 1), test (windows-latest, 22, 4), test (windows-latest, 22, 2), test (windows-latest, 22, 3), test (ubuntu-latest, 24, 3), test (ubuntu-latest, 22, 3) — stopping for human review |
[bot] 🏷 Re-dispatch to fix the 6 red test shards. Re-verified live via the mirror cache: all 6 are still red (windows 22 × 1–4, ubuntu 24/22 × 3; no pending). My previous run hung on a check-log fetch and was force-restarted, so I'm avoiding that op this run — I have the root cause from git instead. Why these shards can't be fixed mechanically on this PR:
So the red CI and the merge conflict share one root cause — the PR is obsolete — and one unblock: your A/B/C decision (default A: close as obsolete). Closing the PR clears both. Nothing has been pushed; the branch is untouched. |
[ework] auto-fix stalled: test (windows-latest, 22, 1), test (windows-latest, 22, 4), test (windows-latest, 22, 2), test (windows-latest, 22, 3), test (ubuntu-latest, 24, 3), test (ubuntu-latest, 22, 3) — stopping for human review |
1 similar comment
[ework] auto-fix stalled: test (windows-latest, 22, 1), test (windows-latest, 22, 4), test (windows-latest, 22, 2), test (windows-latest, 22, 3), test (ubuntu-latest, 24, 3), test (ubuntu-latest, 22, 3) — stopping for human review |
[bot] 🏷 Conflict re-dispatch — state unchanged, and the system itself has now flagged this as stalled.
I'm not re-attempting the fix (the lane has stopped) and not re-looping on checks. A one-word "A" closes it and clears both the conflict and the red CI. |
[ework] auto-fix stalled: test (windows-latest, 22, 1), test (windows-latest, 22, 4), test (windows-latest, 22, 2), test (windows-latest, 22, 3), test (ubuntu-latest, 24, 3), test (ubuntu-latest, 22, 3) — stopping for human review |
2 similar comments
[ework] auto-fix stalled: test (windows-latest, 22, 1), test (windows-latest, 22, 4), test (windows-latest, 22, 2), test (windows-latest, 22, 3), test (ubuntu-latest, 24, 3), test (ubuntu-latest, 22, 3) — stopping for human review |
[ework] auto-fix stalled: test (windows-latest, 22, 1), test (windows-latest, 22, 4), test (windows-latest, 22, 2), test (windows-latest, 22, 3), test (ubuntu-latest, 24, 3), test (ubuntu-latest, 22, 3) — stopping for human review |
[bot] 🏷 Re-dispatch (attempt 1/6) — no state change: no owner decision posted; PR still obsolete (fixes the file master's takedown The auto-fix lane keeps re-triggering as its 24h window expires, but every cycle re-confirms this same unchanged state — it's already logged "lane reached limit / auto-fix stalled, stopping for human review" several times above. It won't resolve on its own. Only unblock: your A/B/C decision (A close-as-obsolete [recommended, default] / B re-create / C leave open). I've escalated (🔶 需要决策) and won't re-attempt or re-loop. A one-word "A" closes it and clears both the conflict and the red CI. |
[ework] auto-fix stalled: test (windows-latest, 22, 1), test (windows-latest, 22, 4), test (windows-latest, 22, 2), test (windows-latest, 22, 3), test (ubuntu-latest, 24, 3), test (ubuntu-latest, 22, 3) — stopping for human review |
[bot] 🏷 Still unchanged (7th re-trigger — the lane's 24h window keeps expiring): no owner decision posted; PR still obsolete (fixes the file master's takedown Full options are in the |
[bot] 🏷 Still unchanged — no owner decision; PR obsolete (fixes the file master's takedown |
[ework] auto-fix stalled: test (windows-latest, 22, 1), test (windows-latest, 22, 4), test (windows-latest, 22, 2), test (windows-latest, 22, 3), test (ubuntu-latest, 24, 3), test (ubuntu-latest, 22, 3) — stopping for human review |
[bot] 🏷 Still unchanged (9th re-dispatch): no owner decision; PR obsolete (fixes the file master's takedown |
[ework] auto-fix stalled: test (windows-latest, 22, 1), test (windows-latest, 22, 4), test (windows-latest, 22, 2), test (windows-latest, 22, 3), test (ubuntu-latest, 24, 3), test (ubuntu-latest, 22, 3) — stopping for human review |
[bot] 🏷 Still unchanged (10th re-dispatch): no owner decision; PR obsolete (fixes the file master's takedown |
[bot] 🏷 Still unchanged (11th re-dispatch): no owner decision; PR obsolete (fixes the file master's takedown |
[ework] auto-fix stalled: test (windows-latest, 22, 1), test (windows-latest, 22, 4), test (windows-latest, 22, 2), test (windows-latest, 22, 3), test (ubuntu-latest, 24, 3), test (ubuntu-latest, 22, 3) — stopping for human review |
(ai: zai/glm-5.3)
Fixes #4695
What & why
Lane leak guard在 12:02 对bugfix-v0.1.207的干净 carry merge(#4684,fe2ae109)报红——本地复算确认范围内零真泄漏,红因是守卫自己的 shell 结构 bug:改动
单文件
.github/workflows/lane-leak-guard.yml:把探测&&链包进if [ -n "$P2" ] && git merge-base --is-ancestor ...; then echo ...; fi——if假条件退出 0,不再向 pipefail 泄漏;泄漏仍由后面的[ -n "$LEAKS" ]大声失败。语义不变,只是不再误杀/吞证据。验证
exit=1零输出(复现 CI 12:02 签名);新逻辑正确打印LEAKS=[<sha> leaky merge]并走失败分支;纯干净范围 exit 0。python3 yaml.safe_loadOK;step 脚本bash -nOK。