Revert "perf: reuse TextDecoder instance (#2863)"#2999
Conversation
This reverts commit 2091dcf.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2999 +/- ##
==========================================
- Coverage 93.50% 93.50% -0.01%
==========================================
Files 89 89
Lines 24223 24220 -3
==========================================
- Hits 22649 22646 -3
Misses 1574 1574 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
ronag
left a comment
There was a problem hiding this comment.
ACtually doesn't this just move the issue to when websocket is used? Should we maybe not pass fatal? Does the spec require that? If it does, then maybe we should disable websocket for builds without ICU?
I don't particularly care how this moves forward but the revert is needed to unblock a Node.js version bump. |
Uzlopak
left a comment
There was a problem hiding this comment.
It actually revealed that there is an issue with no-icu cases.
Which, now that we know about it, we can take all the time in the world to contemplate a fix for. In the meantime, node's bundled fetch is lagging behind on fixes which is why this revert is proposed. |
|
I would atleast expect that you open an issue here, so that it keeps tracked. |
Uzlopak
left a comment
There was a problem hiding this comment.
Approving but somebody should create an issue.
Noted. |
|
@mcollina can you do a release? Node nightly is currently lagging on 6.6.2 |
|
6.10.2 published |
yes, we're meant to close the connection if we receive invalid utf-8
It's already essentially disabled:
We might be able to support builds without icu by using Buffer.isUTF8, but it should only be used when we can't use TextDecoder for perf. I'm not really sure if it's available in builds without ICU and I don't have the time to test myself. |
This reverts commit 2091dcf.
See