| 18 Sep 2025 |
 connor (he/him) | Which brings me to another great irritation — should older versions of software refer specifically to older versions of the license? Do we need to do something to preserve them or vendor them in tree? If the license contains clauses allowing it to be updated without notice, is that enforceable everywhere? | 16:17:41 |
| connor (he/him) | * Which brings me to another great irritation — should older versions of software refer specifically to older versions of the license? Do we need to do something to preserve them or vendor them in tree? If the license contains clauses allowing it to be updated without notice, is that enforceable everywhere?
Ignore that; licenses are complicated and I can’t give myself a migraine this early.
| 16:18:22 |
 SomeoneSerge (back on matrix) | Posted a response to the allowUnfree part | 20:11:27 |
| 20 Sep 2025 |
| connor (he/him) | Posted a reply back | 21:45:34 |
| 21 Sep 2025 |
 tomberek | Hey, through the GitHub Open Source security program we can get a significant amount of Azure credits. Would the CUDA team be able to effectively use that? Would that make a difference in the maintenance burden? | 14:10:32 |
| SomeoneSerge (back on matrix) | I'm afraid that expert-hours are 146% the scarcest resource right now (as always?) | 15:48:56 |
| SomeoneSerge (back on matrix) | connor (he/him) (UTC-7): repeatedly mentioned he's been experimenting with building nixos images for Azure | 15:49:27 |
| SomeoneSerge (back on matrix) | If we could have ephemeral azure instances with a mutable nix store that would be amazing | 15:50:19 |
| 22 Sep 2025 |
| SomeoneSerge (back on matrix) | Judging by Gaétan Lepage's emoji reaction, he's already imagining them nixpkgs-reviews going brrrrrrrr. Gaétan Lepage would you have the availability for this one? | 08:01:20 |
 Gaétan Lepage | To work on the Azure stuff? | 09:16:35 |
| Gaétan Lepage | I have gained access to a beefy builder since then, so I'm less constrained than before on the x86_64-linux side of things. | 09:17:08 |
 matthewcroughan | SomeoneSerge (back on matrix): can you bump or have you bumped privately https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/development/python-modules/opensfm/default.nix#L144 ? | 20:19:03 |
| matthewcroughan | I need it for https://github.com/NixOS/nixpkgs/pull/442003 | 20:19:15 |
| matthewcroughan | because none of the SfM tools work properly in nixpkgs anymore | 20:19:27 |
| matthewcroughan | SfM tools are tools that take a dir of image and tag it with inferred data like rotation, coordinates etc, to pipe into gaussian splat utils like brush | 20:19:52 |
| matthewcroughan | https://github.com/NixOS/nixpkgs/pull/438672 | 20:43:43 |
| matthewcroughan | hmm, this gets close to fixing colmap | 20:43:50 |
| 23 Sep 2025 |
| SomeoneSerge (back on matrix) | matthewcroughan: hard pressed right now, maybe end of week... | 00:30:01 |
 hexa | did anyone here make substitions from the flox cache work yet? | 01:51:21 |
| Gaétan Lepage | I had some cache hits is this is your question | 08:23:23 |
| Gaétan Lepage | FYI Zowoq has restored the cuda jobset on nix-community:
https://matrix.to/#/%21PbtOpdWBSRFbEZRLIf%3Anumtide.com/%240hueN5_QPZEhj5g4nqSa-gFgmCYe3CMKlG79bd2E-nM?via=blad.is&via=matrix.org&via=envs.net | 08:24:47 |
 Hugo | @ss:someonex.net Thanks for your feedback on my PR adding Cuda tests.
I implemented most, but cannot test because I cannot rebuild xformers with CUDA enabled 🫤. I tried many times on multiple machines but no luck. It builds fine without Cuda though.
| 10:19:57 |
| Hugo | Redacted or Malformed Event | 10:20:52 |
| Hugo | 
Download Screenshot_20250923_122127.png | 10:22:03 |
| Hugo | 
Download Screenshot_20250923_122117.png | 10:22:24 |
| Hugo | I also find it really weird that CPU stays at 100% while the build is stuck. | 10:22:25 |
| Hugo | Is that a known bug in Nix or in the build tools? | 10:22:55 |
|  kenji changed their display name from a-kenji to kenji. | 10:42:31 |
 Albert Larsan | nvcc spawns multiple compiler instances per invocation, and ninja spawns as many nvcc instances as the number of cores/threads, which makes the CPU overcommited (ex: you have 16 threads, ninja spawn 16 nvcc instances, and each one of the nvcc intances spawns 6 cicc instances, and each cicc instance consumes one full cpu thread. So you end up with 16*6=96 processes trying to run at the same time). The build is not stuck, it just takes a very long time to happen (because it tries to do more at the same time than your computer can handle) | 11:32:01 |
| Hugo | Tanks for this explanation. My impression is more that the system goes OOM and then something gets stuck and never resumes. | 11:44:59 |
