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

proxy.golang.org: module upgrade not detecting new tag #40170

Closed
kevingentile opened this issue Jul 12, 2020 · 5 comments
Closed

proxy.golang.org: module upgrade not detecting new tag #40170

kevingentile opened this issue Jul 12, 2020 · 5 comments
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@kevingentile
Copy link

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

$ go version
  version go1.14.4 darwin/amd64

Does this issue reproduce with the latest release?

yes, using latest stable release

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

go env

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



$ go env

What did you do?

go clean -modcache
go get github.com/govice/golinks@v0.1.1

What did you expect to see?

Package upgraded to recently pushed tag (from v0.1.0 -> v0.1.1

What did you see instead?

go: github.com/govice/golinks@v0.1.1/go.mod: verifying module: github.com/govice/golinks@v0.1.1/go.mod: reading https://sum.golang.org/lookup/github.com/govice/golinks@v0.1.1: 410 Gone
        server response: not found: github.com/govice/golinks@v0.1.1: invalid version: unknown revision v0.1.1

It's worth noting that prior to attempting this upgrade I deleted two invalid tags from the govice/golinks repository (v0 and v.0.1.1)

@kevingentile
Copy link
Author

Tried this upgrade again ~11 hours after posting this issue and it succeeded.

@andybons
Copy link
Member

@katiehockman @hyangah @heschik

@andybons andybons added this to the Unplanned milestone Jul 13, 2020
@andybons andybons added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jul 13, 2020
@heschi
Copy link
Contributor

heschi commented Jul 13, 2020

The version was added a few minutes after this issue was posted. I haven't fully verified but this is almost certainly a case where the version was fetched before it actually existed. In that case proxy.golang.org will cache its nonexistance for up to about half an hour.

@heschi heschi closed this as completed Jul 13, 2020
@kevingentile
Copy link
Author

Is there a way to flush the cache from my end? @heschik

@heschi
Copy link
Contributor

heschi commented Jul 13, 2020

Sorry, no; generally we just suggest you make sure not to try to fetch it before you tag it. Or just wait a little while.

Setting GOPRIVATE for modules you own will avoid accidentally fetching them early, though by the same token doesn't guarantee that they have been successfully fetched.

@golang golang locked and limited conversation to collaborators Jul 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Development

No branches or pull requests

4 participants