mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 11:46:35 +00:00
kevinveenbirkenbachandClaude Opus 5
85de49f1df
Docker hands out the lowest free address, so a node attached without one lands in the same band where the cache services pin themselves and can take an address its owner then cannot claim. That happened: a node held the registry-cache address and every swarm cycle died at the image pull. Each node now takes a fixed address, offset per instance because worktrees share the primary's cache network while clearing only their own cluster, so a surviving cluster elsewhere no longer collides with a fresh one. A failed attach is classified rather than swallowed. The nodes already carry extra_hosts pointing at the cache addresses, so a node that silently fails to attach reaches neither apt nor the registry and reports it as network flakiness. Only the markers the docker_network_noop filter already treats as benign are tolerated; anything else stops the bootstrap. The subnet is asserted rather than assumed, since the address arithmetic only holds for a x.y.z.0/24. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Test Utilities 🧪
This directory holds the operational side of testing in Infinito.Nexus.
These assets are meant to support confidence, not ceremony. They help the project validate real-world behavior across local development, CI environments, and deployment-oriented smoke tests. The emphasis is on practical feedback: when something breaks, the surrounding test tooling should make the failure easier to understand, easier to reproduce, and easier to clean up. 🚀
Good changes in this area usually make the test experience more:
- repeatable
- diagnosable
- environment-aware
- safe to rerun
The ideal outcome is boring reliability: contributors should be able to trust that a test run says something meaningful about the system, not just about the machine that happened to execute it. ✅