Improve error messages in StorageExceptions #861
Labels
api: storage
Issues related to the googleapis/java-storage-nio API.
priority: p3
Desirable enhancement or fix. May not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
I know that the messages in StorageExceptions come from some storage service that isn't part of this project, but I'm not sure where to make this request otherwise.
Is your feature request related to a problem? Please describe.
StorageExceptions are always extremely vague about the exact details of what caused the problem. They don't include the specific strings that were invalid. This can make debugging tricky when there are multiple potential connections that could have failed, or if something in the user code that generates a Path is generating incorrect ones.
For example, they'll include information like the following:
It would be much more useful if in this case they included what the bucket name was.
Describe the solution you'd like
Include the specific problem in the message.
For instance if the bad bucket name was "bucketImisspelled"
Describe alternatives you've considered
Other options would be to include an additional "details" field if the message has to always be the same.
The text was updated successfully, but these errors were encountered: