websocket
: send
callbacks are not all called if multiple messages are sent rapidly
#698
Labels
bug
Something isn't working
Describe the bug
When using the
websocket
transport, ifsocket.send()
is called multiple times in the same tick with a callback provided, some of the callbacks may not be called even though the messages were sent.To Reproduce
Engine.IO server version:
6.5.4
Server
Engine.IO client version:
6.5.0
Client
Expected behavior
The server above should log:
Instead it logs:
It does log
callback 3 called
after about 25 seconds, andcallback 4 called
25 seconds later — enabling debug logs shows thatping
packets are triggering those late callbacks.The client logs that the messages are all received immediately.
Platform:
Additional context
There is an existing test that is supposed to check this scenario. However it does not expose this bug, because it does not specify a transport and defaults to
polling
, which also makes it redundant with the next test. That first test also only sends two messages, when the test program above shows that only the third and further callbacks are delayed.The text was updated successfully, but these errors were encountered: