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
We noticed encoding issues using this library in production, and after some investigation it turns out there's a correctness issue in the library. I took the official WPT testcases and threw a loose harness around them to make them runnable:
This then fails with a bunch of failed a assertions: Test failed with error Error: Assertion failed: 1 is not equal to 2. Commenting out the delete TextEncoder line then allows us to verify that the tests pass when executed with the native TextEncoder.
The text was updated successfully, but these errors were encountered:
In our case we were using encodeInto out of theoretical correctness rather than need; our underlying stream was being buffered anyway so we simply swapped over to encode.
We noticed encoding issues using this library in production, and after some investigation it turns out there's a correctness issue in the library. I took the official WPT testcases and threw a loose harness around them to make them runnable:
This then fails with a bunch of failed a assertions:
Test failed with error Error: Assertion failed: 1 is not equal to 2
. Commenting out thedelete TextEncoder
line then allows us to verify that the tests pass when executed with the native TextEncoder.The text was updated successfully, but these errors were encountered: