refactor(p2p): refactor peer address handling [part 1/10] #1173
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.
Motivation
As part of the P2P Multiprocess project, this PR implements refactors to improve the way we handle peer addresses.
Acceptance Criteria
WarningFlags.NO_PEER_ID_URL
.FakeConnection
andHathorStringTransport
so they support real addresses.FakeConnection
so it actually callsConnectionsManager.connect_to
to make a connection, instead of just manually creating a connection that was not properly started by that method.PeerAddress
dataclass and renameEntrypoint
dataclass toPeerEndpoint
, which is now composed by the newPeerAddress
and aPeerId
.PeerInfo.entrypoints
to a list ofPeerAddress
instead ofPeerEndpoint
.Checklist
master
, confirm this code is production-ready and can be included in future releases as soon as it gets merged