googleapis / googleapis/google-cloud-java

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

Aperta
#12,555 3 commenti 0 reazioni 1 assegnatario Rivendicata da @BenWhitehead Vedi su GitHub
api: storage priority: p3 type: feature request
Lingua principale
Java
Stelle
2.1k
Fork
1.2k
Merge medio
1g 23h
PR unite (30g)
154

Descrizione

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.

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.