go get -u cloud.google.com/go/ fails "unrecognized import path "cloud.google.com/go"" #820

macrael · 2017-12-04T23:02:45Z

It appears that the website cloud.google.com/go has been taken down.

I can't build my projects because an import for "cloud.google.com/go" doesn't download anything. The site https://cloud.google.com/go no longer has the required meta tag to point to the repo.

Please resolve this, my build process is broken right now.

elithrar · 2017-12-04T23:05:59Z

As a fellow user: go get -v -u cloud.google.com/go Fetching https://cloud.google.com/go?go-get=1 Parsing meta tags from https://cloud.google.com/go?go-get=1 (status code 200) cloud.google.com/go (download) Is there an intermediate proxy that might be interfering?

…

On Mon, Dec 4, 2017 at 3:04 PM MacRae Linton ***@***.***> wrote: It appears that the website cloud.google.com/go has gone down. I can't build my projects because an import for "cloud.google.com/go" doesn't download anything. The site https://cloud.google.com/go no longer has the required meta tag to point to the repo. Please resolve this, my build process is broken right now. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#820>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABIcBnmPu-4IKuuDQIwomMT0SBQQdIOks5s9HoVgaJpZM4Q1dhk> .

macrael · 2017-12-04T23:10:17Z

$ go get -v -u cloud.google.com/go
Fetching https://cloud.google.com/go?go-get=1
Parsing meta tags from https://cloud.google.com/go?go-get=1 (status code 200)
package cloud.google.com/go: unrecognized import path "cloud.google.com/go" (parse https://cloud.google.com/go?go-get=1: no go-import meta tags ())

macrael · 2017-12-04T23:10:46Z

that site was 404 for me for a minute, and when I grep through the page returned currently I don't see any meta tags.

timfallmk · 2017-12-05T00:02:04Z

I've confirmed that the problem appears to be missing go import tags: From golang.org:

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<meta name="go-import" content="golang.org/x/net git https://go.googlesource.com/net">
<meta name="go-source" content="golang.org/x/net https://github.com/golang/net/ https://github.com/golang/net/tree/master{/dir} https://github.com/golang/net/blob/master{/dir}/{file}#L{line}">
<meta http-equiv="refresh" content="0; url=https://godoc.org/golang.org/x/net">
</head>

Equivalent section on cloud.google.com/go (with forwarding) shows no go related tags.

bradfitz · 2017-12-05T00:07:11Z

Hey @broady, this is bad. Please escalate.

Looks like the URL path canonicalization (GET /go/bigtable?go-get=1 => /go/bigtable/?go-get=1) is happening before the go-get=1 special-casing.

dfawley · 2017-12-05T00:08:20Z

FWIW, I filed an internal bug about this.

ankurcha · 2017-12-05T00:09:22Z

And this is why we should vendor the internet before building software?

timfallmk · 2017-12-05T00:10:46Z

@ankurcha Also breaks vendoring:

dep ensure -v --vendor-only
grouped write of manifest, lock and vendor: error while writing out vendor tree: failed to write dep tree: failed to export cloud.google.com/go: unable to deduce repository and source type for "cloud.google.com/go": unable to read metadata: go-import metadata not found

I appreciate your snark, but even that breaks 😉

bradfitz · 2017-12-05T00:16:19Z

@timfallmk, it breaks updating vendored deps, but not people who've already vendored their deps and just want to hack on & rebuild their own code.

ankurcha · 2017-12-05T00:16:26Z

Sorry didn't mean to be snarky. Just spent a good half an hour trying to figure out what broke my day long roll. :-/

Actually, I also noticed it when my dep ensure --vendor-only step broke

timfallmk · 2017-12-05T00:18:29Z

@bradfitz Fair enough. It's a fine distinction. Unfortunately, it also breaks (at least for dep) when checking to see if vendored dependencies should be updated. Your point is well taken however.

chetananand · 2017-12-05T00:26:55Z

If someone is using glide for vendoring, then adding something like:

package: cloud.google.com/go
vcs: git
repo: https://code.googlesource.com/gocloud
subpackages:
  - compute/metadata
  - internal/version

will help as a temporary workaround.

jba · 2017-12-05T00:28:30Z

We've found the problem and are working on a solution.

jba · 2017-12-05T00:33:43Z

This should be fixed. Ping this issue if it's still a problem.

macrael · 2017-12-05T01:28:15Z

Thanks all!

scottpettyjohn · 2018-11-20T16:49:50Z

I am having the same issue described.
go get -v -u cloud.google.com/go
Fetching https://cloud.google.com/go?go-get=1
https fetch failed: Get https://cloud.google.com/go?go-get=1: x509: certificate signed by unknown authority
package cloud.google.com/go: unrecognized import path "cloud.google.com/go" (https fetch: Get https://cloud.google.com/go?go-get=1: x509: certificate signed by unknown authority)

If I use the -insecure flag, I get the missing meta-tag:

go get -v -u -insecure cloud.google.com/go/...
Fetching https://cloud.google.com/go?go-get=1
https fetch failed: Get https://cloud.google.com/go?go-get=1: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Fetching http://cloud.google.com/go?go-get=1
Parsing meta tags from http://cloud.google.com/go?go-get=1 (status code 401)
package cloud.google.com/go/...: unrecognized import path "cloud.google.com/go/..." (parse http://cloud.google.com/go?go-get=1: no go-import meta tags ())

bradfitz · 2018-11-20T18:03:11Z

@scottpettyjohn, looks like you're having a different problem. Also, this issue is closed and almost a year old.

Can you file a new bug? We don't track old, closed bugs.

You might be missing a ca-certificates package or something, but you should include details about your OS & version in a new bug you file (not here).

Ark-kun · 2020-01-31T23:13:52Z

Having this again:

go: cloud.google.com/go@v0.44.3: unrecognized import path "cloud.google.com/go" (parse https://cloud.google.com/go?go-get=1: no go-import meta tags ())

tbpg · 2020-02-03T20:21:26Z

Thank you for the report. Unfortunately, I'm not seeing the error right now.

Do you have a proxy enabled? That would sidestep this issue in the future.

$ go env GOPROXY
https://proxy.golang.org,direct

broady · 2020-02-03T20:25:45Z

Locking this issue. If you see something similar, please open a new bug.

bradfitz assigned broady Dec 5, 2017

jba self-assigned this Dec 5, 2017

jba closed this as completed Dec 5, 2017

jeanbza mentioned this issue Nov 20, 2018

Repeat of issue #820 #1228

Closed

chrislusf mentioned this issue Mar 20, 2019

notification: add Go CDK pubsub support seaweedfs/seaweedfs#895

Merged

emirb mentioned this issue Apr 22, 2019

unrecognized import path "cloud.google.com/go" go-gorm/gorm#2415

Closed

googleapis locked as resolved and limited conversation to collaborators Feb 3, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

go get -u cloud.google.com/go/ fails "unrecognized import path "cloud.google.com/go"" #820

go get -u cloud.google.com/go/ fails "unrecognized import path "cloud.google.com/go"" #820

macrael commented Dec 4, 2017 •

edited

elithrar commented Dec 4, 2017 via email

macrael commented Dec 4, 2017

macrael commented Dec 4, 2017

timfallmk commented Dec 5, 2017

bradfitz commented Dec 5, 2017

dfawley commented Dec 5, 2017

ankurcha commented Dec 5, 2017

timfallmk commented Dec 5, 2017 •

edited

bradfitz commented Dec 5, 2017

ankurcha commented Dec 5, 2017

timfallmk commented Dec 5, 2017

chetananand commented Dec 5, 2017

jba commented Dec 5, 2017

jba commented Dec 5, 2017

macrael commented Dec 5, 2017

scottpettyjohn commented Nov 20, 2018

bradfitz commented Nov 20, 2018 •

edited

Ark-kun commented Jan 31, 2020

tbpg commented Feb 3, 2020

broady commented Feb 3, 2020

go get -u cloud.google.com/go/ fails "unrecognized import path "cloud.google.com/go"" #820

go get -u cloud.google.com/go/ fails "unrecognized import path "cloud.google.com/go"" #820

Comments

macrael commented Dec 4, 2017 • edited

elithrar commented Dec 4, 2017 via email

macrael commented Dec 4, 2017

macrael commented Dec 4, 2017

timfallmk commented Dec 5, 2017

bradfitz commented Dec 5, 2017

dfawley commented Dec 5, 2017

ankurcha commented Dec 5, 2017

timfallmk commented Dec 5, 2017 • edited

bradfitz commented Dec 5, 2017

ankurcha commented Dec 5, 2017

timfallmk commented Dec 5, 2017

chetananand commented Dec 5, 2017

jba commented Dec 5, 2017

jba commented Dec 5, 2017

macrael commented Dec 5, 2017

scottpettyjohn commented Nov 20, 2018

bradfitz commented Nov 20, 2018 • edited

Ark-kun commented Jan 31, 2020

tbpg commented Feb 3, 2020

broady commented Feb 3, 2020

macrael commented Dec 4, 2017 •

edited

timfallmk commented Dec 5, 2017 •

edited

bradfitz commented Nov 20, 2018 •

edited