Closed dwsutherland closed 4 weeks ago
Solution is probably to spawn next instance on perhaps any use of set
on the task.. As if the xtrigger was satisfied and the task produced that output.. Being parentless means setting prerequisites is irrelevant, i.e. this graph:
[[graph]]
T-00 = """
@clock_P5Y => a
"""
T01, T03, T05, T07, T09, T11, T13, T15, T17, T19, T21, T23 = """
@wall_clock => z
z => a => b
"""
Will remove the even hours, but the odd hour a
s are spawned by z
Fix up: https://github.com/cylc/cylc-flow/pull/6448
An easier workflow to visualize is:
[scheduler]
cycle point format = CCYYMMDDThh
allow implicit tasks = True
[scheduling]
initial cycle point = 20241017T22
[[xtriggers]]
clock_P5Y = wall_clock(offset=P5Y):PT20S
[[graph]]
T-00 = """
@clock_P5Y => a => b
b[-PT1H] => b
"""
[runtime]
[[root]]
script = sleep $((1 + $RANDOM % 10))
w/o this change the workflow shuts down when set
ting a
as above.. with this change b
kicks off and a
is spawned forward.
Description
When setting the outputs on a parentless sequential xtriggered task, the next occurrence is not spawned.
Reproducible Example
Take this workflow, whose task is waiting on and xtrigger:
if you use
cylc set
ona
, the task will disappear and workflow shutdown:Expected Behaviour
The task should be spawned into the future/next-occurrence, as if the xtrigger was satisfied.