sites: confirm access-stream recovery after reconnect - #303
Merged
Merged
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.
After Janus restarts, Rip reports that an access stream is waiting for app re-registration but never confirms recovery. Emit one
rip-sites: access stream: reconnectedmessage once the replacement stream completes its validated initial protocol exchange. Normal startup stays quiet, and diagnostics stay on stderr so raw access output remains NDJSON.Validation: all 140 Sites tests, 3,196 language tests, and 16 browser tests pass (two existing skips). Regression coverage checks registration replacement, repeated outages, initial-gap validation, and recovery after a real Janus restart.