-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
The golangcilint
linter of perfsprint
is not working as expected
#14214
Comments
Why does a performance linter matter for test files? |
It doesn't - but it's not the way it worked in the previous version thus can be considered a breaking change? |
When So at the very minimum, it is now inconsistent. |
It's not a regression. That line is not caught because of a perfsprint exclusion in .golangci.yml. That exclusion had to be updated for v1.59.0. That's why you see more things getting caught when downgrading. |
🤦 so this is actually text-based exclusion in This comment from Björn makes all the sense in the world: #14091 (comment) |
Thanks for the clarification 😉 |
What did you do?
I noticed that this particular line should have been caught by the linter and failed: https://github.com/prometheus/prometheus/blob/main/rules/manager_test.go#L198 (there are more examples)
The text was updated successfully, but these errors were encountered: