ls but with io_uring

Update nix/cache.nix hash #3

merged opened by knightpp.bsky.social targeting main

It seems it become stale after Zig deps updates.

Labels

None yet.

Participants 4
AT URI
at://did:plc:3zsjx5jgd6dbi4orckspsqiq/sh.tangled.repo.pull/3lolzlm4t7222
+1 -1
Diff #0
+1 -1
nix/cache.nix
··· 17 17 mv $ZIG_GLOBAL_CACHE_DIR/p $out 18 18 ''; 19 19 20 - outputHash = "sha256-hAq1/uE9eu/82+e079y+v9EnN0ViXX7k3GwkgQkxOyo="; 20 + outputHash = "sha256-le8JKDyBHOZliJZjiZHEM5Kl9MfBnCXkKFAyy1f0GDM="; 21 21 outputHashMode = "recursive"; 22 22 outputHashAlgo = "sha256"; 23 23 }

Submissions

sign up or login to add to the discussion
knightpp.bsky.social submitted #1
rockorager.dev

Thanks!

handle.invalid

yes the hash of the cache has to be updated on dependency updates as the cache.nix file basically fetches all dependencies and hashes where zig stores them recursively to produce a hash.

pull request successfully merged
knightpp.bsky.social submitted #0

ah patch submissions are trailing EOL sensitive. can you run git diff | xclip -sel c or git diff | pbcopy or git diff | wlclip and resubmit?

alternatively, you can open a PR straight from your fork!

knightpp.bsky.social

Thanks!