Hilary James Oliver
Hilary James Oliver
Parent-less tasks have no parents to spawn them "on demand", so we have to auto-spawn them: ``` P1 = "foo" # foo must be auto-spawned ``` To stick within the...
Placeholder for possible changes to the initial SoD implementation as discussed in the [SoD proposal](https://cylc.github.io/cylc-admin/proposal-spawn-on-d.html), e.g.: - [ ] try to avoid all remaining iteration over task proxies - [...
Runahead limiting was originally designed to limit the performance impact of task pool bloat caused by spread over cycles, in the old spawn-on-submit system where the intermediate cycles would fill...
Tasks waiting on any kind of external triggers currently appear as "waiting" in the scheduler task pool, and are consequently seen as n=0 active tasks in the data store. However,...
We need to analyze partially satisfied prerequisites before using them as an excuse to stall. If some correspond to optional outputs, then partial satisfaction may not indicate an error condition....
From @oliver-sanders > - We should develop the ability to upgrade workflows via the auto-restart mechanism (basically just auto-restart as usual but change the value of CYLC_VERSION / CYLC_ENV_NAME, and...
While testing #6046 I noticed we can assign the same output message to different triggers: ```ini [scheduling] [[graph]] R1 = "foo:x? & foo:y? => bar" [runtime] [[bar]] [[foo]] script =...
```ini [scheduling] initial cycle point = now [[graph]] PT1M = "foo" [runtime] [[foo]] ``` 1. `cylc vip bug` 2. `cylc stop bug` 3. (add a comment to `flow.cylc`) 4. `cylc...
A forum post has revealed that EmPy 3 doesn't play well with scheduler daemonization: https://cylc.discourse.group/t/empy-import-shell-environment-variables/985/1 If I simply add `#!EmPy` to a `flow.cylc`, the workflow runs fine but: - I...
Close #5963 I've added the "question" label because there's some disagreement on the issue itself: @oliver-sanders has argued that manual triggering (i.e., with immediate effect) should only be allowed with...