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

tpr/issue167: Fixed explicit connect after connection has disconnected #172

Merged
merged 2 commits into from
Oct 5, 2016

Conversation

trenouf
Copy link
Contributor

@trenouf trenouf commented Oct 5, 2016

Also a test for the regression.

Tim Renouf added 2 commits October 4, 2016 18:28
#167
says that, after a disconnect caused by a network outage, then waiting
long enough for the connection to go disconnected state and the channels
to be detached, an explicit AblyRealtime.connection.connect() is not
immediately actioned. Instead it does not connect until up to a couple
of minutes later.

It looks like the condition is incorrect in ConnectionManager.connect()
to see if a connection attempt is already underway, so the explicit
connect does not do anything. Instead it waits until the next time it
would have attempted a reconnect anyway.

Fixed.

Also fixed so that the connect happens even if there is a connection
thread already started.
@mattheworiordan
Copy link
Member

Thanks, LGTM, should I merge

@trenouf
Copy link
Contributor Author

trenouf commented Oct 5, 2016

Yes please.

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

Successfully merging this pull request may close these issues.

2 participants