-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reload and restart - smart insertion of new tasks #774
Comments
@dpmatthews wants to have a think and comment on what the best way to implement this may be. |
Missed this one from the email chain as an option: "another option could be to choose the first instance with upstream dependencies not yet satisfied, or the instance just prior to that - and trigger it immediately in case its upstream dependencies had been cleaned up already." - @hjoliver |
I assume the default will remain not to insert new tasks. |
Worth doing - some users do seem to find the lack of new task auto-insertion confusing. |
[meeting] we agreed: find earliest instance of an unsatisfied task that depends on a new task, and insert there. |
[meeting] A robust, reliable solution that works for all edge cases is a major challenge. A solution which fails to handle these edge cases properly risks generating a false sense of security. Once we move to a spawn-on-demmand model for the task pool, auto-insert on reload should become somewhat easier. |
To be closed with or after #987 |
So very happy to close this, I can finally delete my failed attempts. |
Result of an email conversation between myself, @hjoliver and @dpmatthews.
It would be useful to have cylc perform a smart insertion of new tasks on performing a reload.
Options could include:
There may be a challenge with determining what to do about purged tasks and whether they are "new", depending on how the suite tracks those operations across reloads.
The text was updated successfully, but these errors were encountered: