Fix: StorageInputStream read methods hide root cause exception when stream is faulted #28638
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.
Description
The method checkStreamState() for faulty stream hides the wrapped error cause because only the error message is given to the new RuntimeException. It is then not possible to properly react on an reading error (a proper reaction is required e.g. in the case of BlobStorageException, BlobErrorCode.CONDITION_NOT_MET).
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines