-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools/gopls: slow when typing imports #34414
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
Thank you for filing a gopls issue! Please take a look at the Troubleshooting section of the gopls Wiki page, and make sure that you have provided all of the relevant information here. |
It seems like |
@stamblerre thanks for the help. I hope this isn't due to some wierd setup I have going. I'm also not sure if it is a VSCode issue rather than I treid to recreate in a more controlled setting... I created a new directory at
|
Thank you for the detailed report! I think the issue here is basically that we run |
Change https://golang.org/cl/200058 mentions this issue: |
I am observing a long delay for each character typed in response from
gopls
. Output fromgopls
in VSCode sometimes shows an especially long time ingo list
:go pls
outputI am not familiar with the language server concept, so I'm not sure if this is a
gopls
issue or a VSCode issue, although I have occasionally observed a delay using vim (though not repeatable, and it appears to mainly querygopls
on save, whereas VSCode seems to querygopls
on every keystroke).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?
Type the following into VSCode, (not copy/paste):
What did you expect to see?
Quick feedback of:
missing variable type or initialization
What did you see instead?
A long delay, many errors, and finally
missing variable type or initialization
. The following replays 82 seconds at 10x:The text was updated successfully, but these errors were encountered: