Fix #153 - handle nats connections that are already connected #154
Conversation
This file contains 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
kozlovic
approved these changes
Jan 24, 2020
|
|
||
| // @private | ||
| Stan.prototype.setupHandlers = function () { | ||
| // if they gave us a connection, it could be connected, so the `connect` event may never fire. |
There was a problem hiding this comment.
I would have done that in createConnection() since we already check if the connection is owned or not.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
stan.js connections initialize the stan protocol on the nats
connectevent. In cases where the connection is provided, and already connected, this event is never emitted, thus the client hangs.