Hello,
This question (bug report?) pertains to cylc 8.4.1. The issue is that cylc validate
, as well as actual workflow runs, fail when future dependencies are used at time points close to year zero.
As an example, the following graph works without issues:
[scheduler]
allow implicit tasks = True
[scheduling]
initial cycle point = 0001
final cycle point = 0010
[[graph]]
P1Y = foo
P1Y = foo[+P1Y] => bar
But if the last line is changed to P1Y = foo[+P2Y] => bar
, then cylc validate .
fails with:
WorkflowConfigError: failed to instantiate task foo: Cannot dump TimePoint year: -1 not in bounds 0 to 9999.
Similarly, if the last line is changed to P1Y = foo[+P3Y] => bar
, then the error becomes:
WorkflowConfigError: failed to instantiate task foo: Cannot dump TimePoint year: -2 not in bounds 0 to 9999.
In general, the number in the message always equals initial cycle point
minus the interval given for the future foo
dependency.
So my question is: is this a bug, or user error?
Thank you!