Huh, not sure how that's working for you since I can't get it to build:

$ cat ~/.config/nixpkgs/config.nix 
{
  allowAliases = false;
  allowBroken = false;
  allowUnfree = true;
  checkMeta = true;
  cudaCapabilities = [ "7.5" ];
  cudaSupport = true;
}
$ nix run --impure -L --show-trace --builders '' --max-jobs 1 github:nixos/nixpkgs/c7b821ba2e1e635ba5a76d299af62821cbcb09f3#local-ai
...
go-stable-diffusion> CMake Error at /nix/store/q1nssraba326p2kp6627hldd2bhg254c-cmake-3.29.2/share/cmake-3.29/Modules/FindCUDA.cmake:883 (message):
go-stable-diffusion>   Specify CUDA_TOOLKIT_ROOT_DIR
go-stable-diffusion> Call Stack (most recent call first):
go-stable-diffusion>   /nix/store/r008mflixfchlfscby4h0mjgqvz059pw-opencv-4.9.0/lib/cmake/opencv4/OpenCVConfig.cmake:86 (find_package)
go-stable-diffusion>   /nix/store/r008mflixfchlfscby4h0mjgqvz059pw-opencv-4.9.0/lib/cmake/opencv4/OpenCVConfig.cmake:108 (find_host_package)
go-stable-diffusion>   examples/CMakeLists.txt:17 (find_package)

In reply to @trexd:matrix.org
Do you guys have any recommendations on setting up a cache for https://github.com/hasktorch/hasktorch-skeleton/pull/9 ? The haskell part of the build already takes quite a long time but throw CUDA in the mix and I think build times would quickly get out of hand. Either way I've also never setup a cache via cachix or hercules-ci before so I don't know what the limits on build times are either.

In reply to @connorbaker:matrix.org
Depends on how much space you need. Cachix gives 5Gb for free from what I remember. For a single project, that may be enough.
For anything larger than that, you’re in for a world of unpleasantness depending on storage requirements.
Even just hosting a binary cache via S3, you’re going to be paying for each API call (of which Nix will generate many, like an HTTP HEAD request for each NARINFO file, not to mention the actual retrieval of the data) as well as egress, which adds up very quickly.

In reply to @aidalgol:matrix.org
SomeoneSerge (UTC+3): Any thoughts? https://github.com/NixOS/nixpkgs/issues/319167

I suppose we need some kind of a fixpoint 🤷
Btw, I just had a look at the mangohud derivation, and

• we're still doing inherit (linuxPackages.nvidia_x11) libXNVCtrl which I think is a mauvais ton (referencing a concrete version of linuxPackages from nixpkgs)
  • I still think it belongs in the top-level, maybe as an attrset, libXNVCtrlVersions
  • probably a very bad idea, but the nvidia nixos module could add an overlay setting the respective default version of libXNVCtrl
  • all packages taking libXNVCtrl from the top-level, we'd ensure only one version is in use in any given closure (probably at the cost of rebuilding reverse dependencies)
• passing a python package (mako) rather than python3Packages

Honestly, not sure if this is worth the effort 🙃

$ sudo lsof | wc -l
1191414

THat's not much is it

In reply to @gjvnq:matrix.org

Yeah, I had already figured out it but the bug issue is that I don't know what is the "right" way to include the definition of the half type.

To make matters worse, I've tried to compile AliceVision on a docker container and using the official compilation scripts and yet the thing keeps failing. This means I can't even look at how the thing is supposed to compile.

I'm at a bit of a loss as for how to proceed, but I suspect that I'll have to either ask the original authors for help or carefully read the cmake compilation scripts in order to look for potential sources of the error.

Theoretically AliceVision has a nice CI pipeline but I can't see their build history so I don't even know how useful their CI scripts are.

In reply to @ss:someonex.net
Could it be this https://github.com/AcademySoftwareFoundation/Imath/blob/2fc9d89ec52003350fcfd20f337bb3d0b870ff5a/src/Imath/half.h#L180-L182

In reply to @ss:someonex.net

I suppose we need some kind of a fixpoint 🤷
Btw, I just had a look at the mangohud derivation, and

• we're still doing inherit (linuxPackages.nvidia_x11) libXNVCtrl which I think is a mauvais ton (referencing a concrete version of linuxPackages from nixpkgs)
  • I still think it belongs in the top-level, maybe as an attrset, libXNVCtrlVersions
  • probably a very bad idea, but the nvidia nixos module could add an overlay setting the respective default version of libXNVCtrl
  • all packages taking libXNVCtrl from the top-level, we'd ensure only one version is in use in any given closure (probably at the cost of rebuilding reverse dependencies)
• passing a python package (mako) rather than python3Packages

Honestly, not sure if this is worth the effort 🙃

[astraluser@edward:~/Downloads/f/TensorRT-8.6.1.6]$ ls python/tensorrt-8.6.1-cp3
tensorrt-8.6.1-cp310-none-linux_x86_64.whl  tensorrt-8.6.1-cp36-none-linux_x86_64.whl   tensorrt-8.6.1-cp38-none-linux_x86_64.whl   
tensorrt-8.6.1-cp311-none-linux_x86_64.whl  tensorrt-8.6.1-cp37-none-linux_x86_64.whl   tensorrt-8.6.1-cp39-none-linux_x86_64.whl

python3.11-tensorrt> /nix/store/d3dzfy4amjl826fb8j00qp1d9887h7hm-stdenv-linux/setup: line 131: pop_var_context: head of shell_variables not a function context
error: builder for '/nix/store/8pw2fjq86vbkdd6s1bl6axfkhbnm18lr-python3.11-tensorrt-8.6.1.6.drv' failed with exit code 2;
       last 10 log lines:
       > Using pythonImportsCheckPhase
       > Sourcing python-namespaces-hook
       > Sourcing python-catch-conflicts-hook.sh
       > Sourcing auto-add-driver-runpath-hook
       > Using autoAddDriverRunpath
       > Sourcing fix-elf-files.sh
       > Running phase: unpackPhase
       > tar: TensorRT-8.6.1.6/python/tensorrt-8.6.1.6-cp311-none-linux_x86_64.whl: Not found in archive
       > tar: Exiting with failure status due to previous errors
       > /nix/store/d3dzfy4amjl826fb8j00qp1d9887h7hm-stdenv-linux/setup: line 131: pop_var_context: head of shell_variables not a function context
       For full logs, run 'nix log /nix/store/8pw2fjq86vbkdd6s1bl6axfkhbnm18lr-python3.11-tensorrt-8.6.1.6.drv'.