-
Notifications
You must be signed in to change notification settings - Fork 352
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
Close ws connections inactive for more than x seconds #846
Comments
Can be done with the |
I'm here |
I don't think the |
Awesome! core/core/cat/routes/websocket.py Line 48 in f14f2c0
|
Or there was a reason for not deleting it? |
We chose not to delete it just to preserve Working Memory in case of disconnection |
And deleting the stray instance may arise problems when an action using the stray is scheduled in the WhiteRabbit. |
Proposal: Unless as @jacopopalumbo01 said there is a breaking dependency between the objects |
After 23/09/2024 dev meeting: Have a new |
This comment was marked as abuse.
This comment was marked as abuse.
Because you may lose the websocket connection but still want to reattach the same conversation |
Hello, I've added a feature to manage the session expiration, as @valentimarco and I suggested during a previous dev meeting. Hope this could help |
PR in review, merging soon |
At the moment all ws connections remain open forever XD
We can check the old ones and close them, maybe using the
WhiteRabbit
by @jacopopalumbo01 or (tmp) just running a loop on active connections when a new user tries to connect, and close the old inactive onesThe text was updated successfully, but these errors were encountered: