PeerConnectionManager should not disconnect whitelisted nodes #4444
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
When trying to maintain the max peer count allowed, the peer connection manager should not disconnect whitelisted nodes. The expectation for whitelisted nodes is that they should essentially be treated special and assumed to always be connected.
patnir
approved these changes
Nov 9, 2023
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.
Summary
When trying to maintain the max peer count allowed, the peer connection manager should not disconnect whitelisted nodes. The expectation for whitelisted nodes is that they should essentially be treated special and assumed to always be connected.
Closes IFL-1812
Testing Plan
Unit test
Documentation
N/A
Breaking Change
N/A