Remove H3 frame sequence number tracking#11632
Conversation
JosiahWI
left a comment
There was a problem hiding this comment.
Nice cleanup! Let's not free the buffer in the test twice, though.
|
The tests for |
|
@JosiahWI Do you want to gather information before I push a new commit and trigger new jenkins jobs? |
|
@maskit I'm not sure I can gather anything useful from the job. I don't know how to get a stack trace. I suspect it's a race condition, but I don't know how it's related to the test or whether it's related at all. The valgrind report on my OpenSUSE container comes up completely clean. |
|
Ok, I'l rerun the job without pushing a new commit to see if it fails again. I'll push a new commit if it doesn't fail. |
|
[approve ci centos] |
|
All tests passed this time. |
|
|
[approve ci rocky] |
|
Cherry-picked to v10.0.x |
* Remove H3 frame sequence number tracking * Remove redundant free_MIOBuffer call (cherry picked from commit aaff5a9)
This closes #11622.
The frame sequence was only used for
ProtocolEnforcerand there is no other use case planned. This PR removes the sequence number tracking, which was reset on every READ_READY, and use a private flag in ProtocolEnforcer to do the same check for SETTINGS frame.