🐛 Support displaying variables with non-unicode data #758
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.
Description
This fixes #756
DAP is JSON-based, so the state of all variables is dumped into a string that needs to be unicode. When a variable contains binary data that is NOT unicode, this breaks with:
source sequence is illegal/malformed utf-8
.This patch makes sure that we can display at least part, and show the user that the data they are seeing is not exactly the one that is in memory.
Testing
I tried this in VSCode (which uses DAP), and saw:
As a side note,
vscode-ruby-debug
doesn't even try to show the variable content and just shows[Invalid encoding]
, which, IMO, is a worse UX.