fix: Correct byte order for IPv4/IPv6 peer address serialization #127
Conversation
This file contains hidden or 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
Member
satran004
commented
Dec 27, 2025
satran004
commented
- Correct byte order for IPv4/IPv6 peer address serialization
- Add configurable reconnection control for NodeClient
Add NodeClientConfig to provide fine-grained control over connection behavior, addressing the issue where automatic reconnection was problematic for short-lived connections like peer discovery.
- Fix IPv4/IPv6 address byte order in PeerSharingSerializers to use little-endian - Add support for both V11-12 (8 elements) and V13+ (6 elements) IPv6 peer address formats - Reduce PeerSharingAgent timeout from 30s to 5s
|
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.