Ensure that TestRecordingMismatchException doesn't exhaust default header size limits
#9662
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
…f the TestRecordingMismatchException. That one has the potential to blow up the default header size limit
benbp
approved these changes
Jan 17, 2025
Closed
swathipil
pushed a commit
to swathipil/azure-sdk-tools
that referenced
this pull request
Feb 4, 2025
…header size limits (Azure#9662) * limit the size of the Remaining Entries output in the actual header of a TestRecordingMismatch exception. The message content's potential size could break the default limits on header size * update tests to reflect new exception output
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Resolving an issue brought up in the Test-Proxy Teams channel