[Trivial] Reduce log level of "Unable to find ledger" message: fixes #3996. #4129
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
mDuo13
approved these changes
Apr 12, 2022
|
To me it looks like we're processing a request for a ledger from a peer. If the requested ledger is not available locally this message is generated. Doesn't really seem like a |
seelabs
approved these changes
Apr 13, 2022
scottschurr
added
the
Ready to merge
|
Merged into 1.9.1-b1. |
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.
High Level Overview of Change
GitHub issue #3996 notes a lot of unhelpful noise from the
"Unable to find ledger ..."log message. The proposed change is to reduce the log level fromwarn()todebug().Context of Change
Work to reduce noise in the log noted by GitHub issue #3996.
Type of Change