-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
src: disable fast methods for buffer.write
#54565
src: disable fast methods for buffer.write
#54565
Conversation
It should resolve the regressions while we work on fixing them. Refs: nodejs#54521
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #54565 +/- ##
==========================================
- Coverage 87.33% 87.33% -0.01%
==========================================
Files 649 649
Lines 182626 182620 -6
Branches 35041 35040 -1
==========================================
- Hits 159503 159489 -14
- Misses 16394 16404 +10
+ Partials 6729 6727 -2
|
If this is accepted, it should be fast-tracked for inclusion in #54560 |
Fast-track has been requested by @targos. Please 👍 to approve. |
@bricss please do not approve fast-track requests :] (or you know, start making PRs and join as a collaborator that also works :)) |
@targos can you fix commit msg (PR-URL)? |
"utf8WriteStatic", | ||
SlowWriteString<UTF8>, | ||
&fast_write_string); | ||
SetMethod(context, target, "asciiWriteStatic", SlowWriteString<ASCII>); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
non-blocking nit: perhaps consider adding a TODO comment?
@ronag I don't see a problem in the commit message. |
|
This message appears (to collaborators) on all the pull requests of the project. Unfortunately there is no way to customize it but the goal is to prevent merging by accident using the GitHub UI. |
Landed in 7616855 |
It should resolve the regressions while we work on fixing them. Refs: #54521 PR-URL: #54565 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Robert Nagy <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]>
It should resolve the regressions while we work on fixing them. Refs: #54521 PR-URL: #54565 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Robert Nagy <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]>
It should resolve the regressions while we work on fixing them. Refs: #54521 PR-URL: #54565 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Robert Nagy <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]>
Now that Node.js 22.8 is available with a workaround (nodejs/node#54565) for the bug in 22.7 that caused 'RangeError: "length" is outside of buffer bounds' errors in exporter tests (see open-telemetry#4953), we can unpin the Node.js v22 used for unit tests. This undoes the pinning from open-telemetry#4957.
It should resolve the regressions while we work on fixing them. Refs: nodejs#54521 PR-URL: nodejs#54565 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Robert Nagy <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]>
It should resolve the regressions while we work on fixing them.
Refs: #54521