| 30 Oct 2025 |
 Gaétan Lepage | After: | 22:11:19 |
| Gaétan Lepage | 
Download clipboard.png | 22:11:21 |
| Gaétan Lepage | Probably nccl's fault... | 22:18:18 |
| 31 Oct 2025 |
|  connor (burnt/out) (UTC-8) changed their profile picture. | 03:16:13 |
| connor (burnt/out) (UTC-8) changed their display name from connor (he/him) (UTC-7) to connor (burnt/out) (UTC-7). | 03:16:45 |
| connor (burnt/out) (UTC-8) | gonna slow down and take a step back for a bit | 03:18:20 |
 Daniel Fahey | You said upfront "The addition of CUDA 13 does not mean packages will suddenly work with CUDA 13. Expect breakages." I know I'm just a random bloke from GitHub an fairly new but I've had really bad burnout in the past, I'd suggest still doing a little bit of triaging and technical support here and there for the CUDA Team in strict time blocks, so you can at least see the fruits of your labour (given to the world, for free) as the breakages all get sorted out in the coming weeks in our collective efforts.
From my perspective I'm just excited about the prospect of using CUDA 13 with Nixpkgs, I've basicaly used nixos-unstable, sometimes master, since starting to use Nix, and still have no idea how the release cycle is supposed to work 🙃.
I reckon for the next big CUDA update, do something like how the haskell-updates branch gets merged into staging first.
| 10:26:33 |
| Daniel Fahey | * You said upfront "The addition of CUDA 13 does not mean packages will suddenly work with CUDA 13. Expect breakages." I know I'm just a random bloke from GitHub and fairly new but I've had really bad burnout in the past, I'd suggest still doing a little bit of triaging and technical support here and there for the CUDA Team in strict time blocks, so you can at least see the fruits of your labour (given to the world, for free) as the breakages all get sorted out in the coming weeks in our collective efforts.
From my perspective I'm just excited about the prospect of using CUDA 13 with Nixpkgs, I've basicaly used nixos-unstable, sometimes master, since starting to use Nix, and still have no idea how the release cycle is supposed to work 🙃.
I reckon for the next big CUDA update, do something like how the haskell-updates branch gets merged into staging first.
| 10:26:44 |
| connor (burnt/out) (UTC-8) | I mean I’ll still be around, just not doing as much. I’ll still be in the team weeklies, etc. | 14:35:31 |
| connor (burnt/out) (UTC-8) | CUDA 13 isn’t the default because the stuff we have in tree is too old or doesn’t support it; the expect breakages was in reference to trying to use CUDA 13 as the default. | 14:36:20 |
| connor (burnt/out) (UTC-8) | Haskell stuff goes into staging (at least partly) because of the sheer number of packages, to allow Hydra to churn through them. None of our stuff is built upstream, so there’s not really a point. | 14:37:36 |
