-
Notifications
You must be signed in to change notification settings - Fork 3.4k
cilium-cli: clean up log messages #40101
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
Conversation
/test |
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.
thanks!
Don't use the %w format verb in log messages, otherwise the error will be wrapped and will show up as follows in the respective log: %!w(*errors.errorString=&{some error message}) Use the %s format verb instead to just add the error message to the log output. Signed-off-by: Tobias Klauser <tobias@cilium.io>
Remove a stray argument that isn't supposed to be part of the error message and make the message a bit terser by not repeating the feature name. Signed-off-by: Tobias Klauser <tobias@cilium.io>
0c78f3d
to
316e23e
Compare
/test |
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.
Thanks!
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.
reapproving for policy
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.
@tklauser Good catch. Thank you!
Use the correct format verb when logging error messages (
%s
instead of%w
) and fix an error message related to requireModeIsNot requirements in feature detection.See commits for details.