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

Better frontend error page when backend is down #344

Open
ianroberts opened this issue Apr 17, 2023 · 0 comments
Open

Better frontend error page when backend is down #344

ianroberts opened this issue Apr 17, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@ianroberts
Copy link
Member

Current behaviour

Related to #343 - when backend is unavailable for any reason the frontend index page loads "successfully" from an HTTP perspective (i.e. the HTML page and all the associated css and JS files load correctly with 200 response codes) but when the "initizlise" RPC call fails you are left with a completely blank browser window and no error message. Navbar and footer do not appear.

You can test this by running just the frontend development server (npm run serve:frontend) without also running the backend - in this case you get the csrf_token bit of template from the index.html but nothing else.

Expected behaviour

The navbar and footer should still render correctly as it would if no user were logged in, but the page should display a sensible warning that GATE Teamware is temporarily unavailable.

@ianroberts ianroberts added the bug Something isn't working label Apr 17, 2023
@twinkarma twinkarma self-assigned this May 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants