googleapis / googleapis/google-cloud-java

[java-storage-nio] Improve error messages in StorageExceptions

Ouverte
#12,555 3 commentaires 0 réactions 1 personne assignée Réclamée par @BenWhitehead Voir sur GitHub
api: storage priority: p3 type: feature request
Langage dominant
Java
Étoiles
2.1k
Forks
1.2k
Merge moyen
1 j 23 h
PR mergées (30 j)
154

Description

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:
```
{
"code" : 404,
"errors" : [ {
"domain" : "global",
"message" : "The specified bucket does not exist.",
"reason" : "notFound"
}
```
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"
```
{
"code" : 404,
"errors" : [ {
"domain" : "global",
"message" : "The specified bucket does not exist. (bucketImisspelled)"
"reason" : "notFound"
} ],
```
**Describe alternatives you've considered**
Other options would be to include an additional "details" field if the message has to always be the same.

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.