-
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
Add "valid for" states to schema def for cylc set
#6095
Conversation
Dammit, good spot! We should probably have a test to assert this ---- which you've done, great. |
@@ -2103,6 +2103,8 @@ class Meta: | |||
- ``started`` implies ``submitted``. | |||
- ``succeeded`` and ``failed`` imply ``started``. | |||
- custom outputs and ``expired`` do not imply any other outputs. | |||
|
|||
Valid for: paused, running, stopping workflows. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this command is really valid for stopping workflows:
Valid for: paused, running, stopping workflows. | |
Valid for: paused, running. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If waiting for tasks to finish while stopping, is it not valid for users to set task states? I think it can be done from the CLI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ooh, there is a reasonable point there due to this use case:
I need to orphan a "stuck" job submission
Which could otherwise block shutdown.
Ok, leave as is.
Follow-up to #5658
This is needed by the UI to disable mutations that are not valid for the workflow state. At present, "set" is not disabled for stopped workflows as it should be:
Check List
CONTRIBUTING.md
and added my name as a Code Contributor.?.?.x
branch.