mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-13 22:26:49 +00:00
kevinveenbirkenbachandClaude Opus 4.7
19f9735909
The URL-reachability probe now bounds its wall-clock end-to-end: allow_redirects=False (a redirect chain previously stacked timeouts), a 5h30m global deadline that marks in-flight probes as warnings on expiry, and live `[done/total]` progress every 50 probes. Submission order is shuffled so same-host URLs no longer batch at the front and self-DoS one origin. The Docker image-version test drops its bespoke sequential fetch loop and calls find_outdated_updates() from utils.update.docker, so it now shares the INFINITO_WORKER_FETCH-sized worker pool with the repository-refs check. `scripts/tests/code/wrapper.sh` propagates BASH_ENV into the container exec — without it INFINITO_WORKER_FETCH was unset inside the container and the URL probe collapsed to 1 worker. `make test` gains test-external; `make dotenv-force` regenerates .env with a stripped environment so stale BASH_ENV-preloaded INFINITO_* values cannot pin old numbers via setdefault. Co-Authored-By: Claude Opus 4.7 (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. ✅