Recover exceptions wrapped in same class correctly #17437
Merged
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.
Follow up to #17212
We have added exceptions created by ExceptionUtil.tryWrapInSameClass
methods to the client.
ClientExceptionFactory.createException method was not handling these
exceptions correctly. More specifically, the cause was not set to the
exception if there was no Constructor with cause. This pr adds changes
to mitigate that.
related to #17433