- Notifications
You must be signed in to change notification settings - Fork329
Avoid handling ping after close frame has been sent#394
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Any chance you have time to take a quick look at this ? |
825873c
to9b5a15b
Compare3500fce
toa94999f
CompareUnfortunately this doesn't work. writeFrame already has a check like this built in so it makes sense it doesn't work. There is definitely a bug in#298, but need to dig deeper to figure out what. See the test I added to your commit, it still fails. |
268b079
toe4879ab
CompareSeee4879ab for the test |
Closes#298Closes#394The close frame was being received from the peer before we were able to reset ourwrite timeout and so we thought the write kept failing but it never was...Thanks@univerio and@bhallionOhbibi
Fixed in dev, see28c6709 |
Fixes#298