| 22 Sep 2025 |
 hexa | odd, anything you did? | 23:30:16 |
| 23 Sep 2025 |
| hexa | and the cuda jobsets are gone as well? A change to terraform seems to be missing. | 01:03:15 |
| hexa | * and the cuda jobsets are gone as well? A change to infra repo seems to be missing. | 01:03:51 |
| hexa | * and the cuda jobsets are gone as well? A change to the infra repo seems to be missing. | 01:03:55 |
| hexa | ok, read up on the open prs | 01:22:05 |
| hexa | so what I can say is: nix-community cache worked great for me all the time | 01:22:19 |
| hexa | cache.flox.dev does not substitute torch or onnxruntime with cudaSupport on nixos-25.05 or nixos-unstable 🤷 | 01:22:41 |
| hexa | also not stuff from cudaPackages | 01:39:46 |
| hexa | le sigh | 01:39:53 |
| hexa | also we have no introspection what they are building | 01:40:00 |
| hexa | * also we have no introspection what they are building into | 01:40:03 |
| hexa | or how often and what the build results are | 01:40:20 |
| hexa |
The Flox binary cache is built from selected revisions from the Nixpkgs nixos-unstable branch, so you will increase the chances of a "cache hit" by similarly using that branch, or you can maximize your chances by pinning your system to one of the exact github:flox/nixpkgs/{unstable,staging,stable,lts} branches that we build from.
| 01:44:44 |
| hexa | so no nixos-25.05 | 01:45:01 |
| hexa | that's a rather profound regression for stable users | 01:45:29 |
| hexa | zowoq: petition to keep the cuda-stable jobset around until 25.05 eol | 01:46:55 |
| hexa | so they seem to be building cuda for all the branches they track, but stable is currently a month old 25.05 commit | 02:40:22 |
|  sinan changed their profile picture. | 02:47:54 |
 zowoq | that's fair, I've restored the jobset. | 02:59:15 |
|  apyh joined the room. | 09:03:12 |
|  Chris P Bacon joined the room. | 09:46:48 |
|  kenji changed their display name from a-kenji to kenji. | 10:39:36 |
| hexa | thanks! | 13:31:50 |
|  pinkybrain joined the room. | 23:13:05 |
| 24 Sep 2025 |
|  waltmck joined the room. | 18:41:00 |
| waltmck | Hey everyone! nixos-apple-silicon is looking to move to a full kernel, which would simplify things and solve many open bugs but brings the build time from about 20 minutes to 2 hours on my MacBook Air. nixpkgs does not allow vendor kernels, so we are looking for an alternative cache.
Unfortunately, it looks like the nix-communitybuilder builds arbitrary untrusted derivations from PRs, which most of the nixos-apple-silicon maintainers find unacceptable in light of the recent Nix CVE's. How are other projects handling this? Are you just using the nix-community cache or self-hosting your own builders, or something else?
| 18:54:29 |
| waltmck | * Hey everyone! nixos-apple-silicon is looking to move to a full kernel, which would simplify things and solve many open bugs but brings the build time from about 20 minutes to 2 hours on my MacBook Air. nixpkgs does not allow vendor kernels, so we are looking for an alternative cache.
Unfortunately, it looks like the nix-community builder builds arbitrary untrusted derivations from PRs, which most of the nixos-apple-silicon maintainers find unacceptable in light of the recent Nix CVE's. How are other projects handling this? Are you just using the nix-community cache or self-hosting your own builders, or something else?
| 18:54:53 |
 Jonas Chevalier | The best I can think of is to use the namespace.so GitHub Action builders they are gracefully providing to nix-community, and then push to your own Cachix cache. Hopefully it takes less than 2h to build on their hardware but worth trying out to find out. | 21:12:43 |
| Jonas Chevalier | Otherwise, help us secure and bring the Nix builders up to a level that makes you happy, that would be pretty awesome too. | 21:13:44 |
| 25 Sep 2025 |
|  nyanbinary 🏳️⚧️ removed their profile picture. | 16:30:49 |
