-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ws.readData() unable to handle a null result #71
Comments
I don't understand your question, but when I try to run your code, there is no error? This project seems to be unmaintained |
I'll retest. Nim and this package have been updated since. This package just a few minutes ago as I write this. |
|
When I receive data from the websocket that has a null result, the program crashes.
In the attached test case, if you comment out the line that sends the subscribe request the program doesn't crash. This is because the message that is sent back includes a null result. However the websocket library should be able to handle this.
Here's the output from a Chrome websocket extension that does the same thing. The result from the subscribe request is null, but the websocket loop continues to function as expected.
test_ws.zip
The text was updated successfully, but these errors were encountered: