mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 12:17:13 +00:00
kevinveenbirkenbachandClaude Opus 5
0c20aeb800
The spec polled /generated/licensing.html, which the server can only answer with 404. Every unmatched path goes through _version() at server.py:124, where the first segment is checked against library.versions(), and that list is [latest, *release_tags, deployed] and nothing else. The word generated is a directory inside a version tree, never a version, so the poll could not succeed whatever the build did. It then held the full resolveTimeout(5_300_000) budget before giving up.
Sphinx writes the page one level down: commands.py:37 sets generated = src / "generated" and line 112 writes generated/licensing.rst into it, so the address is /deployed/generated/licensing.html. The sibling spec had it right all along, test-yaml-page.js:5 being /deployed/compose.html, and this spec is a copy of it that lost the segment while keeping the comment about the deployed working tree on line 25.
Nine jobs of run 39530674125 fail on this one line. The rescue bundles settle it in a single pair of counters from one container in one window: 222 requests for /generated/licensing.html answered 404 beside 2 for /deployed/compose.html answered 200, with the container running and healthy throughout.
It is not the ModuleNotFoundError that 6f7dda1a9f guards. That one is real and belongs to the latest and v16.2.1 builds, which answer 500, and no spec in the run requests /latest/ anything. Both changes are needed and neither substitutes for the other.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>