In 5bdbaf39, the dream2nix input got updated to a version that includes all-cabal-json as an input. The tarball for that input is ~192 MB, and when extracted, it produces so many files that it takes some of my less powerful systems upwards of 20 minutes just to chech the NAR hash.
As far as I can tell, we don't actually make use of any dream2nix functions that use this input. I also noticed that other unused inputs had been overriden to point to nixpkgs, which I assume was done to avoid downloading them too.
This pull request updates the follows values for the unused inputs so that they're all set to "", meaning nothing will be downloaded for them.
It might also be a good idea to modify the flake update workflow so that it checks whether any new inputs have been added, to avoid this sort of thing happening again in the future.
yusdacra
commented
1 year ago
In 5bdbaf39, the
dream2nixinput got updated to a version that includes all-cabal-json as an input. The tarball for that input is ~192 MB, and when extracted, it produces so many files that it takes some of my less powerful systems upwards of 20 minutes just to chech the NAR hash.As far as I can tell, we don't actually make use of any
dream2nixfunctions that use this input. I also noticed that other unused inputs had been overriden to point to nixpkgs, which I assume was done to avoid downloading them too.This pull request updates the
followsvalues for the unused inputs so that they're all set to"", meaning nothing will be downloaded for them.It might also be a good idea to modify the flake update workflow so that it checks whether any new inputs have been added, to avoid this sort of thing happening again in the future.