-
Notifications
You must be signed in to change notification settings - Fork 93
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
handle version change on restart (resume) #4039
Comments
All good, except:
Not sure about a total block. How about prompt the user for confirmation but with a sterner warning of possible consequences. |
Possibly there could be |
That's what the "(require an override to bypass)" was meant to mean, some sort of |
|
Re worded the proposal to avoid confusion. |
* Closes cylc#4039 * When restarting a workflow, check the version it previously ran under against the current version in order to determine if the change is sensible. * Restart normally if the restart would: * Not change the version. * Increase the maintenance number. * Prompt (override with --yes) for confirmation if the restart would: * Reduce the maintenance number. * Increase the minor number. * Exit with nasty error (override with --force or --yes --yes?) if the restart would: * Decrease the minor number. * Change the major number. * This also moves the pre-existing workflow DB check from post-detatch to pre-detach.
* Closes cylc#4039 * When restarting a workflow, check the version it previously ran under against the current version in order to determine if the change is sensible. * Restart normally if the restart would: * Not change the version. * Increase the maintenance number. * Prompt (override with --yes) for confirmation if the restart would: * Reduce the maintenance number. * Increase the minor number. * Exit with nasty error (override with --force or --yes --yes?) if the restart would: * Decrease the minor number. * Change the major number. * This also moves the pre-existing workflow DB check from post-detatch to pre-detach.
* Closes cylc#4039 * When restarting a workflow, check the version it previously ran under against the current version in order to determine if the change is sensible. * Restart normally if the restart would: * Not change the version. * Increase the maintenance number. * Prompt (override with --yes) for confirmation if the restart would: * Reduce the maintenance number. * Increase the minor number. * Exit with nasty error (override with --force or --yes --yes?) if the restart would: * Decrease the minor number. * Change the major number. * This also moves the pre-existing workflow DB check from post-detatch to pre-detach.
* Closes cylc#4039 * When restarting a workflow, check the version it previously ran under against the current version in order to determine if the change is sensible. * Restart normally if the restart would: * Not change the version. * Increase the maintenance number. * Prompt (override with --yes) for confirmation if the restart would: * Reduce the maintenance number. * Increase the minor number. * Exit with nasty error (override with --force or --yes --yes?) if the restart would: * Decrease the minor number. * Change the major number. * This also moves the pre-existing workflow DB check from post-detatch to pre-detach.
* Closes cylc#4039 * When restarting a workflow, check the version it previously ran under against the current version in order to determine if the change is sensible. * Restart normally if the restart would: * Not change the version. * Increase the maintenance number. * Prompt (override with --yes) for confirmation if the restart would: * Reduce the maintenance number. * Increase the minor number. * Exit with nasty error (override with --force or --yes --yes?) if the restart would: * Decrease the minor number. * Change the major number. * This also moves the pre-existing workflow DB check from post-detatch to pre-detach.
* Closes cylc#4039 * When restarting a workflow, check the version it previously ran under against the current version in order to determine if the change is sensible. * Restart normally if the restart would: * Not change the version. * Increase the maintenance number. * Prompt (override with --yes) for confirmation if the restart would: * Reduce the maintenance number. * Increase the minor number. * Exit with nasty error (override with --force or --yes --yes?) if the restart would: * Decrease the minor number. * Change the major number. * This also moves the pre-existing workflow DB check from post-detatch to pre-detach.
* Closes cylc#4039 * When restarting a workflow, check the version it previously ran under against the current version in order to determine if the change is sensible. * Restart normally if the restart would: * Not change the version. * Increase the maintenance number. * Prompt (override with --yes) for confirmation if the restart would: * Reduce the maintenance number. * Increase the minor number. * Exit with nasty error (override with --force or --yes --yes?) if the restart would: * Decrease the minor number. * Change the major number. * This also moves the pre-existing workflow DB check from post-detatch to pre-detach.
* Closes cylc#4039 * When restarting a workflow, check the version it previously ran under against the current version in order to determine if the change is sensible. * Restart normally if the restart would: * Not change the version. * Increase the maintenance number. * Prompt (override with --yes) for confirmation if the restart would: * Reduce the maintenance number. * Increase the minor number. * Exit with nasty error (override with --force or --yes --yes?) if the restart would: * Decrease the minor number. * Change the major number. * This also moves the pre-existing workflow DB check from post-detatch to pre-detach.
cylc restart
(soon to be renamedcylc play
) currently [8.0a3.dev] restarts a workflow using whatever version of Cylc is selected by the current environment.For many this is a departure from
rose suite-restart
which sets theCYLC_VERSION
to the version of the previous run. This old behaviour has an upside and a downside in that whist it ensures a compatible Cylc version is selected, it prohibits restarts from benefiting from bug fixes in maintainance releases.Proposal:
--yes
) for confirmation if the restart would:--force
or--yes --yes
?) if the restart would:Thoughts?
Pull requests welcome!
The text was updated successfully, but these errors were encountered: