fix: Update logging to coerce ASCII-8BIT into UTF-8. #1076
Merged
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.
r? @stripe/server-api-libraries-admins
Summary
Updates our logging utilities to transform any string encoded as ASCII-8bit (raw binary) to UTF-8 when logging out.
The strings returned from the server are in ASCII-8bit until the JSON marshaller transforms them to UTF-8. Unfortunately we have logging statements which pass the raw content sent back from the server. puts fails to interpret these as 8bit because they're actually utf-8 characters.
So, we force any binary string to actually be encoded as UTF-8 for the purposes of debug logging.
Alternatives:
Motivation
Fix #1059