-
Notifications
You must be signed in to change notification settings - Fork 35
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
Fails to open a bidirectional stream on STOP_SENDING #36
Comments
Thanks! That is very likely, since quant itself won't generate |
By the way, the same thing happens with MAX_STREAM_DATA. Some options for a local repro:
The latter option is nice because we can use the public repository, but it requires some software setup. |
I have docker running, do you have some simple instructions for how to run your test with it locally? |
Sorry I was out for a while. Here are some directions for running the test under docker...
If you see something like this, it means the server sent CONNECTION_CLOSE, probably because of this issue:
Unfortunately this doesn't work for me under Windows -- only under Linux. On Windows the packets don't escape the docker container. I can't tell if this is a docker issue, a windows firewall issue, or something else. |
This should be fixed in fb43936 and later |
It looks like quant is not opening bidirectional streams on receipt of STOP_SENDING, per the change in draft-17. Here is the relevant language:
I haven't checked whether it opens streams on MAX_STREAM_DATA.
Here' s log showing the receipt of STOP_SENDING on stream 4 at 18.579:
The text was updated successfully, but these errors were encountered: