Skip to content
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

x/tools/gopls: Unrelated debug session triggering editing warning #42423

Closed
ermik opened this issue Nov 6, 2020 · 1 comment
Closed

x/tools/gopls: Unrelated debug session triggering editing warning #42423

ermik opened this issue Nov 6, 2020 · 1 comment
Labels
Milestone

Comments

@ermik
Copy link

@ermik ermik commented Nov 6, 2020

What version of Go are you using (go version)?

$ go version
go version go1.13.4 darwin/amd64

Does this issue reproduce with the latest release?

Yes

What operating system and processor architecture are you using (go env)?

go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/ermik/Library/Caches/go-build"
GOENV="/Users/ermik/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/ermik/Projects/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.13.4/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.13.4/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
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 -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/wp/bpblv6xj33n17_8pr7h8k1t40000gn/T/go-build620241596=/tmp/go-build -gno-record-gcc-switches -fno-common"

What is your version of gopls (gopls version)?

$ gopls version
golang.org/x/tools/gopls v0.5.0
    golang.org/x/tools/gopls@v0.5.0 h1:XEmO9RylgmaXp33iGrWfCGopVYDGBmLy+KmsIsfIo8Y=

What did you do?

  • Open workspace which combines a Go project (workspace has a folder which contains go.mod) and a Node.js project
  • Start debug session for the Node.js project
  • Edit Go source code

What did you expect to see?

Editing is straightforward with no notices or warnings.

What did you see instead?

A warning:

A debug session is currently active. Changes to your Go files may result in unexpected behaviour.

which refers to a debug session inconsequential to the Go environment.

@gopherbot gopherbot added this to the Unreleased milestone Nov 6, 2020
@ermik
Copy link
Author

@ermik ermik commented Nov 6, 2020

Eh, I think this is a golang/vscode-go thing, apologies.

@ermik ermik closed this Nov 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants