Tatsh / sbclaude / 32911047693

100%

push

github

project: retry a box that never starts, and say why it did not

A box that dies before the session begins left nothing to go on. The
fullscreen TUI puts claude on the terminal's alternate screen and that
screen is discarded on exit, so whatever was printed on the way down went
with it; docker's own diagnosis on stderr survived, but the `docker run`
behind it -- which is usually where the answer is -- was never shown at
all.

Three things, all about that moment:

Retry. Exit codes 125-127 are what the docker CLI reserves for a
container that never ran, and a box that exits within seconds died before
a session could begin. Either is a failure to start and is launched
again, three attempts in all. A signal death (128+) is neither -- a
session ended with Ctrl-C did exactly what was asked -- and a session
that ran and then ended is never retried, whatever its exit code. The
command is rebuilt per attempt rather than reused, which is what lets the
GPU probe below take effect on the next try.

Somewhere to read it afterwards. Every failed attempt goes to syslog with
docker's message and the full command, one entry per line because a
single long entry is what journalctl truncates at the terminal width. A
syslog that cannot be written says so and does not take the session down
with it. `docker run` is now spawned through Popen so its stderr can be
relayed as it arrives and a bounded tail kept back for the log; stdin and
stdout stay on the terminal untouched, because -t and the TUI both need a
real one and the container's output already comes back on stdout.

--no-fullscreen (config key fullscreen) leaves the TUI setting as the
host has it, so a failing session's output stays on the normal screen.
The failure message points at it, but only when the box got far enough
that claude could have printed something.

And the cause that prompted all this: --gpus all with no usable card is
unresolvable against the CDI registry, which the daemon treats as a
warning rather... (continued)

224 of 224 branches covered (100.0%)

Branch coverage included in aggregate %.

101 of 101 new or added lines in 3 files covered. (100.0%)

863 of 863 relevant lines covered (100.0%)

5.0 hits per line