mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-10 04:36:40 +00:00
kevinveenbirkenbachandClaude Opus 5
70f27f82ef
The LUKS step of the DR drill died on `The file /dev/mapper/usbdrill does not exist and no size was specified.` -- from mkfs, not from cryptsetup, because luksOpen had exited 0. The node did have a udev, and it had created the mapper entry: as a symlink to ../dm-1. Modern udev no longer mknods, it only manages symlinks, and the /dev/dm-N target it points at is a devtmpfs node that a container's tmpfs /dev never receives. Without a udev libdevmapper creates the node itself, which is why the debian nodes passed -- their image ships no udevd at all, while arch cannot install systemd without one. Masking udevd in the node image removes the whole class rather than one call site. DM_DISABLE_UDEV rides on the node containers instead of the script because the drill opens the volume a second time through the recover CLI in a separate docker exec, which would not inherit an export. The block-device check then fails loudly with both prerequisites named, and closes the mapping first so an abort cannot leak it onto the runner -- device-mapper is not namespaced and every distro round shares the VM. 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. ✅