Update Fork Version Handling in Monitoring and Network Modules #14991
+12
−12
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.
Description:
This pull request introduces several updates to the handling of fork versions across the monitoring and network modules. Key changes include:
Monitoring Module:
memory_node_bytes_buffered
to the monitoring properties to enhance memory tracking.Network Module:
wantedForkVersion
field to ensure it correctly reflects the desired fork version in various test cases.TestNextForkData
function to validate the fork version and epoch more effectively.Key Manager Tests:
These changes aim to improve the accuracy and reliability of fork version management within the system. Please review the modifications and provide feedback.