-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
refactor: Introduce LogAcceptDebug()
which is LogAcceptCategory()
with Debug
level
#6436
Conversation
LogAcceptCategory()
to Debug
by defaultLogAcceptDebug()
which is LogAcceptCategory()
with Debug
level
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.
utACK c62b35c
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.
utACK c62b35c
NOTE: we should merge #6441 first to avoid backport conflicts (will rebase this PR later) |
Marked as draft so I don't merge |
This pull request has conflicts, please rebase. |
Range diff looks good; gonna merge |
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.
utACK dfe86b4
Issue being fixed or feature implemented
#6399 introduced severity-based logging via b046e09. We use
LogAcceptCategory()
in quite a few places and it's alwaysBCLog::Level::Debug
so log level is kind of redundant for us and just makes it harder to read the code.What was done?
Set log level in. IntroduceLogAcceptCategory()
toBCLog::Level::Debug
by defaultLogAcceptDebug()
which isLogAcceptCategory()
withDebug
level. Simplify corresponding Dash-specific code.How Has This Been Tested?
Breaking Changes
n/a
Checklist: