Repository navigation
document 7209 - removal of graph orphans on reload/restart - #973
oliver-sanders wants to merge 3 commits into
Conversation
Co-authored-by: Oliver Sanders <oliver.sanders@metoffice.gov.uk>
| If dependencies have changed, tasks that were already active will spawn | ||
| children according to their original outputs. Subsequent instances will have | ||
| the new settings. |
There was a problem hiding this comment.
I think this has been wrong for a while now.
hjoliver
left a comment
There was a problem hiding this comment.
Good, just suggested some minor edits for grammar and conciseness.
Co-authored-by: Hilary James Oliver <hilary.j.oliver@gmail.com>
| Active instances of tasks removed from the | ||
| :term:`graph` by restart or reload will now be removed from the workflow | ||
| (i.e, ``cylc remove``). If they have active jobs, they will be | ||
| killed. |
There was a problem hiding this comment.
I would be tempted to align more closely to my suggested changelog entry for the cylc-flow PR
| Active instances of tasks removed from the | |
| :term:`graph` by restart or reload will now be removed from the workflow | |
| (i.e, ``cylc remove``). If they have active jobs, they will be | |
| killed. | |
| When you delete tasks from the :term:`graph` and then reinstall and | |
| reload/restart the workflow, Cylc will now kill and remove any active instances | |
| of those tasks (as ``cylc remove`` would do). |
There was a problem hiding this comment.
The current phrasing is partly my fault, but as it happens I was also considering whether "removed by reload or restart" is potentially confusing.
My variant of this tweak:
| Active instances of tasks removed from the | |
| :term:`graph` by restart or reload will now be removed from the workflow | |
| (i.e, ``cylc remove``). If they have active jobs, they will be | |
| killed. | |
| If you remove tasks from the :term:`graph`, any active instances of those tasks | |
| will be killed and removed from the workflow when you reload or restart. |
| Active instances of tasks removed from the | ||
| graph will be removed (by ``cylc remove``) from the workflow. | ||
| Their active jobs, if they have any, will be killed. |
There was a problem hiding this comment.
| Active instances of tasks removed from the | |
| graph will be removed (by ``cylc remove``) from the workflow. | |
| Their active jobs, if they have any, will be killed. | |
| Active instances of tasks removed from the | |
| graph will be removed from the workflow (just like if you called | |
| ``cylc remove`` on them). | |
| Their active jobs, if they have any, will be killed. |
There was a problem hiding this comment.
Could be phrased as in the change log, now (e.g. "My variant of this tweak:" above).
There was a problem hiding this comment.
(raise a suggestion if you want it changed differently)
There was a problem hiding this comment.
Ok:
| Active instances of tasks removed from the | |
| graph will be removed (by ``cylc remove``) from the workflow. | |
| Their active jobs, if they have any, will be killed. | |
| If you remove tasks from the :term:`graph`, any active instances of those tasks | |
| will be killed and removed from the workflow when you reload or restart. |
| :term:`Parentless` tasks will not be inserted into the workflow automatically | ||
| as there is no upstream task to spawn them, so must be inserted manually. |
There was a problem hiding this comment.
Tempted to avoid the term "insert" so as not to encourage long-standing Cylc 7 users to keep outdated mental model in their heads!
| :term:`Parentless` tasks will not be inserted into the workflow automatically | |
| as there is no upstream task to spawn them, so must be inserted manually. | |
| :term:`Parentless` tasks will not appear in the workflow automatically | |
| as there is no upstream task to spawn them, so must be dealt with manually. |
| Active instances of tasks removed from the | ||
| graph will be removed (by ``cylc remove``) from the workflow. | ||
| Their active jobs, if they have any, will be killed. | ||
|
|
There was a problem hiding this comment.
Ooh, might be good to note this?
| .. note:: | |
| Cylc cannot track when you rename a task; it will consider the change | |
| as removal of one task and addition of another. | |
document cylc/cylc-flow#7209
Requirements check-list
CONTRIBUTING.mdand added my name as a Code Contributor.