Race Condition: connectTCP and release

[cemreozen]

Peer A:
wait 500;connectTCP FILLER_IP 4444;**wait 500;release CS;**wait 500;sendMessage FILLER_FILENAME sn/file;lsMessages 2;lsMessages 1;exit;

PeerB:
openTCP 4444;block CS;wait 1000;lsMessages 2;lsMessages 1;exit;

Peer A has to wait before sending the message, since the block is not released otherwise due to a race condition arising between connectTCP and release.

[thsc42]

Environment: Windows 11; both peer on same machine. Produced file t.txt containing a few bytes before running test. Started manually B before A.

A:
connectTCP localhost 4444;release CS;sendMessage t.txt sn/file;lsMessages
B:
openTCP 4444;block CS;lsMessages;wait 1000;lsMessages;

Produced expected result.
Comments:
Used lsMessages twice: It is hard to expect how long data transmission actually takes. On B-side: a first lsMessages can fail since the message hasn't yet arrived. A second lsMessages after a - whatever that is - reasonable time should succeed.

Apparently, we have a sync problem here. Could be solved with another block/release pair.

Please check again. Maybe different OS produce different results.