Skip to content

src: disable fast methods for buffer.write - #54565

Merged
nodejs-github-bot merged 1 commit into
nodejs:mainfrom
targos:buffer-fast-write-disable
Aug 29, 2024
Merged

src: disable fast methods for buffer.write#54565
nodejs-github-bot merged 1 commit into
nodejs:mainfrom
targos:buffer-fast-write-disable

Conversation

@targos

Copy link
Copy Markdown
Member

It should resolve the regressions while we work on fixing them.

Refs: #54521

It should resolve the regressions while we work on fixing them.
Refs: nodejs#54521
@nodejs-github-botnodejs-github-bot added buffer Issues and PRs related to the buffer subsystem. c++ Issues and PRs that require attention from people who are familiar with C++. needs-ci PRs that need a full CI run. labels Aug 26, 2024
@targostargos mentioned this pull request Aug 26, 2024
@codecov

codecovBot commented Aug 26, 2024

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.33%. Comparing base (1399d4e) to head (a7a10a7).
Report is 323 commits behind head on main.

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 
Files with missing linesCoverage Δ
src/node_buffer.cc69.94% <100.00%> (-0.71%)⬇️

... and 23 files with indirect coverage changes

@targos

Copy link
Copy Markdown
MemberAuthor

If this is accepted, it should be fast-tracked for inclusion in #54560

@targostargos added the fast-track PRs that do not need to wait for 48 hours to land. label Aug 26, 2024
@github-actions

Copy link
Copy Markdown
Contributor

Fast-track has been requested by @targos. Please 👍 to approve.

@benjamingr

Copy link
Copy Markdown
Member

@bricss please do not approve fast-track requests :] (or you know, start making PRs and join as a collaborator that also works :))

@targostargos added the request-ci Add this label to start a Jenkins CI on a PR. label Aug 26, 2024
@github-actionsgithub-actionsBot removed the request-ci Add this label to start a Jenkins CI on a PR. label Aug 26, 2024
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@ronagronag added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. request-ci Add this label to start a Jenkins CI on a PR. labels Aug 26, 2024
@github-actionsgithub-actionsBot removed the request-ci Add this label to start a Jenkins CI on a PR. label Aug 26, 2024
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@ronag

Copy link
Copy Markdown
Member

@targos can you fix commit msg (PR-URL)?

Comment threadsrc/node_buffer.cc
"utf8WriteStatic",
SlowWriteString<UTF8>,
&fast_write_string);
SetMethod(context, target, "asciiWriteStatic", SlowWriteString<ASCII>);

Copy link
Copy Markdown
Member

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?

@targos

Copy link
Copy Markdown
MemberAuthor

@ronag I don't see a problem in the commit message.

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@ronag

ronag commented Aug 28, 2024

Copy link
Copy Markdown
Member

@ronag I don't see a problem in the commit message.

@targos

Commit message must match a given regex pattern: PR-URL: https://github\.com/(nodejs|nodejs-private)/(node|node-private)/pull/\d+

@targos

Copy link
Copy Markdown
MemberAuthor

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.

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

CI: https://ci.nodejs.org/job/node-test-pull-request/61616/

@lpincalpinca added the commit-queue Add this label to land a pull request using GitHub Actions. label Aug 29, 2024
@nodejs-github-botnodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Aug 29, 2024
@nodejs-github-bot
nodejs-github-bot merged commit 7616855 into nodejs:mainAug 29, 2024
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Landed in 7616855

@targos
targos deleted the buffer-fast-write-disable branch August 29, 2024 07:24
RafaelGSS pushed a commit that referenced this pull request Aug 30, 2024
It should resolve the regressions while we work on fixing them.
Refs: #54521
PR-URL: #54565
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Robert Nagy <ronagy@icloud.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: James M Snell <jasnell@gmail.com>
@emilazyemilazy mentioned this pull request Sep 3, 2024
13 tasks
trentm added a commit to trentm/opentelemetry-js that referenced this pull request Sep 4, 2024
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.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.bufferIssues and PRs related to the buffer subsystem.c++Issues and PRs that require attention from people who are familiar with C++.fast-trackPRs that do not need to wait for 48 hours to land.needs-ciPRs that need a full CI run.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants

@targos@benjamingr@nodejs-github-bot@ronag@jasnell@addaleax@lpinca@anonrig