1.x: fix using() resource cleanup when factory throws or being non-eager #3922
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
| Exceptions.throwIfFatal(e); | ||
| Exceptions.throwIfFatal(disposeError); | ||
| if (disposeError != null) { | ||
| subscriber.onError(new CompositeException(Arrays.asList(e, disposeError))); |
There was a problem hiding this comment.
CompositeException accepts varargs right?
|
Changes applied. |
|
👍 |
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 operator
usingdidn't call the resource cleanup code if theobservableFactory.call()code crashed. In addition, a non-eager using didn't call the resource cleanup if one subscribed withunsafeSubscribeor the subscription to the generatedObservablecrashed.Related: #3921