-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
src: revert 20789 as alternative to 20925 #20938
Conversation
I'm good with either this or #20925 ... This one is likely the quickest fix tho. |
Alternative to nodejs#20938 (clean revert) and nodejs#20925 (adding the headers to the release tarball). The changes to `src/node.h` are a clean revert in the same ways as nodejs#20938 does it, the difference being that the new `.cc` files are kept here. This has the advantage of not being another large diff that other PRs will have to rebase against, especially since the split into `callback_scope.cc` and `exceptions.cc` is something that we want to keep in the long run. This essentialy implements bnoordhuis’s suggestion from nodejs#20925.
Not a great fan of a full revert because it’s a large-ish change – I have had to rebase at least two PRs because of it, and I don’t exactly look forward to doing it twice again. ;) I like Ben’s suggestion from the other PR, it seems like the easiest and most long-term viable approach, so I opened #20939 with it. We could also do this PR, but in that case we should re-revert on (jasnell: edited to correct the PR link) |
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 assuming we either re-revert immediately or only land this on v10.x
Alternative to #20938 (clean revert) and #20925 (adding the headers to the release tarball). The changes to `src/node.h` are a clean revert in the same ways as #20938 does it, the difference being that the new `.cc` files are kept here. This has the advantage of not being another large diff that other PRs will have to rebase against, especially since the split into `callback_scope.cc` and `exceptions.cc` is something that we want to keep in the long run. This essentialy implements bnoordhuis’s suggestion from #20925. PR-URL: #20939 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Refael Ackermann <refack@gmail.com>
Landed the alternate |
Alternative to #20938 (clean revert) and #20925 (adding the headers to the release tarball). The changes to `src/node.h` are a clean revert in the same ways as #20938 does it, the difference being that the new `.cc` files are kept here. This has the advantage of not being another large diff that other PRs will have to rebase against, especially since the split into `callback_scope.cc` and `exceptions.cc` is something that we want to keep in the long run. This essentialy implements bnoordhuis’s suggestion from #20925. PR-URL: #20939 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Refael Ackermann <refack@gmail.com>
As a quick alternative to #20925 to fix issue #20921... revert the offending commits with intent to revisit the change.
/cc @richardlau @MylesBorins @addaleax
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes