Hilary James Oliver
Hilary James Oliver
Supersedes: #5763, #5695 See also: #5752, #5416, #5677 ### TODO: * [ ] hold * [ ] set * [ ] trigger * [ ] release * [ ] kill...
The release command doesn't need to do generic matching of future tasks, because we can only release tasks that are already held - and those are all recorded in the...
Currently the hold/release commands both work like this: - glob pattern args: - find matching task proxies in the task pool - add/remove their IDs from the tasks-to-hold list -...
The workflow-state xtrigger polls until a task in another workflow achieves a status or generates an output. #5809 adds flow-specificity (for the upstream workflow) but defaults to flow=1 as a...
Close #5572 (and extends it to push ext-triggers as well) - If a task has unsatisfied prerequisites, `cylc trigger` will satisfy them - Otherwise, it will satisfy any unsatisfied xtriggers...
Zero-th level workaround for #5437 (We still need to optimize the problematic code, but this approach might be useful in the interim, and possibly in the long run as well)....
We have (or soon will have, in new optional outputs docs etc.) a bunch of examples with triggers that spawn child tasks with the same name as the trigger: ```ini...
Description below pasted verbatim from Element chat room (@oliver-sanders please edit if desired). See also comments on #3766 and #3595 which this issue supersedes. See also: * #4981 * #3766...
During SoD implementation I removed all `cylc insert` functional tests, because that command is now kaput. However, `cylc trigger` now does auto-insertion, and the same rules apply about what can...
Post SoD we could easily do event-driven triggering (like we already do for event-driven finished-task removal, for instance): when a parent-task output is completed and the dependent child spawned, immediately...