-
Notifications
You must be signed in to change notification settings - Fork 4
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
Exception being thrown from tartiflette #34
Comments
I have noticed that on occasion the Coniql application does not unsubscribe from all of the PVs when the websocket disconnects. For example when navigating away from a webpage displaying PV updates. I was debugging the subscribes and unsubscribes in Coniql and noticed this. If it does not unsubscribe from a PV, then when the page is reloaded, a new subscription is created on top of this and we start a memory leak as the first one never gets removed. I believe this issue is related to the exception detailed in this ticket. The However something else must be happening underneath with the tasks that the A quick fix to avoid this exception is to surround the asyncio.gather with a try-except:
With this fix in place I found that I could no longer reproduce the scenario where Coniql does not unsubscribe from all PVs. The only problem of course is that this fix is in the tartiflette code. |
This will be resolved on moving to Strawberry. |
Resolved in move to use the Strawberry API in PR #44. |
While running coniql locally I occasionally see exceptions being thrown by tartiflette. This occurred when testing the cs-web-proto and using coniql+cs-web-proto to monitor 100 PVs changing at a rate of 10Hz.
Exception:
Traceback (most recent call last): File "/home/cnuser/.local/share/virtualenvs/coniql-W5jWBl11/lib/python3.7/site-packages/tartiflette/execution/execute.py", line 200, in execute_operation fields, File "/home/cnuser/.local/share/virtualenvs/coniql-W5jWBl11/lib/python3.7/site-packages/tartiflette/execution/execute.py", line 147, in execute_fields return_exceptions=True, concurrent.futures._base.CancelledError
The text was updated successfully, but these errors were encountered: