insideTheFluxandClaude Opus 5.5 e99fbea7f9 Control port: bound the close drain in total; the reset test waits for the rejection ...

close_gracefully read with a 500 ms timeout per read but no overall limit, so a local client
sending one byte every few hundred milliseconds kept the drain (and its connection slot) going
until it had sent MAX_LINE. Each read now waits at most the time left of DRAIN_TIME (1 s).
New test a_closing_connection_is_not_held_open_by_a_trickling_peer: without the limit it drains
for 10 s.

tcp_connection_is_closed_after_junk no longer sleeps before its second write: it reads the
reply and the rejection first, so the server has rejected the junk before the next line is
sent. It still pauses before the last read so that a reset can arrive. Without
close_gracefully it fails with os error 10053 on Windows.

From CodeRabbit's review of #2723.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PtjHGt5gnCHXgLt4NbGorf

2026-10-23 11:59:47 -07:00

..

lightcraft

Control port: bound the close drain in total; the reset test waits for the rejection

2026-10-23 11:59:47 -07:00

lightcraft-cli

CI: one test binary per crate, line tables only, one WASM check (#2710)

2026-10-23 13:34:30 -04:00

lightcraft-web

Merge track r1-rawcat into next

2026-10-21 14:58:55 +00:00