-
Notifications
You must be signed in to change notification settings - Fork 5
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
Low-level websocket error when connecting to -api #228
Comments
The top one is new to me. Do you think it has something to do with the client attempting to connect to /subscriptions before the schema has loaded? Will investigate further on -api side. I have certainly seen the bottom one before. I think it's related to the browser trying to reconnect to a websocket -api has closed. Possibly -api is closing them incorrectly. I'll investigate. |
Sorry should have been clearer - they're both the same thing but seen in different browsers. The top one is firefox, the bottom one is chrome. This happens when the page is first loaded, and the clients are first loaded. It's happening right down at the apollo client level.
It's entirely possible it's something to do with timing at the client end.. |
Okay. If you close the web browser, restart -api and then load the page do you see the error? |
No, although actually if I hit reload lots of times it happens sometimes and not others. Odd. I guess that probably points to a brower-side timing issue with the async calls? |
I actually think it's to do with -api and websocket connections not being disposed of correctly. There is an error that occurs in the logs I see every now and then generated from here https://github.com/goodrobots/maverick-api/blob/master/maverick_api/modules/base/tornadoql/subscription_handler.py#L211 |
Looks like when initial subscription is made the websocket gets cut off or interrupted. Is it from the server side? Can't see anything obvious in the logs.
The text was updated successfully, but these errors were encountered: