feat(launch): forward the P0-#5 watchdog knobs through the ring launcher - #122
Merged
Conversation
The watchdog env flags (#120) were unreachable in a real deployment: the launcher only forwards ENG_ENV to stages/gateway, and M25_RET_STALL_S (tail), M25_DRAFT_BUDGET_S/M25_JOB_STALL_S (coordinator) plus M25_REPLY_TIMEOUT weren't in it. A flag a stage never receives is dead. Add them so the tail gets its stall bound and a --serve gateway coordinator gets the budgets.
leyten
added a commit
that referenced
this pull request
Jul 20, 2026
…123) Controlled-ring validation closes P0-#5: shipped #120 build + #122 knobs serve M2.5 over a real 3-region WAN ring (degraded=false, receipts chained under one nonce); the sustained-backpressure M1 wedge is not reproducible on a fast datacenter ring by construction (depth-1 EAGLE, 4-6MB buffers, no NET_ADMIN) — proven offline in test_ret_stallguard.py. Marks P0-#5 DONE, adds the receipt.
leyten
added a commit
that referenced
this pull request
Jul 22, 2026
…her (#122) The watchdog env flags from #120 were unreachable in a real deployment — the launcher only forwards ENG_ENV to stages/gateway, and M25_RET_STALL_S (tail), M25_DRAFT_BUDGET_S/M25_JOB_STALL_S (coordinator), M25_REPLY_TIMEOUT werent in it. Adds them so the tail gets its stall bound and a --serve gateway coordinator can tune the budgets.
leyten
added a commit
that referenced
this pull request
Jul 22, 2026
…123) Controlled-ring validation closes P0-#5: shipped #120 build + #122 knobs serve M2.5 over a real 3-region WAN ring (degraded=false, receipts chained under one nonce); the sustained-backpressure M1 wedge is not reproducible on a fast datacenter ring by construction (depth-1 EAGLE, 4-6MB buffers, no NET_ADMIN) — proven offline in test_ret_stallguard.py. Marks P0-#5 DONE, adds the receipt.
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.
Follow-up to #120. The watchdog env flags were unreachable in a real deployment: the launcher only forwards ENG_ENV to stages / the gateway coordinator, and the new knobs were not in it — a flag a stage never receives is dead code.
Adds to ENG_ENV: M25_RET_STALL_S (tail-side return-socket stall bound), M25_DRAFT_BUDGET_S + M25_JOB_STALL_S (coordinator-side draft budget + job-stall backstop), and M25_REPLY_TIMEOUT (the F6 heartbeat, forwardable for the --serve gateway path). Now the tail actually gets its stall bound and a gateway launch can tune the budgets. Needed to run the controlled-ring validation with a fast (non-default) stall bound.