language server(gopls) not working #2768
Comments
seems like the same issue as #2767 |
got the same issue, after upgrading vscode-go to |
I also encountered the same problem, unable to pull up the gopls version at 0.11.5, 0.11.4 is normal |
Thanks for reporting everyone Can one of you check the logs and share any errors that you see there?
Another place to check is the logs from the Extension Host
@stamblerre has found a potential reason for the language server to not load and has a fix for that. Please give that a try as well via the latest beta version of this extension |
Log from Developer tools for version
|
VSCode remote-container with go-extension 0.11.5 and gopls v0.1.7 does not work too. And after switching to 0.11.4 it works again, however it noticed me to rebuild go tools for go version has changed, but I'm using the same go in the same container. |
I have the same problem. this is my settings.json for vscode-go version of vscode: 1.38.1 |
Thanks for your solution! |
@enix223, @kidlj, @js00070, |
0.11.6-beta.1 works perfectly! Thanks! |
Hello all, I have just released an update(0.11.6) where we have replaced the outgoing call with known hard-coded value of the latest version for gopls. This should fix the problem reported here. I have logged an issue #2776 to discuss next steps on how to make this check better, please feel free to provide your thoughts there. |
After setting
go.useLanguageServer
totrue
, this plugin basically stops working: no auto-completion, no go-to-definition, no quick-info-on-hover.When I try to restart the language server, the following message shows up.
Detailed info of my vscode:
Version: 1.38.1
Commit: b37e54c98e1a74ba89e03073e5a3761284e3ffb0
Date: 2019-09-11T13:31:32.854Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 18.7.0
Version of the this plugin I am using: 0.11.5
Version of gopls:
golang.org/x/tools/gopls v0.1.7
golang.org/x/tools/gopls@v0.1.7 h1:YwKf8t9h69++qCtVmc2q6fVuetFXmmu9LKoPMYLZid4=
The text was updated successfully, but these errors were encountered: