-
Notifications
You must be signed in to change notification settings - Fork 241
replace level pkg #385
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
replace level pkg #385
Conversation
566876b
to
55cdba4
Compare
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.
This is more thorough than I expected! I like it, the only thing I would like to clarify are the various messages we show users:
When providing an invalid log level, state what the valid levels are.
Every test error should have a unique text so it is clear which assertion failed. For the table tests, also include which input failed. When checking for errors, say so ("expected no error setting log level to %s, got: %s") instead of "expected: nil".
77b5df0
to
06aa952
Compare
Signed-off-by: royeo <[email protected]>
If an invalid log level is provided, the program will report an error. I have modified the test code, please continue to review @matthiasr |
Please review this PR @matthiasr |
Sorry for the delay, I'll review again this week
…On Sun, Aug 22, 2021, 21:12 Roy ***@***.***> wrote:
@royeo <https://github.com/royeo> requested your review on: #385
<#385> replace level
pkg.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#385 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABAEBXH72L4E66OQKZ23DDT6FDYZANCNFSM5CBR7OTA>
.
|
How's it going? |
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.
LGTM. I would love if this optimization was pushed upstream.
Is MR ready to merge? @matthiasr |
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.
Yep, looks good, thank you! I am not super happy about try --help
as a call to action when specifying an invalid level, but I don't see an elegant way to change that either.
with changelog for #385 #386 Signed-off-by: Matthias Rampke <[email protected]>
Ooops, sorry, I need to back this out. The tests didn't run on this at all for some reason, except for the DCO check, which made everything look green. |
the main change (#385) is missing license headers Signed-off-by: Matthias Rampke <[email protected]>
@royeo unfortunately the new files are missing the mandatory license header. Also, the tests didn't run on this PR at all, possibly because you opened it from your main branch. Could you please open a new PR, with headers like
on both of the new files? |
Please create a branch just for this change and create the PR from that. |
@matthiasr I create a new PR #390, please review it |
filter log calls by log level
Fixes #384