Remove duplicated connection limits checks #6156
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
and remove connection limits checks after connection has been established, as those checks have already been done by connection limits Behaviour.
when we call dial_peer we are not yet dialing but just adding the peer to the dial queue
we only use it at one place, and the function call is explicit.
AgeManning
reviewed
Jul 25, 2024
but do it before the connection has been established.
AgeManning
approved these changes
Jul 26, 2024
|
bumping this |
|
@Mergifyio queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 17711b7 |
5 tasks
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.
Issue Addressed
Following #6140 (review) found duplicated code and took the time to improve the wording with regards to dial logic.
Reviewing by commit is suggested as I left detailed notes on the commit messages.
@AgeManning if you feel it contains too many code changes we should probably wait for after
5.3release.