A child forge the host stopped

src/spawn/stopped.ts records a stop (one state object per parent; the host passes in how a forge starts again), writes stopped.json into the child's directory, and arms a restart after a backoff: 5 s, doubling per stop to 10 min, the count starting again after 30 clean minutes. The restart goes through the due-wake path, so the disk floor still applies; when the awake ceiling is full, forges quiet for a minute with no crew at work are put to sleep to make room, and a try that is turned away is made again a minute later, for the hour the stop is shown. While it stands, the wake page and the terminal's forges list say "ran out of memory and was stopped at HH:MM UTC; the host starts it again at HH:MM UTC" (or "within a minute") instead of "the forge is full".

The run the stop cut off is queued again once (requeueInterrupted reads stopped.json: the stop was for memory and came while the run held its lease); a run cut off for memory a second time fails with that reason (MEMORY_OUT) instead of stopping the forge again.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs