Repository navigation
chore: bump acp-kernel to 0.0.53 (persist ENOENT whole-cycle retry) - #560
Conversation
📦 Built Package ArtifactBranch: Option A — Install from npm PR tag (recommended)npm install -g billion-context@pr-560Each push to this PR publishes a new version under the Option B — Download artifact
tar xzf billion-context-pr560.tgz
npm install -g packageThis comment is automatically updated on each push. |
[bot] 🏷 Reviewing this PR now: verifying the diff against the description, confirming |
[bot] 🏷 Review verdict: ✅ LGTM — with one stacking note below. Merging stays human-only per AGENTS.md. Duplicate screening: only similar item is #375 (bump to 0.0.47, different kernel change) — distinct bump, not a duplicate. Diff verification (vs master):
Cross-repo rule (§5): Pre-flight re-run on branch tip
No issues found. Ready for human merge whenever (and decide on #559 ordering). |
What
Bumps the
acp-kernelpin from 0.0.52 → 0.0.53 (exact pin per AGENTS.md §2; realnpm installso the bundle picks up the new kernel).What 0.0.53 carries
acp-kernel PR #201 —
fix: retry whole write cycle on transient ENOENT/ENOTDIR (CI Windows temp sweep):isTransientFsErrorcovers EPERM/EBUSY/EACCES/ENOENT/ENOTDIR; the old code rethrew ENOENT immediately.writeInner/flushSyncretry the whole cycle per attempt (mkdir moved inside the loop, fresh tmp name, write, rename) — a swept directory is recreated.This closes the loop on the windows-22 CI flake (data layer): GitHub runners sweep
%TEMP%mid-test, killing the tmp file between write and rename. Companion test-layer fix (polling instead of fixed sleeps) already landed in PR #559.Pre-flight
npm test1046/1048 (2 known env-dependent fails inplugin-agent.test.ts, unrelated)node_modules/acp-kernel= 0.0.53 before rebuild