-
Notifications
You must be signed in to change notification settings - Fork 205
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
incompatible encoding regexp match
for non-printing characters in place of space
#693
Comments
I cannot replicate this with your inline sample (btw there is a non-printing character between
This is consistent with HEAD, 2.2.1 and the 2.0.0 release, with ruby 2.3.1 via rvm and 2.0.0 via EL7 system ruby. |
Yes, you are correct - replacing those characters with proper spaces does resolve the linter issue. I had not even noticed they were not actual spaces as the Puppet runs on nodes using the manifests had not complained about them. The error that is produced by the linter suggests running |
incompatible encoding regexp match
on key
incompatible encoding regexp match
for non-printing characters in place of space
Edited the issue's title and description to represent the actual issue, rather than the one I initially reported. |
I think this will be addressed successfully in #586, when the actual puppet parser is used. |
It looks like when you declare a resource and provide akey
parameter, that is not handled nicely. Swap it out forabc
and the error goes away.An example of where it is in use is thepuppetlabs/registry
module and the registry::value type it has, which has akey
parameter there, at least on latest (v1.1.4) which we are using now.The linter is not able to deal with non-printing characters in places where it expects whitespace. The parser throws out a syntax error - even though Puppet's validation does not complain about the file's contents.
puppet-lint version: 2.2.1
ruby version: 2.1.9-p490
platform: x64-mingw32
file path: ./foo/manifests/bar.pp
file contents:
error:
The text was updated successfully, but these errors were encountered: