Ask questionscmd/go: invalid version: unknown revision when GOPROXY/GOSUMDB disabled

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

<pre> $ go version go version go1.13.5 linux/amd64 </pre>

Does this issue reproduce with the latest release?

1.13.6 is not yet packaged for my distro

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

<details><summary><code>go env</code> Output</summary><br><pre> $ go env GO111MODULE="" GOARCH="amd64" GOBIN="" GOCACHE="/home/cape/.cache/go-build" GOENV="/home/cape/.config/go/env" GOEXE="" GOFLAGS="" GOHOSTARCH="amd64" GOHOSTOS="linux" GONOPROXY="" GONOSUMDB="" GOOS="linux" GOPATH="/home/cape/dev" GOPRIVATE="*" GOPROXY="direct" GOROOT="/usr/lib/golang" GOSUMDB="off" GOTMPDIR="" GOTOOLDIR="/usr/lib/golang/pkg/tool/linux_amd64" GCCGO="gccgo" AR="ar" CC="gcc" CXX="g++" CGO_ENABLED="1" GOMOD="/home/cape/dev/src/" 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-build206448337=/tmp/go-build -gno-record-gcc-switches" </pre></details>

(The only concious override from defaults is setting export* in .bashrc, the rest are changed by go or the distro)

What did you do?

<!-- If possible, provide a recipe for reproducing the error. A complete runnable program is good. A link on is best. --> Clone, go mod download. Note that there are no private repos involved.

What did you expect to see?


What did you see instead?

go: invalid version: unknown revision ca3e8f451dd0


Troubleshooting was done on Slack with @Helcaraxan, see

The error was resolved by overriding the Fedora defaults of GOPROXY=direct, GOSUMDB=off (see here for the reasoning).

It seems unexpected that disabling sum checks would prevent fetching a specific dependency? I've been using the setup for several months without running into this with other repos.

Note that there are no firewalls/proxies other things intercepting traffic, so access to Github is not a problem.


Answer questions Helcaraxan

Tl;dr - The upstream users fluxcd/helm-operator should update the version of fluxcd/flux that they are referencing.

Ok. Dug a bit further and solved the problem. It's not an issue with the go toolchain itself.

  • The top-level module that is being build, fluxcd/helm-operator, references fluxcd/flux@ca3e8f451dd0 in its requires.
  • That commit, although it still can be accessed via the GitHub UI is no longer part of the actual git history of the fluxcd/flux repo. It is still visible most likely as part of a fork (as you can access commits from all forks from any repo in the network via the web UI).
  • This pseudo-version was however appropriately cached by the module proxy. Protecting users against the disappearance of the underlying commit, as it is intended to do.
  • The forced setting in Fedora's DNF package for Go of GOPROXY=direct instead of the usual GOPROXY= then resulted in the case of @carlpett to bypass the proxy and instead try to clone the actual repo and find the appropriate revision which had already been deleted.

I believe this means we can close this issue.

Duco van Amstel Helcaraxan @improbable London, UK Software engineer with a pinch of product management and a dash of developer relationship.
Github User Rank List