- As per RTC10, library must not register any listeners for internal use.
- At most of the places, ably-ruby uses emitter callbacks to detect state changes and execute internal code.
- This is causing problems in order of code execution with respect to internal and external code. Same is being reflected in flaky behaviour of the tests. To mitigate this flaky test behaviour, usage of
EventMachine.next_tick can be found in the emitter callbacks. But, this is not a proper solution for apps running in production.
- We have fixed one of the similar issue as a part of a3d9746.
- Aim of this issue is to find and implement code without emitter callback registrations.
┆Issue is synchronized with this Jira Task by Unito
