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
govet: printf
unstable behavior with imported types
#4423
Labels
Comments
Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors. |
Hello, the problem is related to 2 things: the cache, and the relative position between reports and the code.
For now, I have no solution, I need to investigate more. |
I found a solution. |
ldez
changed the title
govet: Feb 27, 2024
govet
printf
unstable behavior with imported typesprintf
unstable behavior with imported types
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Welcome
Description of the problem
Hi, we've encountered some strange behavior with the
govet
printf
linter.If we edit the previously reported file without fixing the issue, it stops reporting the issue. However, if we clean the cache, it gets back to normal, but I'm not sure we're supposed to clean the cache before every
run
.There is one interesting detail that I think may be a clue though.
It stops being unstable if we change the code so that it doesn't import
logger
, but initializeslog
in place:Version of golangci-lint
Configuration
Go environment
Verbose output of running
A minimal reproducible example or link to a public repository
https://github.com/gabolaev/gl-issue-reproduction
Validation
The text was updated successfully, but these errors were encountered: