You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 65d8320
Browse filesBrowse the repository at this point in the historyBrowse files
Three regressions from e1b8ae3/c4722b5:
- renderTaskResult stamped [[codex-task status=complete]] on failure/empty
fallback output, so a failed run carried the success sentinel and the
completion hook read it as success. The sentinel is now appended only on a
successful exit (status 0); failure/empty output renders without it.
- runForegroundTaskWorker inherited the 240s status-wait default, so foreground
xhigh runs (routinely >4min) timed out instead of returning the result. The
inline wait is now unbounded; the detached worker provides survival.
- enqueueBackgroundTask left the queued record pid: null and never persisted
the spawned worker pid, breaking /codex:cancel. The worker pid is now written
after spawn, guarded against clobbering a finished job.
Tests: 97/97 (added failure-no-sentinel + worker-pid coverage).
Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
0 commit comments