Closed
Description
From the slack https://gophers.slack.com/archives/C2B4L99RS/p1594808544075000
This was after getting the prompt from the Go extension to update the tools after detecting a new Go version. All other items were updated successfully, but not gocode. I then opted to try and install it separately via "Go: Install/Update Tools" VSCode option.
Ubuntu system:
Installing 1 tool at /home/adam/go/bin in module mode.
gocode
1 tools failed to install.
gocode: Failed to close gocode process: Error: Command failed: /home/adam/go/bin/gocode close
2020/07/15 05:18:08 dial unix /tmp/gocode-daemon.adam: connect: no such file or directory
Windows system:
Tools environment: GOPATH=C:\Users\atc0005\go
Installing 1 tool at C:\Users\atc0005\go\bin in module mode.
gocode
1 tools failed to install.
gocode: Failed to close gocode process: Error: Command failed: C:\Users\atc0005\go\bin\gocode.exe close
2020/07/15 05:10:15 dial tcp 127.0.0.1:37373: connectex: No connection could be made because the target machine actively refused it.
The corresponding logic is https://github.com/golang/vscode-go/blob/master/src/goTools.ts#L185-L200
@stamblerre I am not familiar with gocode
's closing logic. Is it necessary? And shouldn't the extension avoid this if gocode is not in use?