-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: Metadata API Request Error Handling #3812
Comments
richardjennings-occrp
added
bug
Things that should work, but don’t
triage
These issues need to be reviewed by the Aleph team
labels
Jul 16, 2024
I've created a new pull request: #3813 |
catileptic
added
Low
issue that could require attention
and removed
triage
These issues need to be reviewed by the Aleph team
labels
Jul 30, 2024
tillprochaska
added a commit
that referenced
this issue
Oct 22, 2024
Fixes #3812. Previously, the UI would retry the metadata request indefinitely and without a delay. Now, if the metadata request fails, an error message and a button to reload the page are displayed. I haven’t implemented automatic retries with back-offs for now, as this adds complexity and I’m not sure it’s necessary.
tillprochaska
added a commit
that referenced
this issue
Oct 22, 2024
Fixes #3812. Previously, the UI would retry the metadata request indefinitely and without a delay. Now, if the metadata request fails, an error message and a button to reload the page are displayed. I haven’t implemented automatic retries with back-offs for now, as this adds complexity and I’m not sure it’s necessary.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The UI does not utilise a retry limit or backoff for retrying Metadata API requests when the API is not available.
To Reproduce
Steps to reproduce the behavior:
Expected behaviour
The UI should retry a number of times delayed by some form of backoff.
If a maximum number of retries is reached there should be some button to try again (refresh).
Aleph version
Current
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: