-
Notifications
You must be signed in to change notification settings - Fork 106
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
[#636] Add special case handling of cron workflow status #637
Conversation
Signed-off-by: Flaviu Vadan <flaviuvadan@gmail.com>
e47312f
to
255a9f2
Compare
Codecov Report
@@ Coverage Diff @@
## main #637 +/- ##
=====================================
Coverage 72.7% 72.7%
=====================================
Files 42 42
Lines 2937 2937
Branches 572 572
=====================================
Hits 2137 2137
Misses 648 648
Partials 152 152 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Signed-off-by: Elliot Gunton <elliotgunton@gmail.com>
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
Seems I messed up the DCO check, sorry 😓 github UI wouldn't let me change the email to sign off 🙄 |
Signed-off-by: Flaviu Vadan <flaviuvadan@gmail.com>
Pull Request Checklist
Description of PR
Currently, the Argo server does not return cron workflow statuses when a users' cron workflow does not execute immediately post submission. So,
None
s are returned for the independent fields of the cron workflow status. While the status is indeed optional, the fields are not! This PR adds a special case for handling this in the service. I am not sure whether this is a feature or a bug upstream in Argo Workflows.CC: @iameskild I was able to run your example using the fix in this PR!