-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(tree, engine, prune, stages, storage): improve logs #4790
Conversation
Codecov Report
... and 14 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
bin/reth/src/node/events.rs
Outdated
@@ -127,6 +128,14 @@ impl NodeState { | |||
|
|||
info!(number=block.number, hash=?block.hash, "Block added to canonical chain"); | |||
} | |||
BeaconConsensusEngineEvent::ChainCanonicalized(outcome, elapsed) => match outcome { | |||
CanonicalOutcome::AlreadyCanonical { header } => { | |||
info!(number=header.number, header=?header.hash, ?elapsed, "Chain is already canonical"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be a warning?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure, what are the cases when chain is already canonical? It doesn't sound like a problem that we need to warn the user about for me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this commonly happens on start up and could also happen if there are more CL connected
info is fine here imo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'd prefer downgrading it to trace/debug level, but no strong opinion on this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agree on debug level, because it might be seem like something's wrong while in reality it was a no-op
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems reasonable to me
bin/reth/src/node/events.rs
Outdated
@@ -127,6 +128,14 @@ impl NodeState { | |||
|
|||
info!(number=block.number, hash=?block.hash, "Block added to canonical chain"); | |||
} | |||
BeaconConsensusEngineEvent::ChainCanonicalized(outcome, elapsed) => match outcome { | |||
CanonicalOutcome::AlreadyCanonical { header } => { | |||
info!(number=header.number, header=?header.hash, ?elapsed, "Chain is already canonical"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this commonly happens on start up and could also happen if there are more CL connected
info is fine here imo
3dcec6e
to
e007e1c
Compare
tracing::instrument
spans of blockchain tree toTRACE
levelINFO
level inbin/reth/src/node/events.rs
instead of blockchain treeINFO
level inbin/reth/src/node/events.rs
DEBUG
level