Remove redundant closing of connection #4056
Merged
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
|
I tested with a Regtest Bitcoin Core with wrong configuration and on Mainnet with Bitcoin Core and everything works as expected on macOS. |
|
But there still seems to be an issue on @wiz Linux setup. |
Fixes bisq-network#4052, as the peer.close() already calls closeConnection if a writeTarget is established successfully.
ripcurlx
force-pushed
the
fix-connection-closing-of-core-node-detection
branch
from
5bc3425 to
e7a22f4
Compare
|
Tested and works on macOS Catalina |
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.
Fixes #4052, as the
peer.close()already callscloseConnectionifa
writeTargetis established successfully.