[v11.x-backport] Backport 24861 to v11.x#25258
Closed
gabrielschulhof wants to merge 2 commits intonodejs:v11.x-stagingfrom
Closed
[v11.x-backport] Backport 24861 to v11.x#25258gabrielschulhof wants to merge 2 commits intonodejs:v11.x-stagingfrom
gabrielschulhof wants to merge 2 commits intonodejs:v11.x-stagingfrom
Conversation
Originally from portions of nodejs#23319. PR-URL: nodejs#24861 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
This is an alternative to nodejs#23319 which attaches the loaded addons to the environment and closes them when the environment is destroyed. PR-URL: nodejs#24861 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
nodejs-github-bot
added
c++
Member
|
What was the conflict? |
Contributor
Author
|
@targos I didn't run into a conflict. I made this PR because there was a backport-requested tag. I was surprised to find no conflict. I figured although there might not be a source code conflict the tests might fail or something, but they didn't fail locally. |
Contributor
Author
targos
pushed a commit
that referenced
this pull request
Jan 1, 2019
Originally from portions of #23319. Backport-PR-URL: #25258 PR-URL: #24861 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
targos
pushed a commit
that referenced
this pull request
Jan 1, 2019
This is an alternative to #23319 which attaches the loaded addons to the environment and closes them when the environment is destroyed. Backport-PR-URL: #25258 PR-URL: #24861 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
Member
Contributor
|
This needed to be tested with CITGM before it was landed. The original commits were breaking |
Merged
Member
|
@MylesBorins I’m not sure, but maybe adding a backport request to a change that broke something in CITGM is a bit confusing? We still want a clean CITGM on master, so dont-land + a request to investigate could be a better approach for the future? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesRe: #24861 (comment)