doc: remove reference to resolved child_process v8 issue

[isker]

The linked v8 issue is closed. The NodeJS half of that issue has also been resolved. While there still may be issues related to child_process spawn performance, they are not related to this v8 issue.

Refs: https://bugs.chromium.org/p/v8/issues/detail?id=7381
Refs: #48523
Refs: nodejs/performance#138

[isker]

I could remove the entire paragraph, as it was added all at once, but I figure the bit I've left is not wrong. Let me know if you think it should be removed.

[kvakil]

Thanks, I missed this line! Can you delete the paragraph entirely? It's obviously true that any asynchronous operation will "perform[] memory operations synchronously", the previous wording made sense as a way of emphasizing a particularly large cost which I think is no longer necessary to mention.

[isker]

Done.

[nodejs-github-bot]

Commit Queue failed

- Loading data for nodejs/node/pull/51467
✔  Done loading data for nodejs/node/pull/51467
----------------------------------- PR info ------------------------------------
Title      doc: remove reference to resolved child_process v8 issue (#51467)
   ⚠  Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch     isker:patch-2 -> nodejs:main
Labels     child_process, doc, author ready
Commits    2
 - doc: remove reference to resolved child_process v8 issue
 - Update child_process.md
Committers 1
 - GitHub 
PR-URL: https://github.com/nodejs/node/pull/51467
Refs: https://bugs.chromium.org/p/v8/issues/detail?id=7381
Refs: https://github.com/nodejs/node/pull/48523
Refs: https://github.com/nodejs/performance/issues/138
Reviewed-By: Keyhan Vakil 
Reviewed-By: Luigi Pinca 
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/51467
Refs: https://bugs.chromium.org/p/v8/issues/detail?id=7381
Refs: https://github.com/nodejs/node/pull/48523
Refs: https://github.com/nodejs/performance/issues/138
Reviewed-By: Keyhan Vakil 
Reviewed-By: Luigi Pinca 
--------------------------------------------------------------------------------
   ℹ  This PR was created on Mon, 15 Jan 2024 03:47:37 GMT
   ✔  Approvals: 2
   ✔  - Keyhan Vakil (@kvakil): https://github.com/nodejs/node/pull/51467#pullrequestreview-1826255104
   ✔  - Luigi Pinca (@lpinca): https://github.com/nodejs/node/pull/51467#pullrequestreview-1828022124
   ✔  Last GitHub CI successful
   ℹ  Green GitHub CI is sufficient
--------------------------------------------------------------------------------
   ✔  No git cherry-pick in progress
   ✔  No git am in progress
   ✔  No git rebase in progress
--------------------------------------------------------------------------------
- Bringing origin/main up to date...
From https://github.com/nodejs/node
 * branch                  main       -> FETCH_HEAD
✔  origin/main is now up-to-date
- Downloading patch for 51467
From https://github.com/nodejs/node
 * branch                  refs/pull/51467/merge -> FETCH_HEAD
✔  Fetched commits as 6ab15a1aa8de..9cca93061688
--------------------------------------------------------------------------------
[main cfaf7262ca] doc: remove reference to resolved child_process v8 issue
 Author: Ian Kerins 
 Date: Sun Jan 14 22:46:09 2024 -0500
 1 file changed, 1 insertion(+), 3 deletions(-)
[main b51f83b9b7] Update child_process.md
 Author: Ian Kerins 
 Date: Wed Jan 17 01:44:46 2024 +0000
 1 file changed, 4 deletions(-)
   ✔  Patches applied
There are 2 commits in the PR. Attempting autorebase.
Rebasing (2/4)
Executing: git node land --amend --yes

⚠  Found Refs: https://bugs.chromium.org/p/v8/issues/detail?id=7381, skipping..

⚠  Found Refs: #48523, skipping..

⚠  Found Refs: nodejs/performance#138, skipping..

--------------------------------- New Message ----------------------------------

doc: remove reference to resolved child_process v8 issue
The linked v8 issue is closed. The NodeJS half of that issue has also

been resolved. While there still may be issues related to

child_process spawn performance, they are not related to this v8 issue.
Refs: https://bugs.chromium.org/p/v8/issues/detail?id=7381

Refs: #48523

Refs: nodejs/performance#138

PR-URL: #51467

Reviewed-By: Keyhan Vakil [email protected]

Reviewed-By: Luigi Pinca [email protected]
[detached HEAD 4afd586645] doc: remove reference to resolved child_process v8 issue

Author: Ian Kerins [email protected]

Date: Sun Jan 14 22:46:09 2024 -0500

1 file changed, 1 insertion(+), 3 deletions(-)

Rebasing (3/4)

Rebasing (4/4)
Executing: git node land --amend --yes

--------------------------------- New Message ----------------------------------

Update child_process.md
PR-URL: #51467

Refs: https://bugs.chromium.org/p/v8/issues/detail?id=7381

Refs: #48523

Refs: nodejs/performance#138

Reviewed-By: Keyhan Vakil [email protected]

Reviewed-By: Luigi Pinca [email protected]
[detached HEAD c0a9578c16] Update child_process.md

Author: Ian Kerins [email protected]

Date: Wed Jan 17 01:44:46 2024 +0000

1 file changed, 4 deletions(-)
Successfully rebased and updated refs/heads/main.
ℹ  Add commit-queue-squash label to land the PR as one commit, or commit-queue-rebase to land as separate commits.

https://github.com/nodejs/node/actions/runs/7560845377

[nodejs-github-bot]

Landed in eb4432c