-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
deps/v8: add missing #include "unicode/normlzr.h" #13040
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, thanks. CI: https://ci.nodejs.org/job/node-test-pull-request/8096/
hey @ArchangeGabriel thanks for submitting this PR This patch most likely needs to be sent upstream to V8 first. We could then backport the V8 patch to each appropriate release stream. /cc @fhinkel who might be able to help with this (a patch on V8 and then a backport to Node!!!) As a heads up, v4.x is in maintenance mode, it would not likely land for a while due to not being |
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.
-1 needs to be fixed in V8
edit:
this is not meaningful upstream to V8 so it makes sense to land it as a patch onto v6.x and backport to v4.x
@MylesBorins This patch is not relevant upstream, they are switching (or have switched) to ICU 59. |
LGTM. Yes, upstream V8 wouldn't be right. Thanks @ArchangeGabriel ! |
My apologies. I must have misunderstood something. Should this target master? |
I don't think so, master bundles ICU 59. This is just for v4.x and v6.x since they bundle ICU 58. |
master is not affected. This file is quite different in master, and already supports ICU 59. See #11753 for master and the v8 patches/links. |
@MylesBorins To be more clear maybe: upstream v8 is not 4.x or 6.x v8, you only do cherry-pick. Upstream v8 doesn’t need patching, because the current version supports ICU 59 (since patches/links from my previous comment). Upstream v8 patches cannot be backported, because node 4.x and 6.x v8 doesn’t need the same fixes as upstream v8 for ICU 59, since the code is quite different. |
Ok excellent. I think it would make sense to Target v6.x and then we can
backport to v4.x
I can land this today and get it in the r.c. if we get sign off
…On May 16, 2017 10:06 AM, "Bruno Pagani" ***@***.***> wrote:
@MylesBorins <https://github.com/mylesborins> To be more clear maybe:
upstream v8 is not 4.x or 6.x v8, you only do cherry-pick.
Upstream v8 doesn’t need patching, because the current version supports
ICU 59 (since patches/links from my previous comment).
Upstream v8 patches cannot be backported, because node 4.x and 6.x v8
doesn’t need the same fixes as upstream v8 for ICU 59, since the code is
quite different.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13040 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecV4uXkZKEPe8f4xPVltkmM_NcW5E3ks5r6a1KgaJpZM4NbggI>
.
|
OK, I’ve targeted v4.x first because it’s the one I have to use, but the fix is the same for v6.x. I suppose you should also wait for ARM and ppc-linux CI to finish before merging? |
@ArchangeGabriel we generally waterfall from newer releases to older ones. Further v4.x is in maintenance, so a release won't be happening for quite a while for non critical bugs. If you are ok with it I'll update the issue to target v6.x and run CI again |
@nodejs/v8 how would we want to float a patch like this on V8 for v6.x? Should it bump patch number? |
Yes |
@MylesBorins Yeah, sure. I fixed it on my side anyway, so this is mostly for other users/to be able to remove the patch from my build system. v6.x needs to be fixed too, I just didn’t open the v6.x PR in case this one would have required fixes. |
@ArchangeGabriel github was not able to smartly change target... I have a working branch (including V8 bump). Can you enable us to push to your branch so I can update? |
This is already on. |
odd... |
Ahhh... I don't think we can force push. here is the patch can you checkout v6.x-staging, cherry-pick, and force push over this branch. Sorry this is so convoluted |
I can redo my branch to be only the patch on v6.x, and then you could add your bump and any other change, if that’s easier for you. |
Our messages crossed. I’m doing that right now (but could take some time since I don’t think I can do that from GitHub web, so I’ll have to clone the repo locally first). |
@ArchangeGabriel whatever is easier for you. We only need to bump the patch number in |
Done, sorry for the delay. |
* The following function from <unicode/normlzr.h> is used: normalize() * Until ICU 59, <unicode/normlzr.h> is indirectly included, but this changed with the 59 release. Adding this header has been the right thing to do for many years, so it is backwards compatible and fix compilation with recent ICU. Refs: #13022
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
@nodejs/lts anyone else want to review this? |
Maybe cc/ @srl295 ? |
Small ping. I’d like to get this fixed in Argon and Boron so that I could package them without an out-of-tree patch. :) |
@ArchangeGabriel It has a couple of LGTMs, I expect it will land in the next v6.x patch release. |
* The following function from <unicode/normlzr.h> is used: normalize() * Until ICU 59, <unicode/normlzr.h> is indirectly included, but this changed with the 59 release. Adding this header has been the right thing to do for many years, so it is backwards compatible and fix compilation with recent ICU. Refs: #13022 PR-URL: #13040 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Landed in d3ae2f0 I'll backport to v4.x-staging but can make no guarantees when, if at all, we will land it |
* The following function from <unicode/normlzr.h> is used: normalize() * Until ICU 59, <unicode/normlzr.h> is indirectly included, but this changed with the 59 release. Adding this header has been the right thing to do for many years, so it is backwards compatible and fix compilation with recent ICU. Refs: #13022 PR-URL: #13040 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Thanks! :) I’ll keep an eye on v4.x changes to see if that get merged, but I’ll just keep the patch in my tree else. ;) |
* The following function from <unicode/normlzr.h> is used: normalize() * Until ICU 59, <unicode/normlzr.h> is indirectly included, but this changed with the 59 release. Adding this header has been the right thing to do for many years, so it is backwards compatible and fix compilation with recent ICU. Refs: #13022 PR-URL: #13040 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
* The following function from <unicode/normlzr.h> is used: normalize() * Until ICU 59, <unicode/normlzr.h> is indirectly included, but this changed with the 59 release. Adding this header has been the right thing to do for many years, so it is backwards compatible and fix compilation with recent ICU. Refs: #13022 PR-URL: #13040 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
* The following function from <unicode/normlzr.h> is used: normalize() * Until ICU 59, <unicode/normlzr.h> is indirectly included, but this changed with the 59 release. Adding this header has been the right thing to do for many years, so it is backwards compatible and fix compilation with recent ICU. Refs: nodejs/node#13022 PR-URL: nodejs/node#13040 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
* The following function from <unicode/normlzr.h> is used: normalize() * Until ICU 59, <unicode/normlzr.h> is indirectly included, but this changed with the 59 release. Adding this header has been the right thing to do for many years, so it is backwards compatible and fix compilation with recent ICU. Refs: #13022 PR-URL: #13040 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Notable Changes: * **crypto**: - update root certificates (Ben Noordhuis) #13279 - update root certificates (Ben Noordhuis) #12402 * **deps**: - add support for more modern versions of INTL (Bruno Pagani) #13040 - upgrade openssl sources to 1.0.2m (Shigeki Ohtsu) #16691 - upgrade openssl sources to 1.0.2l (Daniel Bevenius) #13233 PR-URL: #16500
Notable Changes: * **crypto**: - update root certificates (Ben Noordhuis) #13279 - update root certificates (Ben Noordhuis) #12402 * **deps**: - add support for more modern versions of INTL (Bruno Pagani) #13040 - upgrade openssl sources to 1.0.2m (Shigeki Ohtsu) #16691 - upgrade openssl sources to 1.0.2l (Daniel Bevenius) #13233 PR-URL: #16500
@MylesBorins Thanks for having finally merged that patch in v4.x. :) |
* The following function from <unicode/normlzr.h> is used: normalize() * Until ICU 59, <unicode/normlzr.h> is indirectly included, but this changed with the 59 release. Adding this header has been the right thing to do for many years, so it is backwards compatible and fix compilation with recent ICU. Refs: nodejs/node#13022 PR-URL: nodejs/node#13040 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
The following function from <unicode/normlzr.h> is used:
normalize()
Until ICU 59, <unicode/normlzr.h> is indirectly included, but this changed with the 59 release. Adding this header has been the right thing to do for many years, so it is backwards compatible and fix compilation with recent ICU.
Refs: #13022
P.S.: This is my first PR in Node, and my first “real” PR in any project, so I don’t expect it to be alright from the start.