Skip to content
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(deps): Bump golangci-lint from v1.62.0 to v1.62.2 #16250

Merged
merged 5 commits into from
Dec 5, 2024

Conversation

zak-pawel
Copy link
Collaborator

Summary

internal/content_coding.go:1:1                  revive  max-public-structs: you have exceeded the maximum number (5) of public struct declarations
metric.go:1:1                                   revive  max-public-structs: you have exceeded the maximum number (5) of public struct declarations
plugins/common/jolokia2/client.go:1:1           revive  max-public-structs: you have exceeded the maximum number (5) of public struct declarations
plugins/common/opcua/input/input_client.go:1:1  revive  max-public-structs: you have exceeded the maximum number (5) of public struct declarations

Checklist

  • No AI generated code was used in this PR

Copy link
Member

@srebhan srebhan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we should unexport the concrete encoders/decoders! They are helpful if you know the encoding!

@zak-pawel
Copy link
Collaborator Author

I don't think we should unexport the concrete encoders/decoders! They are helpful if you know the encoding!

@srebhan
All these encoders/decoders are available by using NewStreamContentDecoder, NewContentEncoder, NewContentDecoder.

@srebhan
Copy link
Member

srebhan commented Dec 4, 2024

Yes but if I know I want the gzip decoder, why should I need to do the indirection? I don't see any value in this! Furthermore, the PR is about bumping the linter and you are changing code which is not related to the bump. So please leave the encoding as is.

I see value in limiting the exported stuff for the plugins but not for the rest of the code-base...

@zak-pawel
Copy link
Collaborator Author

So please leave the encoding as is.

@srebhan Changed.

Copy link
Member

@srebhan srebhan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we please move the change of the encoding/decoding things to a separate PR!? The title does not suggest those changes...

@zak-pawel
Copy link
Collaborator Author

The title does not suggest those changes...

@srebhan
But the PR description definitely suggests it 😎 Just in case, it's about addressing new findings for

internal/content_coding.go:1:1                  revive  max-public-structs: you have exceeded the maximum number (5) of public struct declarations

Usually, what we did was that if the bumped golangci-lint started detecting new findings, we fixed them in the same PR. Clean and tidy.

Here are excellent examples:

@srebhan
Copy link
Member

srebhan commented Dec 4, 2024

@zak-pawel I'm a bit puzzled. We agreed on limiting the export stuff to the plugin directories only. So why does it warn for something in internal now? And why didn't it previously?

@zak-pawel
Copy link
Collaborator Author

@zak-pawel I'm a bit puzzled. We agreed on limiting the export stuff to the plugin directories only.

@srebhan Yes! You're right, I totally forgot about that.

So why does it warn for something in internal now? And why didn't it previously?

Because the message format that we have excluded so far has been changed from you have exceeded the maximum number of public struct declarations to you have exceeded the maximum number (5) of public struct declarations. I corrected our filter.

@telegraf-tiger
Copy link
Contributor

telegraf-tiger bot commented Dec 5, 2024

Copy link
Member

@srebhan srebhan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @zak-pawel!

@srebhan srebhan added the ready for final review This pull request has been reviewed and/or tested by multiple users and is ready for a final review. label Dec 5, 2024
@srebhan srebhan assigned DStrand1 and unassigned srebhan Dec 5, 2024
@DStrand1 DStrand1 merged commit 598079a into influxdata:master Dec 5, 2024
27 checks passed
@github-actions github-actions bot added this to the v1.33.0 milestone Dec 5, 2024
justinwwhuang pushed a commit to justinwwhuang/telegraf_fork that referenced this pull request Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore linter ready for final review This pull request has been reviewed and/or tested by multiple users and is ready for a final review.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants