vscode-go icon indicating copy to clipboard operation
vscode-go copied to clipboard

Save-All does not update lint info in other buffers

Open aathan opened this issue 3 years ago • 1 comments

What version of Go, VS Code & VS Code Go extension are you using?

Version Information
  • Run go version to get version of Go from the VS Code integrated terminal. go version go1.18.4 linux/amd64

  • Run gopls -v version to get version of Gopls from the VS Code integrated terminal.

  • Run code -v or code-insiders -v to get version of VS Code or VS Code Insiders. gopls not found

  • Check your installed extensions to get the version of the VS Code Go extension v0.35.2

  • Run Ctrl+Shift+P (Cmd+Shift+P on Mac OS) > Go: Locate Configured Go Tools command. Checking configured tools.... GOBIN: undefined toolsGopath: gopath: /home/aathan/go GOROOT: /usr/local/go PATH: /home/aathan/.vscode-server/bin/e4503b30fc78200f846c62cf8091b76ff5547662/bin/remote-cli:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/local/go/bin:/usr/local/go/bin

    go: /usr/local/go/bin/go: go version go1.18.4 linux/amd64

    gotests: /home/aathan/go/bin/gotests (version: v1.6.0 built with go: go1.18.4) gomodifytags: /home/aathan/go/bin/gomodifytags (version: v1.16.0 built with go: go1.18.4) impl: /home/aathan/go/bin/impl (version: v1.1.0 built with go: go1.18.4) goplay: /home/aathan/go/bin/goplay (version: v1.0.0 built with go: go1.18.4) dlv: /home/aathan/go/bin/dlv (version: v1.9.0 built with go: go1.18.4) staticcheck: /home/aathan/go/bin/staticcheck (version: v0.3.2 built with go: go1.18.4) gopls: /home/aathan/go/bin/gopls (version: v0.9.4 built with go: go1.18.4)

go env Workspace Folder (project-new): /home/aathan/src/project GO111MODULE="" GOARCH="amd64" GOBIN="" GOCACHE="/home/aathan/.cache/go-build" GOENV="/home/aathan/.config/go/env" GOEXE="" GOEXPERIMENT="" GOFLAGS="" GOHOSTARCH="amd64" GOHOSTOS="linux" GOINSECURE="" GOMODCACHE="/home/aathan/go/pkg/mod" GONOPROXY="" GONOSUMDB="" GOOS="linux" GOPATH="/home/aathan/go" GOPRIVATE="" GOPROXY="https://proxy.golang.org,direct" GOROOT="/usr/local/go" GOSUMDB="sum.golang.org" GOTMPDIR="" GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64" GOVCS="" GOVERSION="go1.18.4" GCCGO="gccgo" GOAMD64="v1" AR="ar" CC="gcc" CXX="g++" CGO_ENABLED="1" GOMOD="/dev/null" GOWORK="" CGO_CFLAGS="-g -O2" CGO_CPPFLAGS="" CGO_CXXFLAGS="-g -O2" CGO_FFLAGS="-g -O2" CGO_LDFLAGS="-g -O2" PKG_CONFIG="pkg-config" GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build606023368=/tmp/go-build -gno-record-gcc-switches"

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.toolsManagement.autoUpdate": true,

Describe the bug

Using Save-All frequently leaves buffers with yellow underlines indicating (for example) undefined vars etc. These can be resolved by going to the file that defines the var, which is already saved (Save-All is greyed out in the File menu), and pressive Command-S (Save). It seems that Save-All does not trigger the same re-build of metadata that single-file-save does.

Steps to reproduce the behavior:

Make changes to multiple files. Use Save-All. Observe linting hints. Go to a file and Save. Observe changes in linting hints.

Screenshots or recordings

Will add if necessary.

aathan avatar Aug 28 '22 16:08 aathan

I'm having trouble reproducing this. Could you provide a code sample and more detailed reproduction steps?

jamalc avatar Aug 29 '22 18:08 jamalc

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)

gopherbot avatar Sep 29 '22 18:09 gopherbot