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: "no dep handle: no metadata" using -remote #38557

Closed
myitcv opened this issue Apr 21, 2020 · 1 comment
Closed

x/tools/gopls: "no dep handle: no metadata" using -remote #38557

myitcv opened this issue Apr 21, 2020 · 1 comment

Comments

@myitcv
Copy link
Member

@myitcv myitcv commented Apr 21, 2020

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

$ go version
go version devel +801cd7c84d Thu Apr 2 09:00:44 2020 +0000 linux/amd64
$ go list -m golang.org/x/tools
golang.org/x/tools v0.0.0-20200408132156-9ee5ef7a2c0d => github.com/myitcvforks/tools v0.0.0-20200420133701-6e8c44031a50
$ go list -m golang.org/x/tools/gopls
golang.org/x/tools/gopls v0.0.0-20200408132156-9ee5ef7a2c0d => github.com/myitcvforks/tools/gopls v0.0.0-20200420133701-6e8c44031a50

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="/home/myitcv/.cache/go-build"
GOENV="/home/myitcv/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/myitcv/gostuff"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/myitcv/gos"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/myitcv/gos/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/myitcv/.vim/plugged/govim/go.mod"
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-build565813386=/tmp/go-build -gno-record-gcc-switches"

What did you do?

I'm unclear what sequence of steps exactly led to the remote instance of getting into such a state, but opening the Hugo project using -remote causes errors like the following in the forwarded log:

Params: {"type":1,"message":"2020/04/21 09:20:39 no dep handle: no metadata for golang.org/x/text/runes\n\tpackage=\"golang.org/x/text/runes\""}

This manifests in lots of import-related and derivative errors in diagnostics.

If I do not use -remote, then there are no diagnostics returned.

What did you expect to see?

No diagnostic errors when using -remote

What did you see instead?

As above. The full forwarder gopls log is: gopls_20200421_0920_37_997036168.log


cc @stamblerre @findleyr

FYI @leitzler

@gopherbot gopherbot added this to the Unreleased milestone Apr 21, 2020
@gopherbot gopherbot added the Tools label Apr 21, 2020
@myitcv
Copy link
Member Author

@myitcv myitcv commented Apr 21, 2020

This was my error. Closing.

@myitcv myitcv closed this Apr 21, 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
You can’t perform that action at this time.