We are upgrading from 1.9.2 to 1.14.0. I'm having an issue with this change:
The following sequence of events happens:
I realize that I should be doing graceful shutdown via nghttp2_submit_shutdown_notice(), but that is a large change which I would prefer to not do right now.
This feels like a regression to me (especially since the header frame for the new stream appears to be ignored), but I am not familiar enough with the spec to know for sure.
What do you think about this?
You are right, that commit introduced race. I figured another case that it cannot handle well.
To fix this issue, I reverted part of the commit.
Fix committed via 6858cda
Thanks for the quick response. If possible, it would be great if you could release a 1.14.1 with this fix as it is causing us production issues. If that's a big deal I can manually apply the patch.
Will do. The next release is 25th this month, which is 2 weeks later, a bit too long to wait.
Fixed in v1.14.1.