v1 proxy test: order arrivals by limiter state; note the 499-on-served-200 defect for v2.1

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-25 11:08:16 -07:00
parent 27debb9790
commit 481ea12f4c
2 changed files with 32 additions and 4 deletions
@@ -87,3 +87,12 @@ reason.
  (mine): the third acquirer sent its result before its deferred release ran, so the final
  count check could observe one slot still held. The given file now releases before reporting.
  Ornith found it and measured the flake rate rather than editing the protected file.
+- 2026-09-25, task 05, third session: also saw `TestQueueFullIs503` fail with
+  `Requests:3 Errors:2`. Two causes. (1) Test fault (mine): arrival order rested on 30 ms
+  sleeps; the given test now waits on the limiter's in-flight and queued counts. (2) A real v1
+  defect, verified by the owner with a diagnostic build (5 of 8 runs): after a forward completes,
+  `forward.go` checks `r.Context().Err()` and, when the client has already closed its connection,
+  records a served 200 as a 499 "client cancelled" error. Cancellation must be what the reverse
+  proxy itself observed, never a post-hoc context check. Scheduled as v2.1 task 01; not fixed in
+  task 05, which is wiring only. The session then ended on a refused read of `/proc/loadavg` —
+  the seventh refusal-ending. Model fault.