Graduated force-triggering (prereqs, xtriggers, queues). #5585
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Close #5572 (and extends it to push ext-triggers as well)
cylc trigger
will satisfy themThe runahead limit is ignored (i.e., you can trigger tasks beyond the limit).
Reviewers - this is an important part of required intervention capability. E.g. if starting a flow in the middle of a cycle point, we need to be able to set up clock-triggered tasks in subsequent cycles to start checking their clock-triggers now, but not to run immediately.
@dpmatthews - pinging you for a quick look, as the brains behind the xtrigger tweak on this branch.
Check List
CONTRIBUTING.md
and added my name as a Code Contributor.Applied any dependency changes to bothsetup.cfg
(andconda-environment.yml
if present).CHANGES.md
entry included if this is a change that can affect usersCylc-Doc](https://github.com/cylc/cylc-doc) pull request opened if required at cylc/cylc-doc/pull/XXXX.If this is a bug fix, PR should be raised against the relevant?.?.x
branch.