-
Notifications
You must be signed in to change notification settings - Fork 32
🎨 Check study and solver job status before returning output #8511
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
🎨 Check study and solver job status before returning output #8511
Conversation
|
@sanderegg if you could check carefully if this makes sense. Imo we should not return an output if the job is not done, but maybe you're aware of some tools depending on this? |
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.
thx. I highly recommend adding test coverage on these error scenarios
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #8511 +/- ##
===========================================
- Coverage 86.28% 68.95% -17.33%
===========================================
Files 1931 905 -1026
Lines 75777 40157 -35620
Branches 1343 175 -1168
===========================================
- Hits 65382 27690 -37692
- Misses 10007 12410 +2403
+ Partials 388 57 -331
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
🧪 CI InsightsHere's what we observed from your CI run for 6991c0d. ✅ Passed Jobs With Interesting Signals
|
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.
seems good
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.
Cool, thanks!
services/api-server/src/simcore_service_api_server/exceptions/backend_errors.py
Show resolved
Hide resolved
|
@mergify queue |
🟠 Waiting for conditions to match
|
|
@Mergifyio update |
☑️ Nothing to do, the required conditions are not met
|
|



What do these changes do?
This is part of #8280
The idea is to avoid return 'results' unless a computational project/solver job has succeeded, not having this can lead to returning default/out-of-date results.
The function api already protects against this, but I now added it on the level of solver and study jobs.
Related issue/s
closes #8510
How to test
Check if a failed job returns returns results.
Dev-ops
No changes