Tag: testing

  1. No. 015

    Argument list too long, part 2: the prompt goes in a file

    Part 1 bought room under the 128 KB per-argument limit Linux has with the usual 4 KB pages by counting notes instead of listing them. Part 2 is the real fix: my launcher writes the startup notes to a private file and hands Claude Code only its path. On the way, a test showed why a size cap counted in characters would have let through a string almost twice the limit.

  2. No. 010

    My slow test gate hid its own failures

    My push checks grew from 19 seconds to nearly two hours in seven weeks. Time limits, idle connections and even the failure report turned that wait into silence, until a 71-second check found what the full gate only reached at minute 70.

  3. No. 009

    My tests kept agreeing with me

    653 unit tests passed and a real git push still walked straight past my pre-push hook. Again and again over six weeks my tests agreed with my own assumptions instead of the real input, from a hosted test runner to model output and a fixed clock.

  4. No. 008

    My router trusted a usage reading that was seven hours old

    Spreading work across several Claude Code and Codex accounts means watching their five-hour and weekly limits. A cached reading said an account was nearly empty while its live session was past the threshold, and fixing that grew into one line that tells every agent where to go.