From 04f161a95bb98f6c9cf4369df29c28c59f31fcb8 Mon Sep 17 00:00:00 2001 From: atlas Date: Sun, 30 Aug 2026 20:20:40 +0200 Subject: [PATCH] nix/docs: stop naming a specific remote builder in a comment MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- nix/docs/default.nix | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/nix/docs/default.nix b/nix/docs/default.nix index 3d809600..187fde18 100644 --- a/nix/docs/default.nix +++ b/nix/docs/default.nix @@ -26,8 +26,9 @@ let # context so `builtins.path` hashes only the nix/ file content, not # the full flake source (Rust, frontend, markdown, …). Result: the # docs drvs only change when a .nix file changes, not on every - # commit — the muede-pc2 remote builder can reuse its cached result - # for any commit that doesn't touch nix/. + # commit — a remote builder can reuse its cached result for any commit + # that doesn't touch nix/. (Named no machine: which builders are + # reachable depends on the network the deployer is on.) nixSrc = builtins.path { path = builtins.unsafeDiscardStringContext (toString self + "/nix"); name = "hyperhive-nix-src";