We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
We are handling http2 frames in a separate thread.
A race condition could happen in the following case:
main thread: receive Connect frame handler thread: start processing the frame
main thread: receive Reset frame handler thread: tries to write to write to the stream. But the stream is now closed.
In practice, it rarely if ever happens with our regular h2 handlers.
But with websockets, some of the handlers have a time.sleep instruction, and I have noticed it occasionally.
time.sleep
The text was updated successfully, but these errors were encountered:
cc @jgraham
Sorry, something went wrong.
No branches or pull requests
Hi,
We are handling http2 frames in a separate thread.
A race condition could happen in the following case:
main thread: receive Connect frame
handler thread: start processing the frame
main thread: receive Reset frame
handler thread: tries to write to write to the stream. But the stream is now closed.
In practice, it rarely if ever happens with our regular h2 handlers.
But with websockets, some of the handlers have a
time.sleep
instruction, and I have noticed it occasionally.The text was updated successfully, but these errors were encountered: