Skip to content
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

Too many nixpkgs nodes in flake.lock file. #1594

Open
jaredponn opened this issue Feb 7, 2024 · 0 comments
Open

Too many nixpkgs nodes in flake.lock file. #1594

jaredponn opened this issue Feb 7, 2024 · 0 comments

Comments

@jaredponn
Copy link

jaredponn commented Feb 7, 2024

Is there a reason why

db-sync.url = "github:input-output-hk/cardano-db-sync/13.1.0.0";
is not following CTL's haskell-nix? I.e., would it break everything if we had

diff --git a/flake.nix b/flake.nix
index a38d4555d..43e39dcdb 100644
--- a/flake.nix
+++ b/flake.nix
@@ -73,7 +73,10 @@
     };
 
     blockfrost.url = "github:blockfrost/blockfrost-backend-ryo/v1.7.0";
-    db-sync.url = "github:input-output-hk/cardano-db-sync/13.1.0.0";
+    db-sync = {
+        inputs.haskellNix.follows = "haskell-nix";
+        url = "github:input-output-hk/cardano-db-sync/13.1.1.3";
+    };
 
     # Plutip server related inputs
     plutip = {

instead?

Currently, CTL has about 120 nodes for nixpkgs in it's flake.lock file,

$ cat flake.lock | jq '.nodes | keys' | awk -e 'BEGIN { i = 0 } /nixpkgs/ { i++ } END {print i }'
123

but this suggestion reduces it to

$ nix flake lock 
<blah blah blah>
$ cat flake.lock | jq '.nodes | keys' | awk -e 'BEGIN { i = 0 } /nixpkgs/ { i++ } END {print i }'
36

For context, in lambda-buffers doing anything with nix (nix develop, nix build, etc.) takes >10s because the flake.lock is so large, and I'm pretty sure that CTL's db-sync is the last major contributing factor to this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant