-
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
Bypass LIMS for delivery report #3153
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.
Great cleanup, 👍
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.
Looks great 💯
…to skip-lims-report
Quality Gate passedIssues Measures |
Deployed |
Description
The goal is to avoid the delivery report crashing due to samples not being present in LIMS (HTTP exception). While the report creation will still fail, it'll be possible to work around it with the
--force flag
, including empty data for the application info, methods, and metrics for Rnafusion.I've also moved some methods from the report api to the analysis api since I've seen some duplication that could be introduced here: #3112
Added
Changed
How to prepare for test
us
paxa
Tests
Generate delivery report for a sample that's not in LIMS:
With the current master branch (exception raised and not captured, not possible to bypass generation with
--force
):With this branch (generation fails gracefully, logging the missing report data.
--force
flag generates a report with empty data):Balsamic
delivery-reportRnafusion
delivery-reportMIP-DNA
delivery-reportReview
Thanks for filling in who performed the code review and the test!
This version is a
Implementation Plan