mirror of
https://github.com/storytold/deckcraft.git
synced 2026-10-25 11:07:01 -06:00
dotCooCoo
79c1d578be
When every connection slot was taken, the accepting thread wrote the busy reply and dropped the socket. A peer that had already written a line saw a reset instead of the reason. The busy path now closes the same way a rejected line does: it sends the FIN and drains the socket for at most 250 ms, or the write timeout when that is shorter. The drain set its read timeout on the writing handle and read through a clone of the socket. On Windows, a read timeout set on one handle of a try_clone pair can fail to apply to reads through the other. On Windows 11 a rejected peer that stayed connected then kept its slot until the idle timeout (10 minutes by default) instead of the write timeout. The timeout is now set on the handle that reads. Two tests failed intermittently. a_pipelined_peer_still_reads_why_its_line_was_rejected connected 12 peers through 2 slots, and a slot comes back only after the thread serving the previous peer ends; each peer now has a slot of its own. blocked_ui_times_out_and_full_queue_is_busy relied on a 50 ms sleep to order two requests from two connections; it now accepts either order.