Force ohai output to UTF-8 to avoid invalid characters #548
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
replaces invalid characters in the rendered JSON and avoids throwing an exception at that stage.
|
@chef/client-core this will fix the travis failures. should probably have a spec for this but i'm busy shaving other yaks today. |
|
👍 |
|
None of the strings made much sense. One was coming from /proc/cpuinfo but the non-UTF8 chars made no sense. |
lamont-granquist
added a commit
that referenced
this pull request
May 26, 2015
force ohai output to UTF-8
tas50
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
replaces invalid characters in the rendered JSON and avoids throwing
an exception at that stage.