-
Notifications
You must be signed in to change notification settings - Fork 763
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
Language server fails to start #2909
Comments
Note:
This may be related to the larger client/server connection error? I have also opened golangci/golangci-lint#3984 to investigate installation issues with golangci-lint@latest using |
Closing as a duplicate of golang/go#61190. See also: golang/go#61229. |
btw, this might be caused by having the latest Xcode 15 beta installed. I just removed that and went back to 14 and things are working great for me. (I was getting the exact same error). |
@lwdupont how did you do this? this is going to be a really common issue as more people upgrade macOS and unknowingly break their go setup |
What version of Go, VS Code & VS Code Go extension are you using?
Version Information
macOS Sonoma public beta 2, build
23A5301h
Run
go version
to get version of Go from the VS Code integrated terminal.go version go1.20.7 darwin/arm64
Run
gopls -v version
to get version of Gopls from the VS Code integrated terminal.Run
code -v
orcode-insiders -v
to get version of VS Code or VS Code Insiders.Check your installed extensions to get the version of the VS Code Go extension
Run Ctrl+Shift+P (Cmd+Shift+P on Mac OS) >
Go: Locate Configured Go Tools
command.Share the Go related settings you have added/edited
Describe the bug
The
gopls
client fails to connect to the server. Immediately upon starting VSCode there are 3 notifications produced:gopls client: couldn't create connection to server.
The gopls server failed to initialize.
gopls has crashed, but you are using an outdated version. Please update to the latest version of gopls.
Clicking "Go to output" reveals only the following:
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: