-
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
Reconstruct xtriggers at reload time. #6263
Conversation
This looks good to me. Stuck together an integration test to help bump this along: hjoliver#58 |
Thanks (sorry I let this one languish unfinished!) |
(no probs, just running through bugs, working out what I can help push forward) |
(Just working on the one failing integration test ....should be an easy fix) |
d79c63c
to
e93acba
Compare
Somewhat surprisingly, that revealed a problem, now fixed - see the new xtrigger |
Tentatively pushing forward to 8.3.6 since it's ready to go now. |
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, much needed!
Tested it locally with a workflow_state
xtrigger.. Found working 🍻
Co-authored-by: Oliver Sanders <oliver.sanders@metoffice.gov.uk>
Close #6259
Close #6260
User-defined xtriggers (including wall-clock) need to be reconstructed after reload (to pick up changes), but auto-defined ones (retries) must be retained.
Check List
CONTRIBUTING.md
and added my name as a Code Contributor.setup.cfg
(andconda-environment.yml
if present).?.?.x
branch.