-
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
Disallow run n and run x as flow names #4526
Disallow run n and run x as flow names #4526
Conversation
b1750d0
to
3690653
Compare
234be0f
to
9123245
Compare
@@ -1311,7 +1311,7 @@ def _parse_src_reg(reg: Path, cur_dir_only: bool = False) -> Tuple[Path, Path]: | |||
return (reg, abs_path) | |||
|
|||
|
|||
def validate_workflow_name(name: str) -> None: | |||
def validate_workflow_name(name: str, runNcheck=False) -> None: |
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.
Why do we need this runNcheck
argument?
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.
Other commands that use validate_workflow_name
can (sometimes should) be passed a name which ends in runN
or runX
:
Consider cylc clean /home/me/cylc-run/my-workflow/runN
. Cylc clean uses validate workflow, and in that case it certainly doesn't want to claim that /home/me/cylc-run/my-workflow/runN
is not valid.
Cylc play is the other use case.
Co-authored-by: Ronnie Dutta <61982285+MetRonnie@users.noreply.github.com>
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.
Thanks @wxtim. I have read and checked out the code and run the tests.
closes #4394 - IMO a single reviewer PR.
Requirements check-list
CONTRIBUTING.md
and added my name as a Code Contributor.setup.py
andconda-environment.yml
.