Closed mgossage closed 1 year ago
Hey @mgossage, are you testing this on Windows? I was able to reproduce your issue in the Windows terminal because my system wasn't using UTF-8 as its default encoding. Once I switched to UTF-8, the issue was resolved.
(1) Go to administrative language settings (2) Change system locale (3) Check Beta: Use Unicode UTF-8 for worldwide language support box (4) Restart PC
Tried that, exactly the same error. Also the question marks seem to be actual question marks and not just out of range values. I will dig some more.
@mgossage okay thanks for digging a bit more. I also looked at my breakpoint and saw the correct UTF-8 chars in your example.
@mgossage this should be resolved in the latest release but feel free to reopen and let me know if not.
Repro steps: