Handle console output that is improperly encoded #121
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.
Not sure why, but in some cases the data received from SSHKit claims to be encoded as UTF-8 but is actually invalid. This causes
gsub
to blow up withArgumentError: invalid byte sequence in UTF-8
when airbrussh callsstrip_ascii_color
.Work around this by detecting invalid encoding and stripping out the offending code points from string before calling
gsub
.Fixes #120
@dbackeus can you test using this branch to see if this resolves your issue? 🙏