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
go: /opt/homebrew/bin/go: go version go1.23.3 darwin/arm64
gopls: /Users/daniel/go/bin/gopls (version: v0.16.2 built with go: go1.23.0)
gotests: not installed
gomodifytags: not installed
impl: not installed
goplay: not installed
dlv: /Users/daniel/go/bin/dlv (version: v1.23.0 built with go: go1.23.0)
staticcheck: /Users/daniel/go/bin/staticcheck (version: v0.5.1 built with go: go1.23.0)
When I run Tasks: Configure Default Build Task from the command palette, the go view gets added to the explorer window within vscode. This happens instantly (without clicking any option after the configure command), with the go task provider disabled, and will not disappear until you refresh the window.
Steps to reproduce the behavior:
Open the command palette
Run the Tasks: Configure Default Build Task built-in command
The go extension view will appear in the explorer window
Screenshots or recordings
The text was updated successfully, but these errors were encountered:
Hi SoCuul, I was able to see what you are observing in your uploaded screenshots. I can answer some of your questions based on the code written in vscode-go.
In VSCode-Go Extension's entry point, goMain.ts, we call ExplorerProvider.Setup(). This function will create the go extension view will appear in the explorer window. This means, the go extension must be initializing when you execute Tasks: Configure Default Build Task.
By taking another look of your screenshot and my local repro, when you execute the task Tasks: Configure Default Build Task, the bottom left have some notification. (It disappears very shortly) But the notification is Activating Extensions.
My best guess would be, VSCode think it's necessary to activate all the extensions to finish Tasks: Configure Default Build Task. So when you hit enter, extensions are being initialized. Before you select which task you want to configure, the initialization is already done.
Further, if you go to the output, you can see some log from task. And vscode-go is definitely a task provider see vscode-go wiki.
I found a similar issue from vscode side see issue
Is there any concern of activating vscode-go when configuring the task?
Currently, it mostly is just visual clutter on-screen. It will show the go explorer window when I'm not working on go projects, but if I toggle it off I won't see it when I actually am.
h9jiang
changed the title
Go explorer view opens when creating default task
Go extension conditionally register explorer view based on workspace (go project)
Jan 13, 2025
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.code -v
orcode-insiders -v
to get version of VS Code or VS Code Insiders.f1a4fb101478ce6ec82fe9627c43efbf9e98c813
arm64
Go: Locate Configured Go Tools
command.Tools Configuration
Environment
GOBIN: undefined
toolsGopath:
gopath: /Users/daniel/go
GOROOT: /opt/homebrew/Cellar/go/1.23.3/libexec
PATH: /usr/local/opt/make/libexec/gnubin:/Users/daniel/.rbenv/shims:/Users/daniel/Library/pnpm:/Users/daniel/.nvm/versions/node/v22.11.0/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/opt/X11/bin:/Library/Apple/usr/bin:/Applications/Wireshark.app/Contents/MacOS:/Applications/VMware Fusion.app/Contents/Public:/usr/local/share/dotnet:~/.dotnet/tools:/usr/local/go/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Users/daniel/.orbstack/bin:/Users/daniel/bin:/Users/daniel/Library/Python/3.11/bin:/Users/daniel/Library/Python/3.12/bin:/Users/daniel/scripts:/Users/daniel/.spicetify:/bin:/Users/daniel/go/bin:/Users/daniel/Library/Android/sdk/tools/bin:/Users/daniel/Library/Android/sdk/platform-tools:/Users/daniel/Library/Android/sdk/emulator
Tools
Go env
Workspace Folder (test): /Users/daniel/test
Share the Go related settings you have added/edited
Describe the bug
When I run
Tasks: Configure Default Build Task
from the command palette, the go view gets added to the explorer window within vscode. This happens instantly (without clicking any option after the configure command), with the go task provider disabled, and will not disappear until you refresh the window.Steps to reproduce the behavior:
Tasks: Configure Default Build Task
built-in commandScreenshots or recordings
The text was updated successfully, but these errors were encountered: