akula
akula copied to clipboard
Improved logging to reduce noise, additional messages to track progress during headers, bodies, & exec stages
When downloading headers and bodies, I found the default output to be very noisy, so I reduced some of the debug! messages to trace! messages since they are noisy enough that it seems more appropriate for them to be trace messages. This makes it so that debug messages mostly report helpful messages but not so noisy that it running with debug logging generates huge log files with many more messages than needed--that seems more appropriate to be trace-level logging
I also added block numbers to some log messages to track progress because reporting just "Downloaded 50 new headers" doesn't make it clear what block it's on.
In a few places I added a new log message to some functions such as to report the block range (such as BodyDownload) or addition messages to report what's being written to the database (such as account and storage changes in write_history and write_to_db).
Also a saw a few lines where a tab was used instead of spaces so I fixed those lines for consistency.
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.
:white_check_mark: jomuel
:x: mconover
You have signed the CLA already but the status is still pending? Let us recheck it.
I'm afraid I cannot accept the PR unless you sign the CLA :(