kevinveenbirkenbachandClaude Opus 5.5 870433e74d fix(swarm): attach the nodes of a high worktree slot through the cache pool ...

01_bootstrap.sh pins the five swarm nodes into the shared cache network
at 200 + INFINITO_INSTANCE * 5. That band fits a /24 only for instances
0 to 10; from instance 11 on the script aborted with "pushes the node
band past ...254", so no worktree past slot 10 could start a swarm
cluster while the package cache runs. Five nodes per slot cannot fit
255 slots in one /24 with any fixed formula.

Instances whose band fits keep their pinned addresses, so the primary
checkout and CI behave as before. Above that, the nodes join the cache
network without --ip and Docker assigns them from its pool (the upper
half of the subnet), the same way every worktree stack container joins
it. Nothing in the repository reads the nodes' cache-network addresses.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-28 23:01:30 +01:00

..

act

feat(ci): keep GitHub-hosted runner labels current through the updater

2026-10-19 16:56:52 +02:00

ci

fix(ci): name the preserved environment for sudo-rs runners

2026-10-19 13:07:18 +02:00

local

Merge remote-tracking branch 'upstream/main' into feature/role-stalwart-mail-swarm

2026-09-21 03:25:20 +04:00

swarm

fix(swarm): attach the nodes of a high worktree slot through the cache pool

2026-10-28 23:01:30 +01:00

utils

fix(ci): give apt installs more room than apt updates

2026-08-20 14:23:30 +02:00

distros.sh

fix(swarm-test): put the step guard on the same side of sudo as its payload

2026-09-01 12:36:10 +02:00

roundtrip.sh

test(environment): derive the disable set instead of listing it

2026-08-06 10:31:05 +02:00