Repository navigation
Coding run upstream sync check fails silently with 404 (runner /coding/sync not found) #800
Description
Observed during a HeartFull-online/platform coding run (session csess_a73313bf-6537-4e8a-9f91-05b41b83d170, run starting 2026-09-11 03:13 UTC): both the start-of-run and end-of-run upstream sync check logged:
"Whether this checkout is up to date could not be checked: Runner /coding/sync -> 404: {"error":"Not found"}"
The run proceeded anyway on the existing local checkout without a confirmed-fresh sync, purely by luck the checkout happened to be current enough that the fix (issue #326) landed correctly. This is a silent failure mode: if the local checkout were actually stale, the agent would start editing outdated code with no warning surfaced to the operator.
Requested fix: either restore the /coding/sync runner endpoint so the check actually runs, or make a failed sync check block/loudly warn before the run proceeds rather than silently continuing.
Activity
feat(coding): a run does not build on a base it could not confirm (#801)
serge-ivo commentedon Sep 11, 2026
Same cause as #801: the runner was on CLI 0.4.57, one patch below the release that ships
/coding/sync(0.4.58). Fixed by upgrading the runner machines; the platform side (readable refusal + hard block + error_log record) landed in 0af538a. Verified live 2026-09-11: sync check now answersin sync with origin/main.