From 60393d0e32c52c2f5ca64fc96b2aef48ab9d798a Mon Sep 17 00:00:00 2001 From: atlas Date: Thu, 17 Sep 2026 19:29:46 +0200 Subject: [PATCH] module-eval: fix the last stale 'four' count in the swarm-controller comment Same slice, same fact: socketPath lost its pre-rename path, so only three old paths are defined in the fixture now, not four. Missed this sentence while fixing the count three lines below it. --- nix/module-eval.nix | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/nix/module-eval.nix b/nix/module-eval.nix index 6ca1a0cb..b0b26984 100644 --- a/nix/module-eval.nix +++ b/nix/module-eval.nix @@ -961,9 +961,9 @@ let # Reads the host's tmpfiles rules, not the options: the socket directory # nginx and the container share is created there, so a rename that # resolved but stopped reaching the module would leave the gateway - # proxying to a path nothing creates. All four old paths are defined in - # the fixture, so removing any single shim fails the eval rather than - # only the one this assertion reads. + # proxying to a path nothing creates. All three old paths are defined + # in the fixture, so removing any single shim fails the eval rather + # than only the one this assertion reads. # THREE movers (authBridgeUrl, forgeTokenFile, queue.clientSecretFile) # are asserted as rendered effects rather than as option values, so a # rename that resolved but stopped reaching the module is caught