2 ms·
Nixpkgs' so-called binary cache actually also caches source tarballs. Any Nix users out there who ran updates during the change? Did cache hits save you? Did c
by pxc 4y ago
Nixpkgs' so-called binary cache actually also caches source tarballs. Any Nix users out there who ran updates during the change?
Did cache hits save you? Did cache misses break your builds?
- jkachmar 4y agodidn’t realize this had happened until i logged off of my work computer & saw someone had shared this thread in a group chat. looks like we were completely unaffected, as no one made any updates to derivations referencing GitHub sources in a way that invalidated old entries (i.e. no version bumps, new additions, etc.).
- anderskaseorg 4y agoNixpkgs’s fetchFromGitHub function hashes the contents of GitHub archives after unpacking, so it’s unaffected.
- pxc 4y agoI should have remembered this! Nixpkgs committers are consistently mindful of things like this in code reviews.
- clhodapp 4y agoI could be wrong but believe that nix should be safe for the most part because it does a recursive hash of the stuff it cares about on the extraction of these archives.