-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Reports typecheck issues even if it is disabled explictly in command #2177
Comments
Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors. |
this is happening only in linux container, on windows it worked fine with same version |
I meet the same problem, the solution:export CGO_ENABLED=0 |
@ldez could you please explain why this is not a bug? The documentation lists But TBH, I want to see this as a feature. In our case, |
golangci-lint is currently not compatible with go1.18. (#2438)
|
OK, perhaps it should be explicitly stated somewhere? Some warning in the docs, probably. |
This comment was marked as off-topic.
This comment was marked as off-topic.
When there are "real" lint errors, the linter will flood the output with spurious errors from the typecheck linter (which is not a real linter: golangci/golangci-lint#2177). typecheck errors are triggered when the Go compilation frontend fails - it's not clear why a compilation error elsewhere triggers all the spurious errors from AccessNodeBuilder etc. But disabling these makes it easier to find the real comppilation error.
Welcome
Description of the problem
I am running command
Still I am getting typecheck results though i need only unused results
output of command
Version of golangci-lint
Configuration file
Go environment
Verbose output of running
Code example or link to a public repository
The text was updated successfully, but these errors were encountered: