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
Inconsistent go1.13 pkg/mod/cache/download folder. #34866
Comments
These are partial tiles as described in https://research.swtch.com/tlog#serving_tiles. They will appear for any part of the tree that isn't completely filled out yet. That's up to half of the tree at any given time, if I remember the design correctly. The packages that are causing problems are probably just in a newer part of the tree than the rest. I am extremely surprised that disabling the sumdb doesn't change anything. Are you absolutely sure it still downloads those files with |
Sorry screwed up my negative, GOSUMDB=off fixes this, but in general we would like to use the sum proxy since it provides some nice content security. |
I guess since the proof tree is always changing, we should just zero out the pkg/mod/cache/download/sumdb folder when generating the build inputs. |
That's what I'd do. Closing, since this is all working as intended. |
that still happens when install process breaks for some reason (sudden reboot for example) and that manual fix works. But shouldn't go installer detect that and fix that all by itself? Or at least with a prompt |
What version of Go are you using (
go version
)?go version
go version go1.13.1 linux/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
What did you do?
What did you expect to see?
No difference in diff
What did you see instead?
With go1.12, the diff shows no difference, with go1.13 it shows
This behavior is used by the nix build system to download and store dependencies for go programs. We are seeing inconsistent hashes with go 1.13 due to differences in the module cache related to the go sum server, which is breaking the build system for certain packages.
This appears to effect the following packages and versions.
github.com/wata727/tflint@v0.12.1
github.com/instrumenta/conftest@v0.14.0
github.com/syncthing/syncthing@1.3.0
We have some discussion in NixOS/nixpkgs#71049 and NixOS/nixpkgs#68135
DIsabling the sumdb fixes this. It looks like we're getting a new proof(?) every time for some packages(?).
The text was updated successfully, but these errors were encountered: