Improve user-facing network error message when requesting indexes #8738
Conversation
uranusjr
changed the title
There are way too many exceptions that say "connection". Rename this class so it's clear the exception is generated from an HTTP response, not during connection.
uranusjr
force-pushed
the
retry-network-error
branch
from
95b48d0 to
0189f48
Compare
This creates a message that the user can see. We will flesh out this message to include better explainations for each situation in later commits.
uranusjr
force-pushed
the
retry-network-error
branch
2 times, most recently
from
8ce9a12 to
e5ab371
Compare
This may help us provide better error messages if needed, instead of being stuck with an eagerly-rendered string.
uranusjr
force-pushed
the
retry-network-error
branch
from
e5ab371 to
db080bd
Compare
This allows us to output a more specific error message to help users in common cases.
uranusjr
force-pushed
the
retry-network-error
branch
from
db080bd to
f3a04ac
Compare
|
Hello! I am an automated bot and I have noticed that this pull request is not currently able to be merged. If you are able to either merge the |
|
@uranusjr Is this something you'd be working on in the near future? |
|
It depends on your definition of near 😛 I worked on the user-facing message for this briefly with a sprint participant, but this will likely not progress very quickly in any case (the implementation is tedious and requires a lot of effor to untangle). I’d welcome anyone to to take over this if they have the time. |
|
Closing this out, since this is significantly out of date. I might end up tackling this in #10421. |
Fix #8641.