fix: recover when the gateway child dies silently#207
Open
i-am-coco wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
$## Why\nRailway can stay green while Coco is effectively dead: the wrapper process stays up even if the OpenClaw gateway child exits, and
/healthzstill returns200 { ok: true }. That leaves the deployment silently unresponsive until someone visits the web UI.\n\n## What changed\n- auto-restart the gateway child on unexpected exit/spawn failure with bounded backoff\n- make/healthzreturn 503 when the deployment is configured but the gateway is not reachable\n- preserve setup-mode health when the service is not configured yet\n- route intentional stop/reset/import shutdowns through a sharedstopGateway()path so they do not trigger auto-restart\n- add regression guards for the new/healthzsemantics and the reset path\n\n## Validation\n-node -c src/server.js\n-npm test(14/14 passing)\n\n## Impact\nThis closes the specific failure mode where Railway keeps serving a healthy wrapper while the gateway child is gone, which is exactly the silent-unresponsive behavior seen in production.