Add status logging while processing a ledger #3916
Merged
Conversation
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
Codecov Report
@@ Coverage Diff @@
## master #3916 +/- ##
========================================
+ Coverage 77.8% 77.8% +<.1%
========================================
Files 162 162
Lines 27238 27242 +4
========================================
+ Hits 21202 21207 +5
+ Misses 6036 6035 -1 |
1 similar comment
Codecov Report
@@ Coverage Diff @@
## master #3916 +/- ##
========================================
+ Coverage 77.8% 77.8% +<.1%
========================================
Files 162 162
Lines 27238 27242 +4
========================================
+ Hits 21202 21207 +5
+ Misses 6036 6035 -1 |
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.
Problem
process_blocktree()can take minutes, or worse, when processing a large ledger (cc: #2475) with no output of any kind to the user.Summary of Changes
Every two seconds
process_blocktree()now emits aninfo!log containing the current block it's processing.