You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Check your installed extensions to get the version of the VS Code Go extension
Version 0.44.0
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
Run Preferences: Open Settings (JSON) command to open your settings.json file.
Share all the settings with the go. or ["go"] or gopls prefixes.
"go.gopath": "/Users/d070210/go",
"go.goroot": "opt/homebrew/Cellar/go/1.24.0/libexec",
"go.testTags": "integrationtesting",
Describe the bug
My local setup always worked but somehow it stoped. Now I can run ginkgo tests but my intellisence and everything within vscode doesnt work. go commands work like a charm. GOROOT and PATH contain everything needed
Steps to reproduce the behavior:
Go to 'start vscode'
See error
where go command results in: "/opt/homebrew/Cellar/go/1.24.0/libexec/bin/go"
Screenshots or recordings
If applicable, add screenshots or recordings to help explain your problem.
okay after downgrading again to version 1.23.6 everything worked again. Seems like the plugin is not working with latest stable version!
rufreakde
changed the title
go binary not found even though PATH and even GOROOT is maintained correctly
go binary not found even though PATH and even GOROOT is maintained correctly - plugin not working with latest 1.24 version
Feb 21, 2025
@rufreakde the plugin does work with the latest version of Go. The version of Go should not matter here, as the error is saying that the Go binary itself could not be found. Can you try upgrading again? I suspect that the downgrade may have adjusted your PATH.
What version of Go, VS Code & VS Code Go extension are you using?
Version Information
go version
to get version of Go from the VS Code integrated terminal.gopls -v version
to get version of Gopls from the VS Code integrated terminal.----------
golang.org/x/tools/gopls v0.17.1
golang.org/x/tools/[email protected] h1:Mt/DSfnnSe3dyf6MH/dZZ0iww+viHNhAFc4rEYDiOAw=
github.com/BurntSushi/[email protected] h1:pxW6RcqyfI9/kWtOwnv/G+AzdKuy2ZrqINhenH4HyNs=
github.com/google/[email protected] h1:ofyhxvXcZhMsU5ulbFiLKl/XBFqE1GSq7atu8tAmTRI=
golang.org/x/exp/[email protected] h1:1P7xPZEwZMoBoz0Yze5Nx2/4pxj6nw9ZqHWXqP0iRgQ=
golang.org/x/[email protected] h1:D4nJWe9zXqHOmWqj4VMOJhvzj7bEZg4wEYa759z1pH4=
golang.org/x/[email protected] h1:fEo0HyrW1GIgZdpbhCRO0PkJajUS5H9IFUztCgEo2jQ=
golang.org/x/[email protected] h1:TCDqnvbBsFapViksHcHySl/sW4+rTGNIAoJJesHRuMM=
golang.org/x/[email protected] h1:gK/Kv2otX8gz+wn7Rmb3vT96ZwuoxnQlY+HlJVj7Qug=
golang.org/x/[email protected] h1:kgwdasJRsdDWYgWcEgMF424DiXwwXHSb3V8xVTi//i8=
golang.org/x/[email protected] h1:SP0mPeg2PmGCu03V+61EcQiOjmpri2XijexKdzv8Z1I=
honnef.co/go/[email protected] h1:4bH5o3b5ZULQ4UrBmP+63W9r7qIkqJClEA9ko5YKx+I=
mvdan.cc/[email protected] h1:bg91ttqXmi9y2xawvkuMXyvAA/1ZGJqYAEGjXuP0JXU=
mvdan.cc/xurls/[email protected] h1:lyBNOm8Wo71UknhUs4QTFUNNMyxy2JEIaKKo0RWOh+8=
go: go1.24.0
code -v
orcode-insiders -v
to get version of VS Code or VS Code Insiders.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
Run
Preferences: Open Settings (JSON)
command to open your settings.json file.Share all the settings with the
go.
or["go"]
orgopls
prefixes."go.gopath": "/Users/d070210/go",
"go.goroot": "opt/homebrew/Cellar/go/1.24.0/libexec",
"go.testTags": "integrationtesting",
Describe the bug
My local setup always worked but somehow it stoped. Now I can run ginkgo tests but my intellisence and everything within vscode doesnt work. go commands work like a charm. GOROOT and PATH contain everything needed
Steps to reproduce the behavior:
where go
command results in: "/opt/homebrew/Cellar/go/1.24.0/libexec/bin/go"Screenshots or recordings
If applicable, add screenshots or recordings to help explain your problem.
zshrc:
The text was updated successfully, but these errors were encountered: