No description
Find a file
SomeoneSerge c8b8b56456 cuda: support cudnn manifests
Also changes the schemas a bit (still don't care about migrations),
switches to named_params!, fixes up perf issues when ingesting manifests
and/or hrefs into sqlite, etc. Adds sample queries such as "CudaArtifact
conflicts" to datasette config, which explain some issues associated
with choosing an evalModules schema on the cudaPackages side.
2025-05-09 04:05:20 +00:00
npins init 2025-04-20 00:13:35 +00:00
src cuda: support cudnn manifests 2025-05-09 04:05:20 +00:00
static cuda: support cudnn manifests 2025-05-09 04:05:20 +00:00
.gitignore .gitignore: init 2025-04-20 00:15:02 +00:00
Cargo.lock cuda: support cudnn manifests 2025-05-09 04:05:20 +00:00
Cargo.nix feat(fetch-listing): poc recursive fetching 2025-04-27 16:54:04 +00:00
Cargo.toml cuda: support cudnn manifests 2025-05-09 04:05:20 +00:00
default.nix cuda: support cudnn manifests 2025-05-09 04:05:20 +00:00
LICENSE init 2025-04-20 00:13:35 +00:00
README.md cuda: support cudnn manifests 2025-05-09 04:05:20 +00:00
shell.nix cuda: support cudnn manifests 2025-05-09 04:05:20 +00:00

sidx

Work in Progress. Indexing archives and build outputs.

Roadmap

  • PoC: basic reqwest fetcher, minimal snix-castore integration, claims of the form "$uri referred to $blake3 at $time" stored in sqlite.
  • Zip, tar, git fetchers.
  • ELF scanning: claims of the form "$blake3 is ELF" and "$blake3's DT_RUNPATH is $runpath", etc. (DT_NEEDED, .interp, symbols exported in .data and .text)
  • cuobjdump scanner: claims of the form "$blake3 contains PTX or SASS code for $gencode".

Approach

Vapourware and means to an end: this project was originally motivated by the needs of maintaining cudaPackages in Nixpkgs. Specifically, it attempts to answer the question of "what is there to be maintained", improve observability and debug-ability of the package set (cf. demo).