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
x/tools/cmd/gopls: no CheckPackageHandles for file #35081
Comments
Thank you for filing a gopls issue! Please take a look at the Troubleshooting guide, and make sure that you have provided all of the relevant information here. |
Following the troubleshooting guide:
Running that command yields:
|
Oh, ugh, I typed it as |
|
Can you share the output of |
I'm realizing now that $GOPATH/src/github.com/fsnotify/fsnotify doesn't exist. I didn't previously notice this because I usually run justrun in projects that have vendored all dependencies. Still, it seems like we could present a better error message here besides "no CheckPackageHandles." |
Did that error message come up when you tried to go to the definition of the unknown variable? |
Yes - when I hovered over "NewWatcher" in watch.go and hit |
Did it say "no CheckPackageHandles" for the nonexistent package or for the original package? |
The original package, justrun/watch.go. Here's what's in the vim log:
|
Ok, so I'm thinking that this sounds very similar to #34012, in that an import failing to resolve causes all language features to fail. I will then close this as a duplicate. |
Duplicate of #34012 |
OK, thank you for investigating. |
GO111MODULE=on go install -v ./...
.$GOPATH/src/github.com/jmhodges/justrun
:GoDef
while the cursor is onNewWatcher
.If I have
GO111MODULE=on
for step 4 I get the definition, as expected - if it is off, I get "no CheckPackageHandles for file /path/to/watch.go."I am also having trouble figuring out how to export logs, I can start vim-go with these settings:
but the window at the bottom with gopls log messages scrolls off of the right edge of my screen, and it's not clear if they are also being written to a log file somewhere.
The text was updated successfully, but these errors were encountered: