Don't process socket.connect() if we are already re-connecting. #577
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.
@nkzawa Fixes #576 .
I opted to not allow the socket.connect call to proceed if we're in re-connecting mode, because it is breaking re-connection in some edge cases.
The alternative would be to cancel reconnection, try to connect, and if failed, allow reconnection. While this option will make sure that a re-connection try happens whenever .connect() is called, and disregard the timer, it's more messy to code.
And I think that the first option is good enough, since the default max re-connection try is 5000ms