-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
private method `load' called for SafeYAML:Module #2935
Comments
Update README.md and CHANGELOG.md Bring rspec-puppet up to date Remove rubocop (due to rake 11 and rubocop 0.38.0 incompatabilities, [issue #2935](rubocop/rubocop#2935)) Update spec_helper to use ::new instead of [] to remove warning
Update README.md and CHANGELOG.md Bring rspec-puppet up to date Remove rubocop (due to rake 11 and rubocop 0.38.0 incompatabilities, [issue #2935](rubocop/rubocop#2935)) Update spec_helper to use ::new instead of [] to remove warning
@jonas054 No change after |
Then I don't know. Apparently the Perhaps you can examine the
|
According to safe_yaml doc (github.com/dtao/safe_yaml/blob/master/README.md):
So the following seems to work as it should:
This issue only happens if I run rubocop as a rake task.
When invoking rubocop directly |
@aquister Thanks for digging up that information! It all makes sense now, except that we still don't know why Anyway, it can happen. Apparently. So I guess we could solve it with if defined?(SafeYAML) && SafeYAML.respond_to?(:load) We also need a spec example that creates a stub |
[Fix #2935] Make config loading work if SafeYAML.load is private
Running RuboCop...
private method 'load' called for SafeYAML:Module
~/.rvm/gems/ruby-2.1.5/gems/rubocop-0.38.0/lib/rubocop/config_loader.rb:165:in 'yaml_safe_load'
...
RuboCop failed!
The text was updated successfully, but these errors were encountered: