Keep raw headers around to preserve ordering and unknown extra headers #1579
Conversation
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.
WIP fix for #1578.
Preserves extra headers for a very narrow usecase - re-encoding them exactly as they were in the original object. This allows for the successful PGP validation of commits containing such extra headers, such as jj's
change-id. A test for this specific case is provided, and all existing tests currently pass.There's still some "quirky" behavior around the presence of the raw headers causing the stuctured fields to be ignored for encoding. This probably needs to be resolved as it can result in some surprising behavior (see incidental test changes where I had to clear the
headersRawfield to get them to pass). Not sure how exactly to present that to the user though.