New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert "NATS reconnect fully recreates TCP session" #1821
Conversation
Closes #1820 |
Looks, like this nats (disconnect fix) really brokes current broker messaging. @Waldz should we revert and wait for p2p communication implementation for direct messaging? |
Reopen should:
|
ee7ad3b
to
82f0d4b
Compare
@@ -74,3 +74,5 @@ require ( | |||
gopkg.in/urfave/cli.v1 v1.20.0 // indirect | |||
gopkg.in/yaml.v2 v2.2.8 // indirect | |||
) | |||
|
|||
replace github.com/nats-io/go-nats v1.4.0 => github.com/mysteriumnetwork/nats.go v1.4.1-0.20200303115848-b4a5324c56ed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it really required to have a custom version of nats?
This PR was approved as a revert of the commit. But now it merged with completely different changes without review. :/ |
This reverts commit c7fbce9.