3 ms·
The module cache in Go 1.11 can sometimes cause various errors, primarily if there were previously network issues or multiple go commands executing in parallel,
by puddums 8y ago
The module cache in Go 1.11 can sometimes cause various errors, primarily if there were previously network issues or multiple go commands executing in parallel, where the workaround would then be to delete GOPATH/pkg (or run 'go clean -modcache'). I would guess your coworkers were seeing some variation of that.
If so, that is addressed for Go 1.12:
https://github.com/golang/go/issues/26794 https://github.com/golang/go/issues/26794
- canadev 8y agoWe definitely weren't deliberately executing commands in parallel and I think it's pretty rare that we have network issues.
- LukeShu 8y agoI've had 2 coworkers who use different IDEs report that apparently their IDE is running `go` commands in parallel, because they'll get the corrupted module caches.