GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — vm: properly handle defining symbol props by dubzzz · Pull Request #47572 · nodejs/node

Conversation

@dubzzz

@dubzzz dubzzz commented Apr 15, 2023 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor

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

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

bricss and skeet70 reacted with thumbs up emoji
All reactions
  • 👍 2 reactions
@dubzzz
vm: properly handle defining symbol props
d164cd4
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
dubzzz added 3 commits April 19, 2023 11:27
@dubzzz
share more across variants of the test
d7fc35e
@dubzzz
run assertions from the sandbox too
6ab652b
@dubzzz
run even more assertions against sandbox
d108a9c
@dubzzz dubzzz mentioned this pull request Apr 25, 2023
Object.getOwnPropertySymbols not returning all symbols when using vm #47717
Closed
@targos

targos commented May 1, 2023

Copy link
Copy Markdown
Member

@nodejs/vm

dubzzz reacted with heart emoji
All reactions
  • ❤️ 1 reaction

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

jasnell
jasnell approved these changes May 5, 2023
View reviewed changes
@dubzzz dubzzz mentioned this pull request May 5, 2023
Setting __proto__ on vm context's globalThis causes a crash (regression in v19.9.0) #47798
Closed
@dubzzz

dubzzz commented May 9, 2023

Copy link
Copy Markdown
Contributor Author

@jasnell @targos Any blocker to merge it?

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@nodejs-github-bot

nodejs-github-bot commented May 10, 2023

Copy link
Copy Markdown
Collaborator

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

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@jasnell

jasnell commented May 10, 2023

Copy link
Copy Markdown
Member

Needs a CI run. Just started it.

dubzzz reacted with heart emoji
All reactions
  • ❤️ 1 reaction

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@dubzzz

dubzzz commented May 10, 2023

Copy link
Copy Markdown
Contributor Author

Thank you so much

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@dubzzz

dubzzz commented May 10, 2023

Copy link
Copy Markdown
Contributor Author

👀 It seems that the CI passed

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@dubzzz

dubzzz commented May 15, 2023

Copy link
Copy Markdown
Contributor Author

@jasnell Do you think we can merge it?

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@dubzzz

dubzzz commented May 20, 2023

Copy link
Copy Markdown
Contributor Author

@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

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@dubzzz

dubzzz commented May 24, 2023

Copy link
Copy Markdown
Contributor Author

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.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@benjamingr benjamingr added commit-queue PRs queued for automated landing through the Commit Queue. dont-land-on-v20.x labels May 26, 2023
@benjamingr

benjamingr commented May 26, 2023

Copy link
Copy Markdown
Member

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

debadree25 reacted with thumbs up emoji
All reactions
  • 👍 1 reaction

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@nodejs-github-bot nodejs-github-bot added commit-queue-failed PRs whose Commit Queue landing failed and need manual intervention before retrying. and removed commit-queue PRs queued for automated landing through the Commit Queue. labels May 26, 2023
@nodejs-github-bot

nodejs-github-bot commented May 26, 2023

Copy link
Copy Markdown
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 [email protected]

[detached HEAD e3989a52b7] vm: properly handle defining symbol props
Author: Nicolas DUBIEN [email protected]
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 [email protected]

[detached HEAD 9d3829086b] share more across variants of the test
Author: Nicolas DUBIEN [email protected]
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 [email protected]

[detached HEAD 0194c7f82d] run assertions from the sandbox too
Author: Nicolas DUBIEN [email protected]
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 [email protected]

[detached HEAD 7229614bab] run even more assertions against sandbox
Author: Nicolas DUBIEN [email protected]
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

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@debadree25 debadree25 added commit-queue PRs queued for automated landing through the Commit Queue. commit-queue-squash PRs the Commit Queue should land as one squashed commit. and removed commit-queue-failed PRs whose Commit Queue landing failed and need manual intervention before retrying. labels May 26, 2023
@dubzzz

dubzzz commented May 26, 2023 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor Author

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 🤔

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@nodejs-github-bot nodejs-github-bot removed the commit-queue PRs queued for automated landing through the Commit Queue. label May 26, 2023
@nodejs-github-bot
nodejs-github-bot merged commit 06a211b into nodejs:main May 26, 2023
@nodejs-github-bot

nodejs-github-bot commented May 26, 2023

Copy link
Copy Markdown
Collaborator

Landed in 06a211b

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@benjamingr benjamingr removed the dont-land-on-v20.x label May 26, 2023
targos pushed a commit that referenced this pull request May 30, 2023
@dubzzz @targos
vm: properly handle defining symbol props
ed45142
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 <[email protected]>
@targos targos mentioned this pull request Jun 4, 2023
v20.3.0 release proposal #48332
Merged
@dubzzz

dubzzz commented Jul 3, 2023

Copy link
Copy Markdown
Contributor Author

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

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

danielleadams pushed a commit that referenced this pull request Jul 6, 2023
@dubzzz @danielleadams
vm: properly handle defining symbol props
3073ccb
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 <[email protected]>
MoLow pushed a commit to MoLow/node that referenced this pull request Jul 6, 2023
@dubzzz @MoLow
vm: properly handle defining symbol props
d9a68b8
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 <[email protected]>
@danielleadams danielleadams mentioned this pull request Jul 10, 2023
v18.17.0 release proposal #48694
Merged
Ceres6 pushed a commit to Ceres6/node that referenced this pull request Aug 14, 2023
@dubzzz @Ceres6
vm: properly handle defining symbol props
de12099
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 <[email protected]>
Ceres6 pushed a commit to Ceres6/node that referenced this pull request Aug 14, 2023
@dubzzz @Ceres6
vm: properly handle defining symbol props
2c388cf
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 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jasnell jasnell jasnell approved these changes

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

c++ Issues and PRs that require attention from people who are familiar with C++. commit-queue-squash PRs the Commit Queue should land as one squashed commit. needs-ci PRs that need a full CI run. vm Issues and PRs related to the vm subsystem.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Object.getOwnPropertySymbols not returning all symbols when using vm

Uh oh!

There was an error while loading. Please reload this page.

6 participants

@dubzzz @targos @nodejs-github-bot @jasnell @benjamingr @debadree25
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.