-
Notifications
You must be signed in to change notification settings - Fork 79
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
Change log_hashes to log hash-like objects properly #268
Conversation
Note that before it would log with lots of internal structure, and now it logs more like a hash which is cleaner to read. |
Checked commit Fryguy@0316bcc with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
The event catcher runner was printing the blacklisted events array using the VMDBLogger#log_hashes method. Now that this method calls .to_hash on the argument (ManageIQ/manageiq-gems-pending#268) this is throwing an exception for non-hash type arguments. Instead of using log_hashes just log the elements of the array joined by newlines directly.
Change log_hashes to log hash-like objects properly (cherry picked from commit 2270f3d) https://bugzilla.redhat.com/show_bug.cgi?id=1531146
Fine backport details:
|
This will also log Config::Options properly, but I didn't want to include the config gem because it messes with global state. HWIA showed the same problems, and active support is already a dependency, so it will suffice.