Goddammit. I rewrote the history of two Go modules, now they're failing to go get for some weirdass reason.
4
Replies
0
Boosts
Eh, well. git reflog to the rescue, and I force-push the old stuff.
Now both modules go get fine. After the force push, go get complained that the thing doesn't have a go-import meta header. It does. The HTML returned by the checked URL is unchanged between the two commits.
Go's fucking weird.
@algernon hm...
what if you set these env vars?
export GOPROXY=direct
export GOSUMDB=off
export GOTELEMETRY=off
export GOTOOLCHAIN=local
i think only the first 2 is important to what i'm trying to see what happens. the first one disables the go module proxy mirror (and second one is probably similar for checksums or something)
@jacksonchen666 Dunno. I reverted back to pre-history-rewrite, and everything works now as it did before. I don't plan to touch the modules anytime soon (they're caddy plugins, and I'll switch away from Caddy sooner than having to update the plugins :P), so problem solved, and I'm happier if I don't know more. 
