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

Release: ready retries #756

Merged
merged 2 commits into from
Nov 7, 2016
Merged

Release: ready retries #756

merged 2 commits into from
Nov 7, 2016

Conversation

shosti
Copy link
Contributor

@shosti shosti commented Nov 7, 2016

No description provided.

Emanuel Evans and others added 2 commits November 6, 2016 11:06
When the extension automatically reconnects after a connection failure, it sends
its current state to the server. However, it seems that under certain
circumstances the server will keep around a "zombie" connection (that could be
"ready") until it times out, so the new connection can't move to "ready" until
the old connection clears (since we enforce that only one connection can be
"ready" per worker). In this case, it makes sense to retry for a while instead
of alerting the user. (Manual state updates won't retry under any
circumstances.)

My only concern is that this introduces a mismatch between the extension state
and the server state, which could be hard to debug if something goes wrong. But
I can't think of a better alternative.

Fixes #752
@rainforest-bot rainforest-bot merged commit 68dd2fc into master Nov 7, 2016
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