mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-11 21:26:44 +00:00
kevinveenbirkenbachandClaude Opus 5
83c2e040dc
0d8ed0ba8 bounded these call sites with one ceiling for both operations. The two are not equally safe to cut. A SIGTERM landing mid-postinst leaves dpkg interrupted, and in docker_dataroot.sh that fails every later filesystem candidate and sends the run through decline() - one truncated package install becomes a dead job. An interrupted update has no such cascade; it just repeats. Measured on ubuntu:latest with the exact commands: update 10s, install zfsutils-linux 20s. 1200s is a 60x margin on the operation that carries the cascade, and update keeps the 600s it cannot plausibly need more than. This breaks the single-number invariant with scripts/install/apt.sh:19, which is already broken in fact - that call site carries a different Acquire option set than these three do. 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. ✅