r11s-driver: fix offline reconnect #10378
Merged
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.
Transitioning to offline does not overtly fail reconnect attempt, causing reconnect to delay by up to 22 seconds #10325
For more information about how to contribute to this repo, visit this page
Description
The
reconnect_attempt
event from Socket.io does not fire in offline scenario for some reason. Rather than figuring out how/why this is not reliable, we can just switch to counting connect_error events, which are reliable.Steps to Reproduce Bug and Validate Solution
PR Checklist
Does this introduce a breaking change?
Testing
Follow above repro steps. Instead of seeing a delay on reconnect, you can see it reconnects immediately.
Additionally, by adding a breakpoint in the connect_error listener you can see it fail overtly after the 2nd connect_error when offline.
Any relevant logs or outputs
Other information or known dependencies
Fixes #10325