Navigation Menu

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

Jump to bottom

cmd/go: mod why -m is not strict when parsing an import path #36658

Open
perillo opened this issue Jan 20, 2020 · 1 comment
Open

cmd/go: mod why -m is not strict when parsing an import path #36658

perillo opened this issue Jan 20, 2020 · 1 comment
Labels
help wanted modules NeedsFix The path to resolution is known, but the work has not been done.
Milestone
Backlog

Comments

@perillo
Copy link
Contributor

perillo commented Jan 20, 2020 •
edited

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

$ go version
go version go1.13.6 linux/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="on"
GOARCH="amd64"
GOBIN="/home/manlio/.local/bin"
GOCACHE="/home/manlio/.cache/go-build"
GOENV="/home/manlio/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB="github.com/perillo/*"
GOOS="linux"
GOPATH="/home/manlio/.local/lib/go:/home/manlio/src/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/manlio/src/go/src/github.com/perillo/database/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-build853843883=/tmp/go-build -gno-record-gcc-switches"
GOROOT/bin/go version: go version go1.13.6 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.13.6
uname -sr: Linux 5.4.12-arch1-1
/usr/lib/libc.so.6: GNU C Library (GNU libc) stable release version 2.30.
gdb --version: GNU gdb (GDB) 8.3.1

What did you do?

In a project that depends on golang.org/x/tools/go/packages, I executed

go mod why -m golang.org/x/tools/

What did you expect to see?

go: malformed import path "golang.org/x/tools/": trailing slash

as it is done by go mod init.

What did you see instead?

# golang.org/x/tools/
(main module does not need module golang.org/x/tools/)
@jayconrod jayconrod added the NeedsFix The path to resolution is known, but the work has not been done. label Jan 21, 2020
@jayconrod jayconrod added this to the Backlog milestone Jan 21, 2020
@GrigoriyMikhalkin GrigoriyMikhalkin mentioned this issue Jan 23, 2020
Closed
@gopherbot
Copy link

Change https://golang.org/cl/216097 mentions this issue: cmd/go: validate module path in mod why

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted modules NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Milestone
Backlog
Development

Successfully merging a pull request may close this issue.

cmd/go: validate module path in mod why GrigoriyMikhalkin/go
4 participants
@jayconrod @bcmills @perillo @gopherbot