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 message and : inconsistencies #6006
Comments
I can't reproduce the error in your first example Note because there is a colon after the first word The rule is you can use any number of colons after the first The reason for supporting The validation step that enforces only allowing colons if there is one at the end of the first word was an attempt to prevent a message like |
Perhaps the instructions weren't quite right.
If I do
versus
flow.cylc for the above outputs
That is using |
That's fine, it's easy to work around in our case, I just raise things when I see them. Based on my example above, I do think this should be classified as a bug (and could be better) - just a low priority bug. |
Ah, your real example fails validation because |
Description
In Cylc7 at least, I had a task which did something like
cylc message -p CUSTOM "abc::efg::hij::sdf"
. In Cylc8, that produces an error- cannot contain
:unless it occurs at the end of the first word
. Changing the above tocylc message "CUSTOM:abc::efg::hij::sdf"
does what was expected. However, doing this goes against the error message as there are still multiple:
in there, so I'm a bit confused if itshould
work?Doing similar different from CLI, outside of a workflow and you get different results.
In this case, there is no error message, it just strips out the first colon and makes
hel
the severity, ignoring the-p CUSTOM
which was defined.Reproducible Example
Do above commands in a task.
Expected Behaviour
Several potential things
-p
or equivalent flag is passed, then the:
check should not be performed as the severity is defined by the CLI already?:
perhaps?CUSTOM:a::b::c
shouldn't work according to the error message)The text was updated successfully, but these errors were encountered: