-
Notifications
You must be signed in to change notification settings - Fork 94
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 expire triggers. #5412
Fix expire triggers. #5412
Conversation
a21b13d
to
22def64
Compare
Update change log. Add new func test.
22def64
to
0f1894b
Compare
Converted back to draft temporarily, in light of today's project meeting. I think have have nailed the expire stall/no-stall situation, and how expire relates to success (etc.) optionality. But I ran out of time to write it up this afternoon. Stand by ... |
PR blocked pending resolution of the We will still need the ability to trigger tasks off of task expiry, but I have argued against continuing to treat |
if output == TASK_OUTPUT_EXPIRED and not optional: | ||
raise GraphParseError( | ||
f"Expired-output {name}:{output} must be optional") | ||
|
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.
This is now covered by the optional outputs stuff.
if output == TASK_OUTPUT_EXPIRED and not optional: | |
raise GraphParseError( | |
f"Expired-output {name}:{output} must be optional") |
Closing as superseded by #5658 |
And require
?
(optional) on all expire triggers.Check List
CONTRIBUTING.md
and added my name as a Code Contributor.setup.cfg
(andconda-environment.yml
if present).CHANGES.md
entry included if this is a change that can affect users?.?.x
branch.