Double EBADF Error Callback On DNS Fail #565
Description
Running into an issue where when calling a DNS fail (server down), a single setOnMessageCallback lamda gets called twice with a ready state of CLOSED and an EBADF error. Is there a reason this library sends multiple messages back? That is an issue if there's no way to prevent further incoming messages as I'd prefer to end a thread and pursue a retry without having ghost callbacks subsequently returning when live callbacks attached to destructing promises are essentially creating a race condition.
[Websocket] ReadyState: Closed
[Websocket] Unexpected exception during connection.
[Websocket] Error: Unable to connect to localhost on port 8080, error: Connect error: Bad file descriptor
[Online] ❌ Connection failed or timed out.
.... (cropped other messages from main thread)
[Websocket] ReadyState: Closed
[Websocket] Unexpected exception during connection.
[Websocket] Error: Unable to connect to localhost on port 8080, error: Connect error: Bad file descriptor
[Online] ❌ Connection failed or timed out.
It is called twice despite only a single call to start() ... there is also no other calls to close(), etc. Only start() was called.