vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

nix/docs: stop naming a specific remote builder in a comment

Browse source 
The narrowed-source comment justified itself with "the muede-pc2 remote
builder can reuse its cached result". mara, closing the issue I filed
about that builder being unreachable: "this is expected behavior …
depending on what network i am on different builders are available".

So the machine is not a fact about this repo. The reasoning holds for
whichever builder happens to be reachable, and a hostname in a comment is
the thing that rots — the same class as the forge address that has been
wrong twice.
This commit is contained in:
atlas 2026-08-30 20:20:40 +02:00
commit 04f161a95b
1 changed files with 3 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

5
nix/docs/default.nix
View file

@ -26,8 +26,9 @@ let
# context so `builtins.path` hashes only the nix/ file content, not # context so `builtins.path` hashes only the nix/ file content, not
# the full flake source (Rust, frontend, markdown, …). Result: the # the full flake source (Rust, frontend, markdown, …). Result: the
# docs drvs only change when a .nix file changes, not on every # docs drvs only change when a .nix file changes, not on every
# commit — the muede-pc2 remote builder can reuse its cached result # commit — a remote builder can reuse its cached result for any commit
# for any commit that doesn't touch nix/. # that doesn't touch nix/. (Named no machine: which builders are
# reachable depends on the network the deployer is on.)
nixSrc = builtins.path { nixSrc = builtins.path {
path = builtins.unsafeDiscardStringContext (toString self + "/nix"); path = builtins.unsafeDiscardStringContext (toString self + "/nix");
name = "hyperhive-nix-src"; name = "hyperhive-nix-src";