-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools/gopls: no import for [...] #33395
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
Comments
Can you try upgrading to master ( If it still crashes, can you try rebuilding |
If I do this on one of the packages in my repo it passes that same message (no parsed files for package) for gorilla/mux. I'll try the patch next. |
I didn't end up trying the patch. As you noted switching to master fixed the crashing. I'm not sure if you wanted the other errors split off into a separate issue. If you do just let me know. Thanks for the help! This has already moved miles ahead from my previous experience. |
Glad to hear that master is working better! What is the output of |
Yeah, I've seen those kind of messages before.
It seems to be talking less about my project and seems to be talking about the gopls installation itself? Which it is certainly right, there is no go.mod in that tools directory. |
What does your |
go.mod:
I do run
One thing I did notice is that my modules directory (
|
After cleaning my module cache and running that command, I consistently get
I'm not sure how v0.1.4 is even possible, since we've never tagged it. But that shouldn't be related to the behavior of the |
I removed some potentially sensitive imports but otherwise this is intact. |
Can you try |
|
Based on the output of this command, it looks like |
@Mattouille: Is this still an issue for you? |
Closing as obsolete. |
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?
This occurs during normal operation of gopls
What did you expect to see?
It locates the package on my system
What did you see instead?
It said the package was missing
@stamblerre requested the following output:
The text was updated successfully, but these errors were encountered: