Repository navigation
csnode: missing round table while syncing is a warning, not an error - #82
Merged
Merged
Conversation
A node far behind the network gets the packages of the current rounds without their round tables and logged an error for each; the block comes with the sync. Only a node that is not behind still logs an error. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
A node that is still syncing receives the round packages of the network's current rounds without having their round tables.
Node::getCharacteristicloggedcannot access proper round table to add trusted to pool #Nas an error each time, although nothing is wrong: the package is skipped and the block arrives with the normal sync. Seen on a mainnet node a few times after every start, while about 14 M blocks behind.Now a node whose last block is more than one behind the package's sequence logs a warning that names its last block; a node that is not behind still logs the error. Logging only, no change in behaviour.
🤖 Generated with Claude Code