go
- The shutdown grace that never ran
A Go proxy's 5-second shutdown grace was dead code. A real drain and socket activation fixed restarts; KillMode, a WaitGroup and a lock needed fixes too.
- The proxy said unloaded. The model was loading.
A context probe gave up on four models loading behind my LLM proxy: its status was a snapshot up to 30 s old. Then a 336 ms stream timed at 120 s.
- The first engine on the A9 was started to be stopped
v0.3.1 would refuse any engine start on the A9 until its agent was replaced. Then my proxy started its first engine there, for a benchmark to take away.
- The design review found a Konsole tab
My own review of my LLM proxy found a measured MEDIUM. The design review's HIGHs included ssh riding a terminal tab and a help command that started the proxy.
- The benchmark said it was waiting. Once.
My LLM proxy must never pause the A9's benchmark queue. It couldn't see the queue between jobs, while it waited behind the proxy, or mid-handover.
- Restart a Go server under systemd without dropping requests
A systemd socket holds the port, the Go server drains on SIGTERM, KillMode=mixed spares its children: restarts refuse nothing, cut no stream within the drain.
- The fixes had the bugs
Seven re-review passes over a Go LLM proxy found 11, 8, 10, 4, 2, 1 and 0 bugs, nearly all in the fixes. Two could have crashed the process.
- Cutting a stream doesn't cancel the turn
A LAN proxy for two GPU boxes learned to switch llama.cpp engines. Cutting streams to switch faster failed: agent clients re-send the turn.
- The alert about the blackout needs the internet too
Power-cut alerts leave over an uplink the cut can take down: retries, per-channel queues, a router watchdog, and a status LED that goes dark.
- 29 of 34 passing agent runs had a blocker the hidden tests never saw
Blind review packets, a merge rubric and probes that must run: 34 agent-written money transfers passed the hidden tests, and review found a blocker in 29.