| 14 Dec 2025 |
Emma [it/its] | let me try to reproduce on spare hardware | 18:53:19 |
Emma [it/its] |  Download clipboard.png | 18:53:25 |
Jan Kvapil | Hmm. Is this such a convoluted thing, because I am using flake-utils and it runs fetch-deps for evey system? | 18:53:43 |
Jan Kvapil | I am running NixOS/Linux, no osx. | 18:53:52 |
Jan Kvapil | Running this directly within nix-shell finishes quickly. | 18:55:24 |
Corngood | It will run a restore for each platform in meta.platforms, or default to the ones supported by the sdk | 18:55:50 |
Jan Kvapil | I don't define any meta and there is dotnet-runtime set, so should run only once? https://github.com/quapka/bitcoinfuzz/blob/build-with-nix/modules/nbitcoin/default.nix#L20 | 18:57:44 |
Corngood | No, it'll still default to the 4 available platforms from the sdk meta.platforms | 18:58:34 |
Jan Kvapil | Ok, I'll set:
meta = {
platforms = lib.platforms.linux;
};
And try again.
| 19:00:36 |
Corngood | That'll still be two platforms. You can limit it to one arch if you want | 19:01:23 |
Corngood | "x86_64-linux" probably | 19:01:39 |
Jan Kvapil | Thanks! | 19:02:09 |
Jan Kvapil | meta = {
platforms = lib.intersectLists lib.platforms.x86_64 lib.platforms.linux;
};
RAM steadily rising...
| 19:06:39 |
Jan Kvapil | I'd be happy to enter the process and do it step by step, but am not that proficient in how to actually do it here with fetch-deps. A nix-shell -p nuget-to-json -p dotnetCorePackages.sdk_10_0-bin -p dotnetCorePackages.runtime_10_0-bin is clearly different to what that things runs in. This shell finishes fine. | 19:08:09 |
Jan Kvapil | Looks like a stress test to the SSDs also 67 degrees and rising. | 19:09:23 |
Emma [it/its] | oh right, i got side tracked, i was going to try this | 19:24:19 |
Corngood | How exactly are you running fetch-deps in that repo? I can try it out here. | 19:26:01 |
Jan Kvapil | I do nix build .#modules.nbitcoin.fetch-deps and then ./result. | 19:26:36 |
Emma [it/its] | yeah im not seeing nbitcoin exposed in the flake as a package and im not sure how to deal with a default.nix | 19:26:41 |
Emma [it/its] | oh its in modules | 19:26:51 |
Emma [it/its] | that's an odd place lol | 19:26:59 |
Emma [it/its] | not using passthru? | 19:27:53 |
Jan Kvapil | Yes, some of the modules are name-conflicting with nixpkgs, it's WIP anyways. | 19:28:36 |
Emma [it/its] |  Download clipboard.png | 19:28:44 |
Jan Kvapil | I guess I just don't know how. | 19:29:02 |
Emma [it/its] | can confirm im seeing unusually high memory usage, but also a lot of disk io during that time | 19:29:04 |
Jan Kvapil | Yes. | 19:29:17 |
Emma [it/its] | 4.5G now, odd | 19:29:30 |
Jan Kvapil | Depending on the $pwd, I guess something like this:
nix-build -E '((import <nixpkgs> {}).callPackage ./modules/nbitcoin/default.nix {}).fetch-deps
| 19:29:47 |
Jan Kvapil | * Depending on the $pwd, I guess something like this:
nix-build -E '((import <nixpkgs> {}).callPackage ./modules/nbitcoin/default.nix {}).fetch-deps
| 19:29:50 |