| 2 May 2026 |
Devin | nix should not be using the cuda cache as a substituter but it's still trying to download something from it... | 22:06:49 |
Devin | though this is possibly just some weirdness with some other flake input I have
also lmk if i should make this a thread i don't use matrix often | 22:07:27 |
Melody | Also noticed nix isnt just auto falling back to another substituter. Removing it helped at least.
Devin do you have nixConfig.extra-substituters defined in flake.nix by chance?
| 22:09:41 |
Devin | i do not | 22:09:58 |
Devin | hm... manually overriding the substituters option at the command-line seems to have gotten me past this, so ig the change to nix.conf just... didn't go through? | 22:10:07 |
Devin | and now it's just. fine even without that? how bizarre | 22:12:00 |
Devin | anyway good luck figuring ts out :3 | 22:12:49 |
Devin | * anyway good luck figuring ts out you guys:3 | 22:12:54 |
Devin | * anyway good luck figuring ts out you guys :3 | 22:12:55 |
Gaétan Lepage | Yup, restarted it. I might do a few cycles, so there can be more down time tonight.
Sorry for the disruption | 22:13:52 |
Devin | no worries! this stuff isn't easy | 22:14:06 |
Gaétan Lepage | hexa (UTC+1) it looks like harmonia doesn't like the socket path:
May 03 00:11:25 hydra harmonia[5383]: [2026-05-02T22:11:25Z INFO harmonia] listening on /run/harmonia/socket
May 03 00:11:25 hydra harmonia[5383]: Error: Custom { kind: Other, error: invalid socket address }
Am I missing something? | 22:15:29 |
hexa | Can check in 15m | 22:16:08 |
| smudge joined the room. | 22:17:03 |
Gaétan Lepage | Reverted so the cache is now working again. | 22:18:13 |
hexa | https://github.com/nixos-cuda/infra/pull/101 | 22:30:00 |
Gaétan Lepage | Merged, thanks! | 22:43:36 |
| 4 Aug 2022 |
| Winter (she/her) joined the room. | 03:26:42 |
Winter (she/her) | (hi, just came here to read + respond to this.) | 03:28:52 |
tpw_rules | hey. i had previously sympathzied with samuela and like i said before had some of the same frustrations. i just edited my github comment to add "[CUDA] packages are universally complicated, fragile to package, and critical to daily operations. Nix being able to manage them is unbelievably helpful to those of us who work with them regularly, even if support is downgraded to only having an expectation of function on stable branches." | 03:29:14 |
Winter (she/her) | In reply to @tpw_rules:matrix.org i'm mildly peeved about a recent merging of something i maintain where i'm pretty sure the merger does not own the expensive hardware required to properly test the package. i don't think it broke anything but i was given precisely 45 minutes to see the notification before somebody merged it ugh, 45 minutes? that's... not great. not to air dirty laundry but did you do what samuela did in the wandb PR and at least say that that wasn't a great thing to do? (not sure how else to word that, you get what i mean) | 03:30:23 |
tpw_rules | no, i haven't yet, but i probably will | 03:31:03 |
Winter (she/her) | i admittedly did that with a PR once, i forget how long the maintainer was requested for but i merged it because multiple people reported it fixed the issue. the maintainer said "hey, don't do that" after and now i do think twice before merging. so it could help, is what i'm saying. | 03:31:50 |
tpw_rules | i'm not sure what went wrong with the wandb PR anyway, i think it was just a boneheaded move on the maintainer's part | 03:32:10 |
Winter (she/her) | (it was also simple enough that it was fine and the maintainer said it looked good after) | 03:32:15 |
tpw_rules | * i'm not sure what went wrong with the wandb PR anyway, i think it was just a boneheaded move on the merger's part | 03:32:19 |
tpw_rules | but i thought most of the frustration was around packages which don't really involve CUDA breaking the fragile CUDA packages, and i'm not sure how the warning helps in this case. it's not like nixpkgs-review prints out the comments. maybe i'm wrong. but it is a legitimate problem | 03:34:19 |
Winter (she/her) | the frustration that i see is that people are touching packages that he maintains, am i missing further context here? | 03:35:09 |
tpw_rules | did you ever see this? https://discourse.nixos.org/t/nixpkgss-current-development-workflow-is-not-sustainable/18741 | 03:35:43 |
Winter (she/her) | oh yes i did | 03:35:49 |