THRIFT-6132: Reset Ruby Header metadata between frames - #3688
Merged
Conversation
Client: rb Co-Authored-By: OpenAI Codex (GPT-5.6) <codex@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ruby
HeaderTransportcurrently preserves key-value headers from a Header frame when the same connection switches to a legacy framed or unframed Binary or Compact message. Applications can therefore observe metadata from an earlier request while processing a later message that did not carry it.Reset read headers at the start of every frame parse, before protocol detection and validation. Legacy protocol switches and malformed following frames now expose an empty header map, while each later valid Header frame exposes only its own metadata.
[skip ci]anywhere in the commit message to free up build resources.