-
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
cylc vr
- restart with no changes?
#6261
Comments
Not a big deal since the "workaround" is simply to
|
It is, however, it exits at (2) if there are no changes rather than continuing to (3). Note that you can override this with the |
The purpose of rejecting a reinstallation with no changes is that this likely reflects user error or at least user expectation error (e.g. I forgot to save the file I was editing). So I think this functionality is useful and should remain (we have the However, we could consider changing the WARNING into a prompt e.g:
(note, for the reload case, the command may as well exit at this point, any reload would most likely be pointless) Or we could adapt the WARNING to taste, e.g:
|
Yes, that's exactly the bit I'm complaining about!
That's arguable. On the other side of the coin, as I noted above:
However,
I think that's acceptable. It allows my use case, but highlights the fact that there are no changes to reinstall first. |
OK I just tested that and it works. I was not aware of it, because it doesn't make sense - there's no interactive prompt to say "yes" to!
It would make sense with a new prompt as you suggested above. |
* Closes cylc#6261 * If there are no changes to reinstall AND the workflow is stopped, prompt the user to see whether they want to restart it anyway. * This makes `cylc vr` more useful as the "I want to restart my workflow" command. * But it also ensures that they are aware if no changes are present as they might have forgotten to press save or run the command on the wrong workflow or whatever.
* Closes cylc#6261 * If there are no changes to reinstall AND the workflow is stopped, prompt the user to see whether they want to restart it anyway. * This makes `cylc vr` more useful as the "I want to restart my workflow" command. * But it also ensures that they are aware if no changes are present as they might have forgotten to press save or run the command on the wrong workflow or whatever.
* Closes cylc#6261 * If there are no changes to reinstall AND the workflow is stopped, prompt the user to see whether they want to restart it anyway. * This makes `cylc vr` more useful as the "I want to restart my workflow" command. * But it also ensures that they are aware if no changes are present as they might have forgotten to press save or run the command on the wrong workflow or whatever.
* Closes cylc#6261 * If there are no changes to reinstall AND the workflow is stopped, prompt the user to see whether they want to restart it anyway. * This makes `cylc vr` more useful as the "I want to restart my workflow" command. * But it also ensures that they are aware if no changes are present as they might have forgotten to press save or run the command on the wrong workflow or whatever.
* Closes cylc#6261 * If there are no changes to reinstall AND the workflow is stopped, prompt the user to see whether they want to restart it anyway. * This makes `cylc vr` more useful as the "I want to restart my workflow" command. * But it also ensures that they are aware if no changes are present as they might have forgotten to press save or run the command on the wrong workflow or whatever.
* Closes cylc#6261 * If there are no changes to reinstall AND the workflow is stopped, prompt the user to see whether they want to restart it anyway. * This makes `cylc vr` more useful as the "I want to restart my workflow" command. * But it also ensures that they are aware if no changes are present as they might have forgotten to press save or run the command on the wrong workflow or whatever.
Currently, if the workflow is running and no source changes are detected,
cylc vr
aborts with:That's fine, because a reload would achieve absolutely nothing.
However if the workflow is stopped and no source changes are detected, we get:
IMO the "no play required" bit is wrong, it should restart the workflow. I wouldn't do
cylc vr
if I didn't want the workflow to be running. Maybe I don't recall if if I installed my latest changes already, so I docylc vr
instead ofcylc play
just in case.The text was updated successfully, but these errors were encountered: