Thanks for the report. Since this appears to be filesystem corruption and we don't know the cause, I'm going to go ahead and close this issue, but we'll watch for a pattern — if we get more reports of similar issues we'll certainly want to take a closer look.

CC @jayconrod @matloob

I'd like to note that this just happened to me as well.

$ go get -u github.com/matthewmueller/diff
go get github.com/matthewmueller/diff: module github.com/matthewmueller/diff: git ls-remote -q origin in /Users/m/Go/pkg/mod/cache/vcs/5f9f95779422363e8e24e203ef2f34dbab3a4cb052f98aa116323dc518593f13: exit status 128:
        fatal: 'origin' does not appear to be a git repository
        fatal: Could not read from remote repository.

        Please make sure you have the correct access rights
        and the repository exists.
$ git remote -v
origin  git@github.com:matthewmueller/duojs.git (fetch)
origin  git@github.com:matthewmueller/duojs.git (push)
$ rm -rf /Users/m/Go/pkg/mod/cache/vcs/5f9f95779422363e8e24e203ef2f34dbab3a4cb052f98aa116323dc518593f13
$ go get -u github.com/matthewmueller/diff
go: github.com/matthewmueller/diff upgrade => v0.0.0-20191220174011-88a65b538395
go: github.com/sergi/go-diff upgrade => v1.1.0
go: github.com/kr/pretty upgrade => v0.2.0
go: github.com/kr/text upgrade => v0.2.0
go: downloading github.com/kr/text v0.2.0

I recently made this repository public and added go.mod (not sure if before or after).

@matthewmueller Which repository did you make public? github.com/matthewmueller/diff? The public status of the main repository (git@github.com:matthewmueller/duojs.git shouldn't matter here.

Are you able to reproduce this? If so, can you post the config file for the repository with the error? It would have been /Users/m/Go/pkg/mod/cache/vcs/5f9f95779422363e8e24e203ef2f34dbab3a4cb052f98aa116323dc518593f13/config.

Could you post any relevant parts of ~/.gitconfig? I'd be particularly interested in any url and insteadOf lines.

Which repository did you make public? github.com/matthewmueller/diff?

Yep!

Are you able to reproduce this? If so, can you post the config file for the repository with the error? It would have been /Users/m/Go/pkg/mod/cache/vcs/5f9f95779422363e8e24e203ef2f34dbab3a4cb052f98aa116323dc518593f13/config.

Sorry, I deleted this cache. I'll be sure to save it if I run into this again.

Could you post any relevant parts of ~/.gitconfig? I'd be particularly interested in any url and insteadOf lines.

[url "git@github.com:"]
	insteadOf = https://github.com/

This has been here for awhile though.

One thing I did recently is add GOPRIVATE to my rc file so I can pull from private repositories

export GOPRIVATE=github.com/matthewmueller

@matthewmueller Your ~/.gitconfig file explains the remote SSH URLs. And it seems like those URLs should still be valid. I can't think of a reason why anything here would cause problems.

If you (or anyone else) run into this problem in the future, it would be helpful if you could post:

• Git version.
• Any changes to repository privacy, remote URLs, authentication that might cause this.
• Repository config file.
• Ideally, a .zip of the repository inside the module cache (maybe a lot to ask I know; it would help us rule out file corruption).

@balopat @matthewmueller you are a life-saver! I have been looking for the solution for almost a day, and this is exactly what fix mine. Thank you for sharing!

I wish I had read to the bottom of this issue about saving the cache folder for troubleshooting. I turfed my cache after running into this error:

	github.com/dlclark/regexp2: module github.com/dlclark/regexp2: git ls-remote -q origin in /Users/jesseredl/go/pkg/mod/cache/vcs/41f57ef0dad41000850e307b84f39892ac7069a4e73d6b9c629532f5cbf182af: exit status 128:
	fatal: 'origin' does not appear to be a git repository
	fatal: Could not read from remote repository.

	Please make sure you have the correct access rights
	and the repository exists.

We faced this issue recently and for us it was introduced due to the recent git vulnerability update i.e, the pkg mod cache was owned by some other user and go process was being run by another user. Since git prevents you from running git commands inside dirs not owned by you after the recent update (fatal: unsafe repository (‘/dir/path’ is owned by someone else), go was unable to run git ls-remote -q origin and hence the failure.

We also initially thought that the cache got corrupted somehow but that wasn't the case for us. So, for others who face this issue in the future, please try this first before deleting the cache to find the RC:

# cd to the cache dir reported in the error msg, eg.
cd $GOPATH/pkg/mod/cache/vcs/a3...70
git remote -v # should show origin as a remote
# for us all git commands were failing but if the above command works for you then try the actual command being run by go. i.e,
git ls-remote -q origin # refer to your error msg to get the exact command, for us it was this.

Question for maintainers - I'm just curious why the actual git error msg wasn't shown by go and fatal: 'origin' does not appear to be a git repository was shown instead 🤔 . It would've been easier to debug with the actual error msg. By original error msg I mean:

fatal: unsafe repository ('/go/pkg/mod/cache/vcs/a3...70' is owned by someone else)
To add an exception for this directory, call:
	git config --global --add safe.directory /go/pkg/mod/cache/vcs/a3...70