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

Fix deadlock in websocket server #342

Merged
merged 2 commits into from
Apr 23, 2024
Merged

Conversation

arjo129
Copy link
Member

@arjo129 arjo129 commented Apr 22, 2024

Bug fix

OK So I'm not too happy with this "Fix" but it probably will resolve our deadlock issue.

This fixes a deadlock we were facing in production where in the event the server fails to connect after a reconnection is requested, the library deadlocks.

This is a rather dumb mistake. I think I left this in as a vestige of my
testing. However, the websocket client was refusing to reconnect thanks
to a deadlock caused by this variable.

Signed-off-by: Arjo Chakravarty <arjoc@google.com>
Copy link
Member

@aaronchongth aaronchongth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@arjo129 arjo129 merged commit 69d778f into main Apr 23, 2024
3 of 4 checks passed
@arjo129 arjo129 deleted the arjo/fix/deadlock_in_websocket branch April 23, 2024 02:06
arjo129 added a commit that referenced this pull request Jun 7, 2024
This is a rather dumb mistake. I think I left this in as a vestige of my
testing. However, the websocket client was refusing to reconnect thanks
to a deadlock caused by this variable.

Signed-off-by: Arjo Chakravarty <arjoc@google.com>
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

3 participants