NixOS CUDA | 289 Members | |
| CUDA packages maintenance and support in nixpkgs | https://github.com/orgs/NixOS/projects/27/ | https://nixos.org/manual/nixpkgs/unstable/#cuda | 57 Servers |
| Sender | Message | Time |
|---|---|---|
| 23 Sep 2024 | ||
| Kevin Mittman: does NVIDIA happen to have JSON (or otherwise structured) versions of their dependency constraints for packages somewhere, or are the tables on the docs for each respective package the only source? I'm working on update scripts and I'd like to avoid the manual stage of "go look on the website, find the table (it may have moved), and encode the contents as a Nix expression" | 18:39:25 | |
| 24 Sep 2024 | ||
| 08:56:22 | ||
| 11:40:36 | |
| I think this one has been failing for me on the linear-operator package | 11:41:02 | |
As a sanity check — has anyone been able to successfully use torch.compile to speed up model training, or do they also get a python stack trace when torch tries to call into OpenAI’s triton | 15:23:08 | |
| 25 Sep 2024 | ||
| It used to work but now our t2iton is lagging 1 major version behind | 19:36:58 | |
| Because those geniuses are not able to tag a freaking release | 20:20:55 | |
| https://github.com/triton-lang/triton/issues/3535 | 20:21:18 | |
| unstable-yyyy-mm-dd is ok for us; there were some minor but unresolved issues with the PR that does the bump though | 20:23:04 | |
| 26 Sep 2024 | ||
In reply to @glepage:matrix.orgWell that’s an infuriating read | 16:33:18 | |
| It's OK, OpenAI is just a small startup with only a few people. And deep learning is not even their main activity | 17:07:38 | |
| Yeah and they're | 17:20:14 | |
| "open" is in their name | 17:24:26 | |
| it's such a joke that I find it sad it was not opened one day earlier | 17:28:20 | |
"I propose a 200€ bounty for this PR. Please git tag the freaking commit. | 21:09:04 | |
* "I propose a 200€ bounty for this PR. Please git tag the freaking commit." | 21:09:07 | |
| The ease of spinning up a release is a decreasing function of the project/company resources. | 21:09:40 | |
| same issue on a one-man project abandonned for the last year or so: https://github.com/bab2min/EigenRand/issues/56 | 21:47:05 | |
| * same issue on a one-man project abandonned for the last year or so: https://github.com/bab2min/EigenRand/issues/56 : <48h | 21:49:56 | |
| 28 Sep 2024 | ||
| 07:04:58 | ||
| 16:55:46 | ||
| 1 Oct 2024 | ||
| 21:00:15 | ||
| 2 Oct 2024 | ||
| Gaétan Lepage: please take care of tensordict | 00:25:19 | |
Download image.png | 00:25:22 | |
| Sure, I will have a look right now. I have not faced any failure on my end, weird... | 06:21:33 | |
| Is this on staging ? | 06:23:26 | |
| All failures that I was able to find on hydra are timeouts or upstream dependency failures. I was able to build tensordict on all architectures... | 07:05:50 | |
| this is on trunk | 11:03:39 | |
| then you probably need to increase meta.timeout | 11:04:00 | |
| Now that you say it, I remember this package being stuck (indefinitly) during mass rebuilds. I don't know if increasing the timeout will help. When everything works fine, it builds in ~1min... Also, nothing has changed in the derivation for the past few months. | 11:47:12 | |