Backport fatal connection attempt handling to 0.216.x#390
Merged
jackyzha0 merged 1 commit intoJun 26, 2026
Conversation
Monkatraz
approved these changes
Jun 26, 2026
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
2 participants
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
@replit/river@0.219.0includes the fatal connection-attempt fix, but repl-it-web cannot consume it yet because pid2 still uses the 0.216.x River/@sinclair/typebox service type surface. This backports the same retry decision behavior to the 0.216.x maintenance branch.What changed
onConnectingFailed.onConnectingFaileddelete the no-connection session and stop reconnecting whenisFatalConnectionErrorreturns true.0.216.3.Test plan
direnv exec . npm exec -- vitest run __tests__/negative.test.tsdirenv exec . npm run checkdirenv exec . npm exec -- vitest run