- No changes.
- No changes.
- No changes.
- No changes.
- No changes.
- No changes.
- No changes.
- No changes.
- No changes.
- No changes.
- No changes.
- No changes.
- No changes.
- No changes.
-
The Action Cable client now ensures successful channel subscriptions:
- The client maintains a set of pending subscriptions until either the server confirms the subscription or the channel is torn down.
- Rectifies the race condition where an unsubscribe is rapidly followed by a subscribe (on the same channel identifier) and the requests are handled out of order by the ActionCable server, thereby ignoring the subscribe command.
Daniel Spinosa
-
Truncate broadcast logging messages.
J Smith
- No changes.
- No changes.
- No changes.
- No changes.
- No changes.
- No changes.
- No changes.
-
Fix
ArgumentErrorwith ruby 3.0 onRemoteConnection#disconnect.Vladislav
- No changes.
- No changes.
- No changes.
- No changes.
- No changes.
- No changes.
-
ActionCable::Connection::Basenow allows intercepting unhandled exceptions withrescue_frombefore they are logged, which is useful for error reporting tools and other integrations.Justin Talbott
-
Add
ActionCable::Channel#stream_or_reject_forto stream if record is present, otherwise reject the connectionAtul Bhosale
-
Add
ActionCable::Channel#stop_stream_fromand#stop_stream_forto unsubscribe from a specific stream.Zhang Kang
-
Add PostgreSQL subscription connection identificator.
Now you can distinguish Action Cable PostgreSQL subscription connections among others. Also, you can set custom
idincable.ymlconfiguration.SELECT application_name FROM pg_stat_activity; /* application_name ------------------------ psql ActionCable-PID-42 (2 rows) */
Sergey Ponomarev
-
Subscription confirmations and rejections are now logged at the
DEBUGlevel instead ofINFO.DHH
Please check 6-0-stable for previous changes.