x/tools/gopls: "no package for ..." even after added to go.mod #36310
Labels
Milestone
Comments
To clarify, this package was not yet in the module cache? |
This module is completely new, and doing the same thing with the same module again wont trigger this behavior. |
@stamblerre this should work now, right? |
I think so. @JAicewizard: With the new |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
puts package in import -> no package for ...
go mod tidy -> no package for ...
go mod vendor (without previously existing vendor folder) -> no package for ...
reloading file -> no error
removing the import statement and adding it back -> no error
What did you expect to see?
there should be no error in the first place since it is a valid package and after go mod tidy even has a version attached to it
The text was updated successfully, but these errors were encountered: