Skip to content
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

Ably robustness improvements #2991

Merged
merged 2 commits into from Jun 13, 2020
Merged

Ably robustness improvements #2991

merged 2 commits into from Jun 13, 2020

Conversation

jscheid
Copy link
Contributor

@jscheid jscheid commented Jun 13, 2020

The last item is the main reason for this PR. Currently, the ack messages that Ably sends back especially for detach won't be processed correctly because by the time they arrive, the channel has already been released and Ably can't find it in its mapping. I think this should be harmless but there is a chance this is causing problems.

The code could be a lot nicer if we could use Ably.Promise, but that would be a breaking change so I left it for another day.

This ensures Prettier 1.x is used for formatting.
- Refactor to be async
- Fix unsubscribe call (cf. ably/ably-js#667)
- Report missing X-Subscription-ID header
- Report errors when entering presence
- Report errors during leave or detach
- Wait for leave and detach to complete before releasing channel
@jscheid jscheid changed the title Ably cleanup Ably robustness improvements Jun 13, 2020
@rmosolgo
Copy link
Owner

Awesome, thanks for the improvements here. (🙈 My production experience is with Pusher, which does not have as many lifecycle steps!)

@rmosolgo rmosolgo merged commit 7ef6e81 into rmosolgo:master Jun 13, 2020
@rmosolgo
Copy link
Owner

🚢 in 1.7.10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants