Files
netris-nestri/apps
KAAL1 00a2bdab30 fix(nesinit): give one look at the address socket a deadline
There was a cap on how much this would read and none on how long it would
wait. The far end can accept a connection and then write nothing, and a
read with no deadline turns that into a poll loop that never runs again:
the address already forwarded stays correct, and the better one that
arrives afterwards is never seen. That is the failure this polls to avoid,
reached by a different route.

Five seconds, against a two second interval, so an answer that is merely
slow still lands and one that is never coming is abandoned.

The test hangs against the code as it was, which is the whole point of it.
2026-09-06 14:24:04 +03:00
..
2026-08-31 17:31:23 +03:00