qwen-code splits retry-from-history hardening into four checkpoint reliability fixes
qqqys · ghdev · 2026-09-20
QwenLM/qwen-code issue #12287 splits the hardening work out of PR #12190 (retry-from-history), which had ballooned from 1000 to 1900 lines across six autofix rounds and started touching the runner's resume semantics, checkpoint schema, and the daemon's untrusted-workspace boundary.
Four fixes are tracked:
- Make the run checkpoint authoritative: the checkpoint write is deliberately un-awaited, but the retry gate treats it as proof another process is running; the write must be awaited and a failed write must refuse the start.
- Writer identity across pid recycling: process.kill(pid, 0) misreads recycled pids as alive; recording the process start time (Linux /proc/<pid>/stat field 22) makes the check exact.
- Resumes should not restate args: the settled snapshot can claim a run had no args when it did; the prior attempt's args projection should carry forward.
- Distinguish 'args never recorded' from 'args omitted': pre-#12159 snapshots carry neither field, and the daemon needs to decide whether to refuse retries.
A detailed engineering discussion of agent-workflow checkpoint and concurrency semantics.
More from coding & agent
- Grok Bots 1.0 leaks: multiplayer teammates, proactive agents in Slack and Teams — XFreeze · 2026-11-12
- Could MCP-powered copy-trading disrupt ETFs? Investor floats paying 0.5% for trade signals — MartinGTobias · 2026-11-12
- minpts-check: one-run predictor tells if your HDBSCAN clusters survive min_samples changes — leland_mcinnes · 2026-11-12
- Ten wild Gemini 4 Carbon demos in 24 hours: CUDA meadows, V8 engines, mech stomps — socialwithaayan · 2026-11-12
- How to cut Fable 5.2 token costs by 90%: Arc routing plus a lean CLAUDE.md — EXM7777 · 2026-11-12
- Hamel Husain's complete AI evals framework for PMs and engineers — aakashgupta · 2026-11-12