-
-
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
goanalysis_metalinter panics on go1.20 netip package #3533
Comments
Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors. |
Ah, I see that golangci-lint actually does depend on dominikh/go-tools; I didn't realize that that repo is imported as honnef.co/go/tools. It looks like the dominikh/go-tools#1335 fix has not yet been included in a tagged release from that repo: that fix landed in Dec 2022, but the last release v0.3.3 was cut in July 2022. Perhaps the fix here is
|
Welcome
Description of the problem
Now that go1.20 has officially been released, I decided to come back and check on compatibility with golangci-lint again. I can reproduce the exact same error as @atc0005 reported a month and a half ago in #3420 (comment):
(Note that I am filing this as a separate bug, rather than continuing conversation there, because this is about goanalysis_metalinter whereas that bug was initially about the typecheck linter.)
If I instead install golangci-lint at master, I get the same result:
Output is given below in the "Verbose output of running" section.
In both cases, the salient error text is:
This appears to be the same issue as was addressed by dominikh/go-tools#1335 for that repo, but golangci-lint doesn't appear to have a dependency on that repo so I don't believe that fix has any impact on this project's behavior.
Are there any updates on what needs to change to avoid this issue?
Version of golangci-lint
Both v1.50.1 and tip-of-master exhibit this behavior:
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: