NixOS CUDA | 325 Members | |
| CUDA packages maintenance and support in nixpkgs | https://github.com/orgs/NixOS/projects/27/ | https://nixos.org/manual/nixpkgs/unstable/#cuda | 64 Servers |
| Sender | Message | Time |
|---|---|---|
| 27 Apr 2026 | ||
| It’s not our commit message. We’re just syncing branch from NixOS/nixpkgs to nixos-cuda/nixpkgs using API. | 05:54:42 | |
| Oh, forgot this | 05:56:00 | |
| https://docs.github.com/en/rest/branches/branches?apiVersion=2026-03-10#sync-a-fork-branch-with-the-upstream-repository - this one to be precise | 05:57:01 | |
| I have no idea why GitHub decides to add an event to every issue because of this. | 05:58:04 | |
| Maybe the previous event from the master was stuck in split brain or smth. | 05:59:15 | |
| if it appears on a handful of PRs per day probably not | 09:15:27 | |
| Does it trigger something in our infra? | 09:16:24 | |
| I saw it on two consecutive PRs | 09:16:41 | |
| and didn't look further | 09:16:47 | |
| 14:31:41 | ||
| I’ve been having some fun recently with libcupti infinitely recursing during builds trying to find libcuda (ignoring the stub). This seems to be a new issue only in CUDA 13 plus. It doesn’t try and open libcuda in 12. Curious if anyone has run into this before? | 19:01:29 | |
| 21:20:15 | ||
Download | 21:20:33 | |
| pretty sure the name is confusing people | 21:20:50 | |
| hydra-channel-foo makes it sound official | 21:20:56 | |
| yeah | 21:21:03 | |
| 21:48:43 | ||
| True, we can rename this. cc yorik.sar | 22:20:11 | |
| I have not run into this. If you find out why, I can surely make a PR. | 22:20:30 | |
| 23:00:47 | ||
| Ah it’s no stress and easy to get around, just wanted to make sure I wasn’t wasting work if someone had already solved it | 23:10:13 | |
| 30 Apr 2026 | ||
FYI: cudaPackages_13 now points cudaPackages_13_2 (which is at 13.2.0). | 15:14:44 | |
* FYI: cudaPackages_13 now points to cudaPackages_13_2 (which is at 13.2.0). | 15:15:10 | |
| 17:30:10 | ||
| Gaétan Lepage is cache.nixos-cuda.org being hammered or why is it so slow to respond? | 23:47:40 | |
| and any reason there's no ipv6 support? | 23:54:15 | |
| 1 May 2026 | ||
| I am not aware. It seems okay right now, but maybe it was under heavy load. SomeoneSerge (matrix works sometimes) recently added the Anubis firewall to the web portal. Also, it's the same machine hosting the actual hydra instance (including evaluator and queue runner) and evals are sometimes giving it a hard time. | 21:07:45 | |
I didn't initially set up ipv6, but now it is available (2a01:4f9:3071:1108::1). Do you mean that the hydra instance is not correctly configured w.r.t. ipv6? | 21:11:13 | |
| dns.nix has ipv6 but that has not been propagated into dns | 22:08:46 | |
| 22:29:02 | |