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: go mod init doesn't recognize GOPROXY #35931

Closed
yaxinlx opened this issue Dec 2, 2019 · 3 comments
Closed

cmd/go: go mod init doesn't recognize GOPROXY #35931

yaxinlx opened this issue Dec 2, 2019 · 3 comments
Labels
FrozenDueToAge modules NeedsFix The path to resolution is known, but the work has not been done.
Milestone
Go1.15

Comments

@yaxinlx
Copy link

yaxinlx commented Dec 2, 2019 •
edited

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

$ go version
go version go1.13.4 linux/amd64

Does this issue reproduce with the latest release?

Yes

What did you do?

$ git clone https://github.com/heketi/heketi.git
$ cd heketi
$ go mod init github.com/heketi/heketi
go: creating new go.mod: module github.com/heketi/heketi
go: copying requirements from glide.lock
go: converting glide.lock: stat k8s.io/apiserver@c809cf8581e1e44c6174bf5ab4415e6ee39965ca: unrecognized import path "k8s.io/apiserver" (https fetch: Get https://k8s.io/apiserver?go-get=1: dial tcp 35.201.71.162:443: connect: connection refused)
go: converting glide.lock: stat golang.org/x/text@2910a502d2bf9e43193af9d68ca516529614eed3: unrecognized import path "golang.org/x/text" (https fetch: Get https://golang.org/x/text?go-get=1: dial tcp 216.239.37.1:443: connect: connection refused)
go: converting glide.lock: stat golang.org/x/crypto@d172538b2cfce0c13cee31e647d0367aa8cd2486: unrecognized import path "golang.org/x/crypto" (https fetch: Get https://golang.org/x/crypto?go-get=1: dial tcp 216.239.37.1:443: connect: connection refused)
go: converting glide.lock: stat k8s.io/client-go@3627aeb7d4f6ade38f995d2c923e459146493c7e: unrecognized import path "k8s.io/client-go" (https fetch: Get https://k8s.io/client-go?go-get=1: dial tcp 35.201.71.162:443: connect: connection refused)
...

What did you expect to see?

Use GOPROXY to fetch modules

What did you see instead?

But not, so many fetching fail.
@cagedmantis cagedmantis added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Dec 2, 2019
@cagedmantis cagedmantis added this to the Backlog milestone Dec 2, 2019
@cagedmantis
Copy link
Contributor

This error happens when a custom remote import path has been used and the user can't query the domain. I was able to recreate this issue by bypassing the domain name resolution for k8s.io and golang.org via an edit to a local /etc/hosts file.
@bcmills @jayconrod

@oiooj
Copy link
Member

oiooj commented Dec 3, 2019

Yes, now ConvertLegacyConfig not use GOPROXY, I think we need fix this.

@oiooj oiooj added modules NeedsFix The path to resolution is known, but the work has not been done. and removed NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Dec 3, 2019
@oiooj oiooj modified the milestones: Backlog, Go1.15 Dec 3, 2019
@bcmills
Copy link
Contributor

bcmills commented Dec 4, 2019

Duplicate of #33767

@bcmills bcmills marked this as a duplicate of #33767 Dec 4, 2019
@bcmills bcmills closed this as completed Dec 4, 2019
@golang golang locked and limited conversation to collaborators Dec 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge modules NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Milestone
Go1.15
Development

No branches or pull requests
5 participants
@cagedmantis @oiooj @bcmills @gopherbot @yaxinlx