You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cylc currently provides two mechanisms for clock-limiting tasks:
[xtriggers]wall_clock
The new approach, the @clock trigger is used in the graph like regular dependencies. This has the advantage of transparency.
[special tasks]clock-trigger
The old approach. marked as deprecated but still widely used. Allows listing of tasks which should be clock-limited.
We will presumably look to retire the old clock-triggers at some point after Cylc 7 back-compat mode is dropped, but this is still a way off. This means we need to keep these triggers working for the near future (which is something else to go wrong #5217).
Suggest converting clock-triggers to xtriggers at configure time. I think we can do this fairly easily at configure time something along the lines of:
This way the old triggers will continue working under the new logic allowing us to retire this feature early. The old triggers will also become visible in the UI once xtrigger support is added.
Pull requests welcome!
The text was updated successfully, but these errors were encountered:
Cylc currently provides two mechanisms for clock-limiting tasks:
The new approach, the
@clock
trigger is used in the graph like regular dependencies. This has the advantage of transparency.The old approach. marked as deprecated but still widely used. Allows listing of tasks which should be clock-limited.
We will presumably look to retire the old
clock-triggers
at some point after Cylc 7 back-compat mode is dropped, but this is still a way off. This means we need to keep these triggers working for the near future (which is something else to go wrong #5217).Suggest converting clock-triggers to xtriggers at configure time. I think we can do this fairly easily at configure time something along the lines of:
This way the old triggers will continue working under the new logic allowing us to retire this feature early. The old triggers will also become visible in the UI once xtrigger support is added.
Pull requests welcome!
The text was updated successfully, but these errors were encountered: