-
Notifications
You must be signed in to change notification settings - Fork 25.3k
Refactor gcp-fixture multipart parser #125828
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
2fb738d
refactor gcp-fixture multipart parser
mhl-b 28d4481
remove ring-buffer
mhl-b 4ef1236
naming
mhl-b 5105d4c
Merge remote-tracking branch 'upstream/main' into gcp-fixture-multipa…
mhl-b 0dfddd6
add tests
mhl-b 1008194
Merge branch 'main' into gcp-fixture-multipart-refactor
mhl-b 771e069
Merge remote-tracking branch 'upstream/main' into gcp-fixture-multipa…
mhl-b 4eb8b23
merge main
mhl-b 3381864
generic multipart parser
mhl-b f8eb315
Merge branch 'gcp-fixture-multipart-refactor' of github.com:mhl-b/ela…
mhl-b f3210e4
[CI] Auto commit changes from spotless
elasticsearchmachine 9714b32
exceptions
mhl-b 019a04f
Merge branch 'gcp-fixture-multipart-refactor' of github.com:mhl-b/ela…
mhl-b b4869f5
test zero-sized blob
mhl-b 47912f5
sanitize content
mhl-b 8de1110
Merge branch 'main' into gcp-fixture-multipart-refactor
mhl-b 1505b48
Merge remote-tracking branch 'upstream/main' into gcp-fixture-multipa…
mhl-b b7ef093
Merge branch 'gcp-fixture-multipart-refactor' of github.com:mhl-b/ela…
mhl-b 905620d
random multipart boundary
mhl-b efda0e7
cleanup
mhl-b 797d27d
Merge branch 'main' into gcp-fixture-multipart-refactor
mhl-b File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like to keep the behaviour where an invalid body causes a test failure rather than just an
IllegalStateException
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Throw AssertionError errors from the MultipartUpload.parseBody now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was sort of hoping to see tests that ensured that this kind of malformed body would throw an IAE from the parser. Throwing
AssertionError
from the parser itself basically means you can only test the happy path (or else catchAssertionError
in tests which is best avoided if possible).