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
The real problem is we just reported the byte length as the string length for broken strings while MRI tries to calculate the character length and stops when it encounters an invalid byte sequence. Neither value is correct -- the string is broken so you can't calculate the correct value. So, I previously opted to use a faster calculation. But, broken strings are likely to be infrequent so we can be slower to match MRI. However, I also wouldn't recommend relying on that value since it seems like something that's not well defined.
I've ran into this issue while working on encode specs / scrub stuff
Example
Expected Behavior
Actual Behavior
The text was updated successfully, but these errors were encountered: