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.
This commit is contained in:
atlas 2026-09-17 19:29:46 +02:00
commit 60393d0e32

View file

@ -961,9 +961,9 @@ let
# Reads the host's tmpfiles rules, not the options: the socket directory # Reads the host's tmpfiles rules, not the options: the socket directory
# nginx and the container share is created there, so a rename that # nginx and the container share is created there, so a rename that
# resolved but stopped reaching the module would leave the gateway # resolved but stopped reaching the module would leave the gateway
# proxying to a path nothing creates. All four old paths are defined in # proxying to a path nothing creates. All three old paths are defined
# the fixture, so removing any single shim fails the eval rather than # in the fixture, so removing any single shim fails the eval rather
# only the one this assertion reads. # than only the one this assertion reads.
# THREE movers (authBridgeUrl, forgeTokenFile, queue.clientSecretFile) # THREE movers (authBridgeUrl, forgeTokenFile, queue.clientSecretFile)
# are asserted as rendered effects rather than as option values, so a # are asserted as rendered effects rather than as option values, so a
# rename that resolved but stopped reaching the module is caught # rename that resolved but stopped reaching the module is caught