Preserve exception type on BlockingIterable#forEach variants #3154
Conversation
This file contains 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
The previous refactoring wrapped all non-runtime exception into a runtime exception to adhere to the unchecked singature of the method. Turns out, some code on top has been relying on the actual exception (i.e. an IOException) so wrapping, while correct, is not backwards compatible and in this case for us the latter is more important.
idelpivnitskiy
approved these changes
Dec 23, 2024
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.
The previous refactoring (#3128) wrapped all non-runtime exception into a runtime exception to adhere to the unchecked singature of the method. Turns out, some code on top has been relying on the actual exception (i.e. an IOException) so wrapping, while correct, is not backwards compatible and in this case for us the latter is more important.