-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
chore: Fix linter findings for errorlint (part1) #12701
Conversation
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.
Many thanks, it would be great if we can enable this linter, I can't recall how many times I asked to change %v
to %w
on PRs.
Shouldn't we also be consistent to always use :
before the error? I see sometimes ,
is used..
@Hipska I would appreciate a consistent error formatting, but I think this is beyond the scope of this PR. However, additional PRs are welcome! |
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.
@zak-pawel thanks for the epic effort. I'd love to see this linter enabled! However, I agree with the comments of @Hipska. Can you please fix those!?
@srebhan during yesterdays maintainers meeting we agreed the uniform error messages with |
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.
Almost ;-)
Download PR build artifacts for linux_amd64.tar.gz, darwin_amd64.tar.gz, and windows_amd64.zip. 📦 Click here to get additional PR build artifactsArtifact URLs |
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.
Nice. Thanks again @zak-pawel for this epic effort!
Co-authored-by: Pawel Zak <Pawel Zak> (cherry picked from commit f7949ca)
Address findings for errorlint - finds code that can cause problems with the error wrapping scheme introduced in Go 1.13.
It is only part of the bigger job.
After all findings in whole project are handled, we can enable
errorlint
linter to guard this.Following findings in
agent
,cmd
,config
,internal
,models
,testutil
andtools
packages were fixed: