You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if I'm missing something, but here it goes..
Steps to reproduce
1 - Given an actioncable connection with two identifiers;
2 - Connect one user passing both identifiers;
3 - Close the browser or call unsubscribe;
4 - Open rails console and disconnect that specific connection manually
Expected behavior
After unsubscribing / manually disconnecting I would expect the connection to no longer be listed in Redis pubsub, or at least some state change on ActionCable.server.remote_connections.
Actual behavior
The connection seems to live in redis pubsub and ActionCable.server.remote_connections.
System configuration
Rails version:
Rails 5.1.4 Ruby version:
2.4.2
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails team are limited, and so we are asking for your help.
If you can still reproduce this error on the 5-1-stable branch or on master, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions.
I'm not sure if I'm missing something, but here it goes..
Steps to reproduce
1 - Given an actioncable connection with two identifiers;
2 - Connect one user passing both identifiers;
3 - Close the browser or call unsubscribe;
4 - Open rails console and disconnect that specific connection manually
Expected behavior
After unsubscribing / manually disconnecting I would expect the connection to no longer be listed in Redis pubsub, or at least some state change on ActionCable.server.remote_connections.
Actual behavior
The connection seems to live in redis pubsub and ActionCable.server.remote_connections.
System configuration
Rails version:
Rails 5.1.4
Ruby version:
2.4.2
The text was updated successfully, but these errors were encountered: