Unrelated, but I'm getting errors with the nix-required-mounts hook, maybe I'm just on a bad commit:

$ /nix/store/kgcbq3ablba98myqn8j4sq7yla6nzs3m-nix-required-mounts-0.0.1/bin/nix-required-mounts /nix/store/5i5w8byychlxjbrjnvfl4rwbi9wqr66d-nix-shell-env.drv
Traceback (most recent call last):
  File "/nix/store/kgcbq3ablba98myqn8j4sq7yla6nzs3m-nix-required-mounts-0.0.1/bin/.nix-required-mounts-wrapped", line 9, in <module>
    sys.exit(entrypoint())
             ~~~~~~~~~~^^
  File "/nix/store/kgcbq3ablba98myqn8j4sq7yla6nzs3m-nix-required-mounts-0.0.1/lib/python3.13/site-packages/nix_required_mounts.py", line 142, in entrypoint
    [canon_drv_path] = parsed_drv.keys()
    ^^^^^^^^^^^^^^^^
ValueError: too many values to unpack (expected 1)

Using commit https://github.com/NixOS/nixpkgs/commits/8110df5ad7abf5d4c0f6fb0f8f978390e77f9685 of Nixpkgs. I remember something about JSON derivation format change but I can't remember for the life of me if we already fixed that. Previous commit was https://github.com/NixOS/nixpkgs/commits/a6531044f6d0bef691ea18d4d4ce44d0daa6e816.

Interesting, I'm facing another error:

error:
       … while setting up the build environment

       error: getting attributes of path '/nix/store/02wkfkv635277dyq176lw5dcqpxlpsl0-kmod-31/sbin/bin': No such file or directory

In reply to @connorbaker:matrix.org
Also, can someone explain https://developer.download.nvidia.com/compute/cuda/redist/cuda_compat_orin/ to me? If I had to hazard a guess, it would be that it would allow using CUDA 13.1/13.2 on a Jetson based on JetPack 7 (since support for Orin is added in JetPack 7.2, but that hasn't been released yet as far as I can tell, though it is talked about in the CUDA 13.2 blog post: https://developer.nvidia.com/blog/cuda-13-2-introduces-enhanced-cuda-tile-support-and-new-python-features/#embedded_devices). Is that correct? Or does it allow forward compat across major versions and can be used with JetPack 6, similar to how cuda_compat for Orins on JetPack 5 allows support for up to CUDA 12.2 despite shipping with CUDA 11.4.

In reply to @connorbaker:matrix.org
Also, can someone explain https://developer.download.nvidia.com/compute/cuda/redist/cuda_compat_orin/ to me? If I had to hazard a guess, it would be that it would allow using CUDA 13.1/13.2 on a Jetson based on JetPack 7 (since support for Orin is added in JetPack 7.2, but that hasn't been released yet as far as I can tell, though it is talked about in the CUDA 13.2 blog post: https://developer.nvidia.com/blog/cuda-13-2-introduces-enhanced-cuda-tile-support-and-new-python-features/#embedded_devices). Is that correct? Or does it allow forward compat across major versions and can be used with JetPack 6, similar to how cuda_compat for Orins on JetPack 5 allows support for up to CUDA 12.2 despite shipping with CUDA 11.4.

Neat project!
https://www.youtube.com/watch?v=AvK_gi_snJE

Some quotes from the conclusions:

"Nixpkgs CUDA aarch64 ecosystem is quite healthy"
Thanks to nix-community's 80 core ampere system

"Flakes make a good user interface"
This one is for you SomeoneSerge (matrix works sometimes)

"Lack of cached aarch64 CUDA builds"
👀💸

"Uneven freshness of packages"
Until we unlock core and maintainer cloning, that's going to be tough to change (especially reagrding how fast the whole space is moving).

"Community lacks GPU hardware"
Yes. And CPU too 😅

Neat project!
https://www.youtube.com/watch?v=AvK_gi_snJE

Some quotes from the conclusion:

"Nixpkgs CUDA aarch64 ecosystem is quite healthy"
Thanks to nix-community's 80 core ampere system

"Flakes make a good user interface"
This one is for you SomeoneSerge (matrix works sometimes)

"Lack of cached aarch64 CUDA builds"
👀💸

"Uneven freshness of packages"
Until we unlock core and maintainer cloning, that's going to be tough to change (especially reagrding how fast the whole space is moving).

"Community lacks GPU hardware"
Yes. And CPU too 😅

Neat project!
https://www.youtube.com/watch?v=AvK_gi_snJE

Some quotes from the conclusion:

"Nixpkgs CUDA aarch64 ecosystem is quite healthy"

Thanks to nix-community's 80 core ampere system

"Flakes make a good user interface"
This one is for you SomeoneSerge (matrix works sometimes)

"Lack of cached aarch64 CUDA builds"
👀💸

"Uneven freshness of packages"
Until we unlock core and maintainer cloning, that's going to be tough to change (especially reagrding how fast the whole space is moving).

"Community lacks GPU hardware"
Yes. And CPU too 😅

Neat project!
https://www.youtube.com/watch?v=AvK_gi_snJE

Some quotes from the conclusion:

"Nixpkgs CUDA aarch64 ecosystem is quite healthy"

Thanks to nix-community's 80 core ampere system

"Flakes make a good user interface"

This one is for you SomeoneSerge (matrix works sometimes)

"Lack of cached aarch64 CUDA builds"

👀💸

"Uneven freshness of packages"

Until we unlock core and maintainer cloning, that's going to be tough to change (especially reagrding how fast the whole space is moving).

"Community lacks GPU hardware"

Yes. And CPU too 😅

Neat project!
https://www.youtube.com/watch?v=AvK_gi_snJE

Some quotes from the conclusion:

"Nixpkgs CUDA aarch64 ecosystem is quite healthy"

Thanks to nix-community's 80 core ampere system

"Flakes make a good user interface"

This one is for you SomeoneSerge (matrix works sometimes)

"Lack of cached aarch64 CUDA builds"

👀💸

"Uneven freshness of packages"

Until we unlock core and maintainer cloning, that's going to be tough to change (especially reagrding how fast the whole space is moving).

"Community lacks GPU hardware"

Yes. And CPU too 😅

Neat project!
https://www.youtube.com/watch?v=AvK_gi_snJE

Some quotes from the conclusion:

• "Nixpkgs CUDA aarch64 ecosystem is quite healthy"
  Thanks to nix-community's 80 core ampere system

• "Flakes make a good user interface"
  This one is for you SomeoneSerge (matrix works sometimes)

• "Lack of cached aarch64 CUDA builds"
  👀💸

• "Uneven freshness of packages"
  Until we unlock core and maintainer cloning, that's going to be tough to change (especially reagrding how fast the whole space is moving).

• "Community lacks GPU hardware"
  Yes. And CPU too 😅

Neat project!
https://www.youtube.com/watch?v=AvK_gi_snJE
I find it really cool that someone wrote a convenient flake to make the DGX spark work OOTB.

Some quotes from the conclusion:

• "Nixpkgs CUDA aarch64 ecosystem is quite healthy"
  Thanks to nix-community's 80 core ampere system
• "Flakes make a good user interface"
  This one is for you SomeoneSerge (matrix works sometimes)
• "Lack of cached aarch64 CUDA builds"
  👀💸
• "Uneven freshness of packages"
  Until we unlock core and maintainer cloning, that's going to be tough to change (especially reagrding how fast the whole space is moving).
• "Community lacks GPU hardware"
  Yes. And CPU too 😅

🆕 transformer-engine added!

https://github.com/NixOS/nixpkgs/pull/473703

That was not a trivial one!

🆕 transformer-engine added!

https://github.com/NixOS/nixpkgs/pull/473703

That was not a trivial one!

🆕 transformer-engine added!

https://github.com/NixOS/nixpkgs/pull/473703

That was not a trivial one! Thanks to connor (burnt/out) (UTC-8) and @NickCao for the review.

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