-
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
Configure dummy pipeline to emit warnings/errors #984
Conversation
I'm going to leave approval in case @fengelniederhammer has any thoughts since he's been the driving force behind this dummy pipeline. |
kubernetes/loculus/templates/loculus-preprocessing-deployment.yaml
Outdated
Show resolved
Hide resolved
39b4af3
to
ca9c762
Compare
6beff4a
to
a116223
Compare
@fengelniederhammer I've addressed your feedback - the errors/warnings are now deterministic (always on) by default but can be made random with a |
kubernetes/loculus/templates/loculus-preprocessing-deployment.yaml
Outdated
Show resolved
Hide resolved
Refactor deployment template to remove server env check
f44dfdd
to
1641394
Compare
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.
Thanks, looks good 👍
This PR configures the dummy preprocessing pipeline to emit errors and warnings when deployed on the server.
E2E is not touched to simplify testing. But the ability to have submissions with errors/warnings is essential to demonstrate/test how our frontend handles them.
For example, I noticed that the new submission review page shows the "release" paperplane icon even for sequences with errors. This wasn't easy to test before the code changes here.
I also add a
--dry-run
feature to./deploy.py
to make it easiert to see what commands it executes. This helped me understand the precise configuration used by E2E testing.Preview: https://dummy-warn-error.loculus.org
Resolves #983
Screenshots showing that errors now occur: