You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Closed pull request #854 seems to be causing an issue with running the Vale prose linter. Here is an example linting from stdin:
$ lbv "bare metal is the way to go"
E201 Invalid value [/vale_app/styles/RedHat/TermsErrors.yml:22:4]:
21 "(?<!self-)hosted engine|hosted-engine": self-hosted engine
22* "bare metal( clusters?| compute| configuration| controls?| environments?| equipment| events?| hardware| hosts?| infrastructure| installations?| installers?| machines?| media| nodes?| provisioning| servers?| workers?)": bare-metal $1
23 "bare-metal(?! clusters?| compute| configuration| controls?| environments?| equipment| events?| hardware| hosts?| infrastructure| installations?| installers?| machines?| media| nodes?| provisioning| servers?| workers?)": bare metal
24 "[bB]asic [aA]uth": Basic HTTP authentication|Basic authentication
capture group not supported; use '(?:' instead of '('
Execution stopped with code 1.
Here, lbv is a local alias for running Vale from a Docker container. I rebuilt this container today after the pull request was committed and got this error. If I take the container's "sync" step back to a locally cached version from before the pull request, the error goes away. The sync step I believe "grabs" packaged style rules. I don't know if that is significant here or not.
Hope this report is helpful and that I have provided enough details. Happy to do more if needed.
The text was updated successfully, but these errors were encountered:
Ah! Indeed, that is the problem for me. My container was based on an older Vale version (jdkato/vale:v2.x.x). Thank you for the reply and apologies for the noise.
Closed pull request #854 seems to be causing an issue with running the Vale prose linter. Here is an example linting from stdin:
Here,
lbv
is a local alias for running Vale from a Docker container. I rebuilt this container today after the pull request was committed and got this error. If I take the container's "sync" step back to a locally cached version from before the pull request, the error goes away. The sync step I believe "grabs" packaged style rules. I don't know if that is significant here or not.Hope this report is helpful and that I have provided enough details. Happy to do more if needed.
The text was updated successfully, but these errors were encountered: