-
Notifications
You must be signed in to change notification settings - Fork 2
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
fix(website): Handle 503 error from SILO #1132
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm apart from linting
509a2b7
to
c1acaa7
Compare
I guess we need to increase maxNumberOfRetries or add some back off time |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Errors are handled but E2E still fails - but I guess this is expected?
I don't know why this happens. Locally it works... |
See GenSpectrum/LAPIS-SILO#295 SILO throws an error now when it did not load a database yet.
c1acaa7
to
0323b2f
Compare
IIUC, Silo is up per the "pods ready step" - strange Seems to be running but somehow not initialized |
Seems to be OK now :) |
preview URL: https://lapis503error.loculus.org/
Summary
See GenSpectrum/LAPIS-SILO#295. SILO throws an error now when it did not load a database yet.
PR Checklist
[ ] All necessary documentation has been adapted.[ ] The implemented feature is covered by an appropriate test.