check / check (push) Waiting to run
A request past the server's 30-second limit answered 408, which tells the client it was too slow sending its request, and /api/v1/stats answered 500 when its 4-second read ran out. The limit is now chi's middleware.Timeout, which answers 504 and never writes from a second goroutine while the handler is writing. Right after each database read or host name lookup, whatever came back, a handler asks deadlinePassed whether its time limit has passed and, if so, answers 504, with the JSON error body on JSON routes: a cut-off read can return part of its rows without an error. The health check is unchanged. Model: opus-5-5