-
Notifications
You must be signed in to change notification settings - Fork 30k
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
[v12.x] Backport 33570 and 33508 to v12.x #33819
[v12.x] Backport 33570 and 33508 to v12.x #33819
Conversation
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.
LGTM
@codebytere could we please have this PR in 12.18.3? |
... it's blocking some work on node-addon-api (nodejs/node-addon-api#738) and causing nodejs/node-addon-api#730. |
Refs: nodejs/node-addon-api#722 Ensure a scope is on stack during finalization as finalization functions can create JS Objects Signed-off-by: Michael Dawson <[email protected]> PR-URL: nodejs#33508 Reviewed-By: Gabriel Schulhof <[email protected]> Reviewed-By: James M Snell <[email protected]>
8821399
to
344889e
Compare
One of the commits (n-api: remove |
The remaining commit in this PR is a backport of 362e4a1, which currently applies cleanly when cherry-picked onto v12.x-staging. |
The remaining commit landed as 90ddf0a. Thanks @codebytere! |
#33508 cannot be backported directly, but must be preceded with a backport of #33570.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes