We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm doing the setup following the CONTRIBUTING.md file and when I run make lint, throws the following error in staticcheck step :
make lint
staticcheck
-: cannot import "github.com/cockroachdb/pebble/internal/rawalloc" (unknown bexport format version -1 ("...")), possibly version skew - reinstall package (compile) -: cannot import "math/bits" (unknown bexport format version -1 ("...")), possibly version skew - reinstall package (compile)
I did some research on my own but couln't find the root cause of the issue, I wonder if someone else experienced this issue before.
$ go version go version go1.20.8 darwin/arm64
The text was updated successfully, but these errors were encountered:
Based on the answer from this issue, It seems that staticcheck version must be ahead Go version to work properly, so for:
I had to upgrade staticcheck by running
go install honnef.co/go/tools/cmd/staticcheck@v0.4.0
And that fixed the issue
Sorry, something went wrong.
After fixing the staticcheck version, now the following command throws error
$ golangci-lint run ERRO Running error: unknown linters: 'musttag', run 'golangci-lint help linters' to see the list of supported linters
The solution was to upgrade golangci-lint to 1.51, by the release notes, they include musttag in this version:
$ go install github.com/golangci/golangci-lint/cmd/golangci-lint@v1.51.0
And voilà 🙂 make lint works
No branches or pull requests
Description
I'm doing the setup following the CONTRIBUTING.md file and when I run
make lint
, throws the following error instaticcheck
step :I did some research on my own but couln't find the root cause of the issue, I wonder if someone else experienced this issue before.
The text was updated successfully, but these errors were encountered: