Skip to content
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

vm: properly handle defining symbol props #47572

Merged
merged 4 commits into from May 26, 2023

Conversation

dubzzz
Copy link
Contributor

@dubzzz dubzzz commented Apr 15, 2023

This PR is a follow-up of #46615.

When bumping V8 for node 18, various bugs appeared around vm. Some have been fixed along the flow, but there is at least one remaining and described at:
jestjs/jest#13338.

The current fix does nothing on node 20: the new bump of v8 done for node 20 seems to fix it. But it would fix the problem in both node 18 and node 19. I confirmed it would fix node 19 by cherry-picking the commit on v19.x-staging and launching make -j4 jstest on it.

Fixes #47717

This PR is a follow-up of nodejs#46615.

When bumping V8 for node 18, various bugs appeared around vm.
Some have been fixed along the flow, but there is at least one
remaining and described at:
jestjs/jest#13338.

The current fix does nothing on node 20: the new bump of v8 done for
node 20 seems to fix it. But it would fix the problem in both node 18
and node 19. I confirmed it would fix node 19 by cherry-picking the
commit on v19.x-staging and launching `make -j4 jstest` on it.
@nodejs-github-bot nodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. needs-ci PRs that need a full CI run. vm Issues and PRs related to the vm subsystem. labels Apr 15, 2023
@targos
Copy link
Member

targos commented May 1, 2023

@nodejs/vm

@dubzzz
Copy link
Contributor Author

dubzzz commented May 9, 2023

@jasnell @targos Any blocker to merge it?

@nodejs-github-bot
Copy link
Collaborator

@jasnell
Copy link
Member

jasnell commented May 10, 2023

Needs a CI run. Just started it.

@dubzzz
Copy link
Contributor Author

dubzzz commented May 10, 2023

Thank you so much

@dubzzz
Copy link
Contributor Author

dubzzz commented May 10, 2023

👀 It seems that the CI passed

@dubzzz
Copy link
Contributor Author

dubzzz commented May 15, 2023

@jasnell Do you think we can merge it?

@dubzzz
Copy link
Contributor Author

dubzzz commented May 20, 2023

@jasnell Sorry for the ping, it seems that everything is green. Looking forward to see this fix merged to fix a long running issue in Jest when used with Node 18 and 19

@dubzzz
Copy link
Contributor Author

dubzzz commented May 24, 2023

Should I rebase it or merge master into it? The branch has been opened 1 month+ ago and does not seem to conflict but I was wondering if it needed to be resynced at some time to re-run the tests against an updated version of master.

@benjamingr benjamingr added commit-queue Add this label to land a pull request using GitHub Actions. dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. labels May 26, 2023
@benjamingr
Copy link
Member

I added "dont-land-on-v20" given the openjs slack message but as a reviewer please guide what's right here @jasnell

@nodejs-github-bot nodejs-github-bot added commit-queue-failed An error occurred while landing this pull request using GitHub Actions. and removed commit-queue Add this label to land a pull request using GitHub Actions. labels May 26, 2023
@nodejs-github-bot
Copy link
Collaborator

Commit Queue failed
- Loading data for nodejs/node/pull/47572
✔  Done loading data for nodejs/node/pull/47572
----------------------------------- PR info ------------------------------------
Title      vm: properly handle defining symbol props (#47572)
Author     Nicolas DUBIEN  (@dubzzz)
Branch     dubzzz:fix-symbol-vm-node-master -> nodejs:main
Labels     c++, vm, needs-ci, dont-land-on-v20.x
Commits    4
 - vm: properly handle defining symbol props
 - share more across variants of the test
 - run assertions from the sandbox too
 - run even more assertions against sandbox
Committers 1
 - Nicolas DUBIEN 
PR-URL: https://github.com/nodejs/node/pull/47572
Reviewed-By: James M Snell 
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/47572
Reviewed-By: James M Snell 
--------------------------------------------------------------------------------
   ℹ  This PR was created on Sat, 15 Apr 2023 16:12:17 GMT
   ✔  Approvals: 1
   ✔  - James M Snell (@jasnell) (TSC): https://github.com/nodejs/node/pull/47572#pullrequestreview-1414068765
   ✔  Last GitHub CI successful
   ℹ  Last Full PR CI on 2023-05-10T03:56:15Z: https://ci.nodejs.org/job/node-test-pull-request/51725/
- Querying data for job/node-test-pull-request/51725/
   ✔  Last Jenkins CI successful
--------------------------------------------------------------------------------
   ✔  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 47572
From https://github.com/nodejs/node
 * branch                  refs/pull/47572/merge -> FETCH_HEAD
✔  Fetched commits as 70da07595447..d108a9c6b972
--------------------------------------------------------------------------------
Auto-merging src/node_contextify.cc
[main feeadaf4a8] vm: properly handle defining symbol props
 Author: Nicolas DUBIEN 
 Date: Sat Apr 15 14:33:13 2023 +0000
 3 files changed, 81 insertions(+), 26 deletions(-)
 create mode 100644 test/parallel/test-vm-global-get-own.js
 delete mode 100644 test/parallel/test-vm-global-symbol.js
[main 56049eb66f] share more across variants of the test
 Author: Nicolas DUBIEN 
 Date: Wed Apr 19 11:27:08 2023 +0000
 1 file changed, 60 insertions(+), 63 deletions(-)
[main 195e77b537] run assertions from the sandbox too
 Author: Nicolas DUBIEN 
 Date: Wed Apr 19 11:42:21 2023 +0000
 1 file changed, 85 insertions(+), 33 deletions(-)
[main 71cd77fd40] run even more assertions against sandbox
 Author: Nicolas DUBIEN 
 Date: Wed Apr 19 18:35:07 2023 +0000
 1 file changed, 24 insertions(+), 48 deletions(-)
   ✔  Patches applied
There are 4 commits in the PR. Attempting autorebase.
Rebasing (2/8)

Executing: git node land --amend --yes
--------------------------------- New Message ----------------------------------
vm: properly handle defining symbol props

This PR is a follow-up of #46615.

When bumping V8 for node 18, various bugs appeared around vm.
Some have been fixed along the flow, but there is at least one
remaining and described at:
jestjs/jest#13338.

The current fix does nothing on node 20: the new bump of v8 done for
node 20 seems to fix it. But it would fix the problem in both node 18
and node 19. I confirmed it would fix node 19 by cherry-picking the
commit on v19.x-staging and launching make -j4 jstest on it.

PR-URL: #47572
Reviewed-By: James M Snell jasnell@gmail.com

[detached HEAD e3989a52b7] vm: properly handle defining symbol props
Author: Nicolas DUBIEN github@dubien.org
Date: Sat Apr 15 14:33:13 2023 +0000
3 files changed, 81 insertions(+), 26 deletions(-)
create mode 100644 test/parallel/test-vm-global-get-own.js
delete mode 100644 test/parallel/test-vm-global-symbol.js
Rebasing (3/8)
Rebasing (4/8)

Executing: git node land --amend --yes
--------------------------------- New Message ----------------------------------
share more across variants of the test

PR-URL: #47572
Reviewed-By: James M Snell jasnell@gmail.com

[detached HEAD 9d3829086b] share more across variants of the test
Author: Nicolas DUBIEN github@dubien.org
Date: Wed Apr 19 11:27:08 2023 +0000
1 file changed, 60 insertions(+), 63 deletions(-)
Rebasing (5/8)
Rebasing (6/8)

Executing: git node land --amend --yes
--------------------------------- New Message ----------------------------------
run assertions from the sandbox too

PR-URL: #47572
Reviewed-By: James M Snell jasnell@gmail.com

[detached HEAD 0194c7f82d] run assertions from the sandbox too
Author: Nicolas DUBIEN github@dubien.org
Date: Wed Apr 19 11:42:21 2023 +0000
1 file changed, 85 insertions(+), 33 deletions(-)
Rebasing (7/8)
Rebasing (8/8)

Executing: git node land --amend --yes
--------------------------------- New Message ----------------------------------
run even more assertions against sandbox

PR-URL: #47572
Reviewed-By: James M Snell jasnell@gmail.com

[detached HEAD 7229614bab] run even more assertions against sandbox
Author: Nicolas DUBIEN github@dubien.org
Date: Wed Apr 19 18:35:07 2023 +0000
1 file changed, 24 insertions(+), 48 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/5093621801

@debadree25 debadree25 added commit-queue Add this label to land a pull request using GitHub Actions. commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. and removed commit-queue-failed An error occurred while landing this pull request using GitHub Actions. labels May 26, 2023
@dubzzz
Copy link
Contributor Author

dubzzz commented May 26, 2023

As asked on openjs slack, why don't we at least merge the test part on node 20? Maybe I don't get the meaning of the don't land in tag 🤔

@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label May 26, 2023
@nodejs-github-bot nodejs-github-bot merged commit 06a211b into nodejs:main May 26, 2023
64 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in 06a211b

@benjamingr benjamingr removed the dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. label May 26, 2023
targos pushed a commit that referenced this pull request May 30, 2023
This PR is a follow-up of #46615.

When bumping V8 for node 18, various bugs appeared around vm.
Some have been fixed along the flow, but there is at least one
remaining and described at:
jestjs/jest#13338.

The current fix does nothing on node 20: the new bump of v8 done for
node 20 seems to fix it. But it would fix the problem in both node 18
and node 19. I confirmed it would fix node 19 by cherry-picking the
commit on v19.x-staging and launching `make -j4 jstest` on it.

PR-URL: #47572
Reviewed-By: James M Snell <jasnell@gmail.com>
@targos targos mentioned this pull request Jun 4, 2023
@dubzzz
Copy link
Contributor Author

dubzzz commented Jul 3, 2023

Any chance to have it in a patch of node 18?

danielleadams pushed a commit that referenced this pull request Jul 6, 2023
This PR is a follow-up of #46615.

When bumping V8 for node 18, various bugs appeared around vm.
Some have been fixed along the flow, but there is at least one
remaining and described at:
jestjs/jest#13338.

The current fix does nothing on node 20: the new bump of v8 done for
node 20 seems to fix it. But it would fix the problem in both node 18
and node 19. I confirmed it would fix node 19 by cherry-picking the
commit on v19.x-staging and launching `make -j4 jstest` on it.

PR-URL: #47572
Reviewed-By: James M Snell <jasnell@gmail.com>
MoLow pushed a commit to MoLow/node that referenced this pull request Jul 6, 2023
This PR is a follow-up of nodejs#46615.

When bumping V8 for node 18, various bugs appeared around vm.
Some have been fixed along the flow, but there is at least one
remaining and described at:
jestjs/jest#13338.

The current fix does nothing on node 20: the new bump of v8 done for
node 20 seems to fix it. But it would fix the problem in both node 18
and node 19. I confirmed it would fix node 19 by cherry-picking the
commit on v19.x-staging and launching `make -j4 jstest` on it.

PR-URL: nodejs#47572
Reviewed-By: James M Snell <jasnell@gmail.com>
Ceres6 pushed a commit to Ceres6/node that referenced this pull request Aug 14, 2023
This PR is a follow-up of nodejs#46615.

When bumping V8 for node 18, various bugs appeared around vm.
Some have been fixed along the flow, but there is at least one
remaining and described at:
jestjs/jest#13338.

The current fix does nothing on node 20: the new bump of v8 done for
node 20 seems to fix it. But it would fix the problem in both node 18
and node 19. I confirmed it would fix node 19 by cherry-picking the
commit on v19.x-staging and launching `make -j4 jstest` on it.

PR-URL: nodejs#47572
Reviewed-By: James M Snell <jasnell@gmail.com>
Ceres6 pushed a commit to Ceres6/node that referenced this pull request Aug 14, 2023
This PR is a follow-up of nodejs#46615.

When bumping V8 for node 18, various bugs appeared around vm.
Some have been fixed along the flow, but there is at least one
remaining and described at:
jestjs/jest#13338.

The current fix does nothing on node 20: the new bump of v8 done for
node 20 seems to fix it. But it would fix the problem in both node 18
and node 19. I confirmed it would fix node 19 by cherry-picking the
commit on v19.x-staging and launching `make -j4 jstest` on it.

PR-URL: nodejs#47572
Reviewed-By: James M Snell <jasnell@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c++ Issues and PRs that require attention from people who are familiar with C++. commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. needs-ci PRs that need a full CI run. vm Issues and PRs related to the vm subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Object.getOwnPropertySymbols not returning all symbols when using vm
6 participants