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
oracle-gaps daemon: a closing hung daemon and --stop-daemon have no cold fallback or bound #135
Two daemon paths still have no cold fallback, merge-gate finding F3 on #131 (v21.2 R39, P10/I7, D61).
A closing daemon whose check is hung.
A stop request, or a CLI of other code, sets closing and queues shutdown behind the hung check (daemon.mjs, serve).
Every later check hears { closing: true }. After WAIT_MS (60 s), requestDaemon throws "the package's daemon did not answer within 60 s".
The result is an internal error: exit 3, and no cold check.
--stop-daemon against a hung daemon.stopDaemon sends its stop request with no bound, so the command never returns.
Owed, oracle-first:
A constructed history that closes a held daemon. Hold a check at the daemon-check pause, send a stop or a CLI of other code, then run a check and a --stop-daemon.
The law: each ends with one done line within the bound, and a check runs cold.
The hostile mutant: the current throw, and an unbounded stop.
Activity
fix(oracle-gaps): a CLI that falls back ends the daemon that held its…