-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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/gopls: stuck on "Setting up workspace: Loading packages..." #42255
Comments
Thanks for the report! Can you please share the |
Thanks for the quick reply. @stamblerre Here is the output:
|
Is there anything more after the |
Thanks for clarifying. A few things to try, suggested by @hyangah:
"gopls": {
"verboseOutput": true
}
|
|
am I adding this to settings.json in vscode ?
In any case there is no output for "gopls" |
Yep, that's correct. But thanks for the output of the process explorer command. I tried to reproduce with the same repository, and it did take a long time for the packages to be loaded. How long are you waiting before looking at the logs? |
I've let it run for 30 mins minimum and have had it run for up to an an hour. How long did it take for you ? |
Ah, it only took me a minute or two with a clean module cache. Have you tried "Developer: Reload Window" to try restarting it? |
yea, I've retried restarting the window, a system restart as well...any other ideas ? |
One last thing to try might be It does seem like you may have run into something similar to #42132. I would make sure you kill the /cc @heschik |
I tried running the command from process 3699 and it's just never returning, so I think you may be right on the similarity to 42132 |
If you can reliably reproduce the problem that's pretty interesting. Please run the command with |
@heschik I tried using gopls version 0.5.0 to no avail. With version 0.5.0, the process explorer output
running comand in terminal: killed process of
|
Ugh. goroutine 1 is, of course, the one we need. Sorry, but can you run the Can you check that you don't have any strange symlinks set up, or huge directories inside the module? |
do you run that command with
That gave a long output. Do you want the whole thing ? |
If it succeeded, it's not interesting. That environment setting should allow us to get a full traceback using |
I'm saying when I killed it, it gave a long output... |
Oh. Yes, I want the whole thing, please. Upload it to a gist if it's really huge? |
@heschik I just nuked the repo and cloned again. gopls is working fine now...Sorry if that ruins the test. If it starts hanging again, I'll ping you. Thanks for the help. |
I'm glad it's working again. It sounds like the deadline suggested in #42132 might solve the issue of Since things are working again, I'm going to go ahead and close this as a duplicate of #42132, but please open a new issue if you see this again and can reproduce it. |
I confirm that this works, people. Do not try to understand this, JUST NUKE AND RECLONE. I wasted 3 hours on this and nobody has a real answer. just my friendly advice. |
Doesn't help. Even when I clone a completely different repo I experience the same issue. |
@yury-kozlov: Please see the Troubleshooting guide and file an issue if necessary. |
Describe the bug
I upgraded to go 1.15.3, updated golang tools including the Go extension and the extension is stuck on "Loading packages..."
Screenshots or recordings
If applicable, add screenshots or recordings to help explain your problem.
The text was updated successfully, but these errors were encountered: