Skip to content
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

Handle Aspen connection failures more gracefully #189

Closed
psvenk opened this issue Nov 28, 2020 · 2 comments
Closed

Handle Aspen connection failures more gracefully #189

psvenk opened this issue Nov 28, 2020 · 2 comments
Labels
backend Suspected problem with backend (server or scraper) enhancement New feature or request frontend Suspected problem with frontend (client-side code in public directory)

Comments

@psvenk
Copy link
Member

psvenk commented Nov 28, 2020

When connections to Aspen fail (e.g., because Aspen is down), Aspine's behavior is currently an infinite loading circle with a technical error description on the backend but no indication to the user of what is going on. We should use a try/catch or something similar on the backend to communicate such a situation to the frontend, which should then display an error message along the lines of "Aspen could not be reached" with a suggestion to try again.

@psvenk psvenk added backend Suspected problem with backend (server or scraper) enhancement New feature or request frontend Suspected problem with frontend (client-side code in public directory) on hold Will not be worked on until further notice labels Nov 29, 2020
@psvenk
Copy link
Member Author

psvenk commented Nov 29, 2020

On hold until #184.

@psvenk psvenk removed the on hold Will not be worked on until further notice label Feb 16, 2021
@psvenk
Copy link
Member Author

psvenk commented Apr 21, 2021

Fixed in #278.

@psvenk psvenk closed this as completed Apr 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Suspected problem with backend (server or scraper) enhancement New feature or request frontend Suspected problem with frontend (client-side code in public directory)
Projects
None yet
Development

No branches or pull requests

1 participant