-
Notifications
You must be signed in to change notification settings - Fork 84
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Demotes some logging and cleans up some instrumentation to avoid overly noisy output that isn't cause for concern. * In catchup, demote retryable failures from WARN to INFO. We now only WARN if the overall operation fails (failed to fetch from any provider) or if we fail to fetch from a single provider in a way that indicates that provider is malicious (e.g. invalid Merkle proof) instead of just unreachable (e.g. HTTP error) * Add instance state to `skip` list for `instrument`, since it generates a very large debug output with each log * Remove `Debug` requirement from `StateCatchup` trait. This was generating a huge dump of useless data for the SQL provider in particular. Instead, we have a function `name() -> String` which is meant to be a short, readable identifier of the provider. We now use this when logging information about a specific catchup provider * Update `derive_more`, so we could customize the `Debug` impl of `NodeState` to use the `name()` function of the nested `Box<dyn StateCatchup>`, instead of the `Debug` impl. This update was a breaking change and thus required minor tweaks to a lot of other uses of `derive_more`. * Demote `timed out fetching proposal` from WARN to INFO. This happens normally when we are fetching an old proposal that the rest of the network has already GCed, and the task will eventually just exit on its own * Demote `background task exited` from INFO to DEBUG for short-lived tasks (proposal fetching) only * Demote L1 logging that happens every L1 block from INFO to DEBUG
- Loading branch information
Showing
15 changed files
with
142 additions
and
58 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.