You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because of the ASCII_8BIT job argument, the whole exception message ends up as ASCII_8BIT. We're able to combine that just fine with other ascii-only strings, but we're not able to combine that with the UTF_8 ↳ used to print the backtrace.
What did you expect to happen?
I'm not certain. Encodings can be difficult...
A fallback to leave out the ↳ if there's any sort of encoding problem, perhaps? Or replace it with - or something else ascii that's likely to be more broadly compatible?
Environment
Ruby Version:
3.2
Framework Version (Rails, whatever):
Rails main (7.1)
Isolator Version:
0.10.0
The text was updated successfully, but these errors were encountered:
What did you do?
Tried running isolator against the GitHub test suite and saw a number of
incompatible character encodings: ASCII-8BIT and UTF-8
errors.Here's a test to reproduce the problem:
Because of the ASCII_8BIT job argument, the whole exception message ends up as ASCII_8BIT. We're able to combine that just fine with other ascii-only strings, but we're not able to combine that with the UTF_8
↳
used to print the backtrace.What did you expect to happen?
I'm not certain. Encodings can be difficult...
A fallback to leave out the
↳
if there's any sort of encoding problem, perhaps? Or replace it with-
or something else ascii that's likely to be more broadly compatible?Environment
Ruby Version:
3.2
Framework Version (Rails, whatever):
Rails main (7.1)
Isolator Version:
0.10.0
The text was updated successfully, but these errors were encountered: