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

Not sending messages to closed websocket connections #99

Merged
merged 1 commit into from
Jun 22, 2017

Conversation

schmidt-sebastian
Copy link
Contributor

@schmidt-sebastian schmidt-sebastian commented Jun 22, 2017

This should be a safe change since the timer function 'nop' is only ever run after the WebSocket is initialized.

This works around potential issues in the WebSocket layer after we close the connection and should address Google-internal issue: https://b.corp.google.com/issues/62363018

I believe this should be a safe change since the timer function nop is only ever run after the websocket is initialized.
This works around potential issues in the websocket layer after we close the connection and hopefully addresses
https://b.corp.google.com/issues/62363018x
Copy link
Contributor

@mikelehen mikelehen left a comment

Choose a reason for hiding this comment

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

LGTM

@schmidt-sebastian
Copy link
Contributor Author

@paulb777 Paul, it looks like the Travis build passed but took longer than the 10 minute timeout. Can you let me know if we are ok to merge?

@paulb777 paulb777 self-requested a review June 22, 2017 21:08
@paulb777
Copy link
Member

OK to merge. Thanks!

@schmidt-sebastian schmidt-sebastian merged commit 9917869 into master Jun 22, 2017
@schmidt-sebastian schmidt-sebastian deleted the mrschmidt-databasecrash branch June 26, 2017 22:09
XiangtianDai pushed a commit that referenced this pull request Jul 28, 2017
minafarid pushed a commit to minafarid/firebase-ios-sdk that referenced this pull request Jun 6, 2018
I believe this should be a safe change since the timer function nop is only ever run after the websocket is initialized.
This works around potential issues in the websocket layer after we close the connection and hopefully addresses https://b.corp.google.com/issues/62363018x
@firebase firebase locked and limited conversation to collaborators Nov 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants