-
Notifications
You must be signed in to change notification settings - Fork 103
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: Update third-party dependencies to their latest releases #1615
Conversation
This bump the modules as well as 'golangci-lint' to their latest releases. It also fixes linter warnings due to updated linters, among them a potential DoS when copying files from archives (gosec G110). 'gotest.tools' has been removed in favor of 'stretchr/testify', as it offers the same functionality. Signed-off-by: Jan Schlicht <jan@d2iq.com>
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.
Looks pretty good, apart from that one change that I commented. It may be ok to change the behavior, but i'd like to get some more opinions about it
Signed-off-by: Jan Schlicht <jan@d2iq.com>
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.
Looks good, I have two questions but they probably won't be a blockers. Thanks 👏
@@ -29,5 +29,4 @@ linters-settings: | |||
dupl: | |||
threshold: 400 | |||
goimports: | |||
# Don't use 'github.com/kudobuilder/kudo', it'll result in unreliable output! | |||
local-prefixes: github.com/kudobuilder | |||
local-prefixes: github.com/kudobuilder/kudo |
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.
what changed here? that we can do it now...
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.
No idea 😆
I had a lot of issues with that back when we introduced golangci-lint
. Now I don't see them anymore and have been using it with full prefixes successfully in other (albeit smaller) projects -- kitt and test-tools.
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.
why don't we leave it local-prefixes: github.com/kudobuilder
? It seems to function and allows for a usable configuration across projects.
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.
Because that wouldn't just group kudo
packages but packages from other projects in the kudobuilder
org as well. For example in pkg/engine/task/task_kudo_operator_test.go
, a kuttl
import was grouped with kudo
imports. This will be fixed with this change to local-prefixes
.
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.
make generate
leaves the repo dirty
CRDs and bindata.go are dirty
@@ -29,5 +29,4 @@ linters-settings: | |||
dupl: | |||
threshold: 400 | |||
goimports: | |||
# Don't use 'github.com/kudobuilder/kudo', it'll result in unreliable output! | |||
local-prefixes: github.com/kudobuilder | |||
local-prefixes: github.com/kudobuilder/kudo |
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.
why don't we leave it local-prefixes: github.com/kudobuilder
? It seems to function and allows for a usable configuration across projects.
I would push the updated changes... but it likely needs some analysis... some of the change looks like simple line limits which result in wrapping... like:
It would be good to understand what is causing this change... and if innocuous.. then including the changed files |
after generating files |
additionally... golangci needs a change to which makes me question if the correct linter version was used.. |
I should add.. there are some really good mods here... In particular the error handling around io.Copy and size limitations! |
@kensipe, interesting, |
Signed-off-by: Jan Schlicht <jan@d2iq.com>
This would also explain why running |
Signed-off-by: Jan Schlicht <jan@d2iq.com>
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
It was necessary to delete controller-gen
and go-bindata
. after that all is well!
Signed-off-by: Jan Schlicht <jan@d2iq.com>
What this PR does / why we need it:
This bumps the modules as well as 'golangci-lint' to their latest releases.
It also fixes linter warnings due to updated linters, among them a potential DoS when copying files from archives (gosec G110).
gotest.tools
has been removed in favor ofstretchr/testify
, as it offers the same functionality.