Errors running puppet-check when metadata.json misses requirements about puppet-check HOT 6 OPEN

After some more investigation and code reading: at least the error undefined method empty?' for nil:NilClass (NoMethodError)occurs when themetadata.jsonmisses therequirementsblock. At leastpuppet-check` should warn about that and don't fail with such an error I guess.

For the other error wrong number of arguments (5 for 1..3) I haven't found a cause for now.

from puppet-check.

First issue:

I checked the source code and, strangely enough, my comment dictates the correct behavior but the code doesn't seem to follow it. It is a quick fix.

Second issue:

It looks like rubocop is using a yaml gem that comes with puppet instead of the one that comes with ruby. This could be an issue with rvm/rbenv gem loading.

from puppet-check.

First issue:

This actually revealed that i have redundant code in the related method, and I don't know how I missed that when it is the first Reek warning for the file.

Second issue:

Looking at it again, there is a possibility that you have an invalid .rubcop.yml. Give that another look to verify. Otherwise, this is some weird environment error that may best be solved on Stack Overflow.

from puppet-check.

First issue fixed in 26f3831. I recommend directly patching data_parser.rb as part of the Dockerfile for the image your are building as it will be a while before 1.4.0 since that will be the 'octocatalog-diff' release.

from puppet-check.

Thanks a lot for looking into it and I'm very sorry to have mixed two unrelated issues in one ticket.

Looking at it again, there is a possibility that you have an invalid .rubcop.yml. Give that another look to verify. Otherwise, this is some weird environment error that may best be solved on Stack Overflow.

There is no .rubcop.yml file available in this module. Seems to be related to rubocop/rubocop#3539 but I'm not sure how to fix this. I also discovered that it only happens in the Docker image with Puppet 3. The other image with Puppet 4 doesn't have this issue. And interestingly enough it isn't a general issue, for some modules tested by puppet-check the issue doesn't show up, but I couldn't find the differences until now.

from puppet-check.

Yeah, it did seem like an environment issue. The stack trace makes it seem like Rubocop is trying to load in a config file, so if there was some way to block that it might fix the issue.

from puppet-check.