beardthelion d4e5ecf299 fix(review): bound the probe's channel waits and stop overstating the handshake ...

Cross-model review round, findings corroborated by the in-process reliability
reviewer.

Both channel waits were unbounded. If the reader thread never reached its read,
or never returned after the peer close, the test wedged the binary instead of
failing, and cargo test has no per-test timeout to rescue it. Both are now
recv_timeout with bounds far above any real scheduling delay, so hitting one is
a genuine defect report rather than a flake, and the failure names which wait
stalled.

The handshake paragraph also overstated what the handshake buys. It listed "the
reader thread not yet scheduled to reach the read at all" among the states the
handshake removes, which reads as though the whole scheduling window is closed.
It is not: the handshake removes thread spawn from the window, and a reader
descheduled between its own Started send and its read is still a false-green
path. That path is now stated plainly instead of being left to the following
paragraph to correct.

Re-verified after the change: probe RED 50/50 under a deleted
set_nonblocking(false) at full-suite parallelism, RED on the named message under
a deleted set_read_timeout, 50/50 green unmutated, fmt and clippy clean.

2026-08-10 13:55:53 -05:00

..

src

fix(git-remote): reject malformed pkt-line length headers instead of flushing

2026-08-09 22:21:00 -05:00

tests

fix(review): bound the probe's channel waits and stop overstating the handshake

2026-08-10 13:55:53 -05:00

Cargo.toml

test(git-remote): tear down the fetch tree with a Job Object on Windows (#192)

2026-08-09 22:39:31 -05:00