-
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
Feature/update cares to 2bae2d56d7866defcee18455c1f2ecfef6c7663d #5090
Feature/update cares to 2bae2d56d7866defcee18455c1f2ecfef6c7663d #5090
Conversation
On Windows, when compiling with `UNICODE` defined, `LoadLibrary` becomes `LoadLibraryW`. When an ASCII string is passed to that function it crashes. PR-URL: nodejs#226 Reviewed-By: Bert Belder <bertbelder@gmail.com>
Anything regarding #894 in there? |
I doubt that it fixes it. |
I'm not sure what to make of the SmartOS and Windows failures. |
@indutny can we have this in https://github.com/piscisaureus/cares instead? Maybe we can move that repo somewhere more appropriate? /cc @piscisaureus |
@saghul hm... do we have CI there? |
CI is green after fixes. |
We don't, because it just contains the C library, and the test suite for it
|
@saghul yeah, I know this. However, it is very important to test it across various platforms. See failures on Windows and SmartOS above. I will be more than happy to submit PR there once I'll get LGTM here. |
* prefixed with fec0:0:0:ffff. These ususally do not point to | ||
* working DNS servers, so we ignore them. */ | ||
if (strncmp(txtaddr, "fec0:0:0:ffff:", 14) == 0) | ||
continue; |
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.
You should retain this, it's from a patch we float.
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.
FTR, it's this one: 3afa5e6 Maybe the comment can be prefixed with "nodejs:" so it's easier to spot that it's a floating patch?
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.
Looks like it got merged into previous update commit, so I missed it. Ack.
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.
@saghul I think it should be enough to just float the patch actually instead of squashing it into update commit.
@indutny ok, no worries. The changes LGTM, except for the missing floating patch @bnoordhuis mentioned. @silverwind was that problem reported upstream? |
/* Configure process defines this to 1 when it finds out that system */ | ||
/* header file ws2tcpip.h must be included by the external interface. */ | ||
|
||
#ifdef WIN32 |
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.
Maybe this should be _WIN32 instead? I see the CI failed because on the include in line 96, which wouldn't happen if we entered through here.
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.
I did this change after failure, and now it seems to be fixed.
The SmartOS failures are really weird:
We don't compile those files (acountry, adig and ahost) ?! |
Ah, wait, you did have them before! indutny@f4cc5cd maybe run the CI again? (after fixing the _WIN32 thing) |
@saghul The patch at emotional-engineering/c-ares@e701b9a was posted on the c-ares mailing list, but no one picked it up from the looks of it. |
Is there a reason we're bumping cares? Bug fixes? Performance improvements? |
PR-URL: nodejs#5090 Reviewed-By: Fedor Indutny <fedor@indutny.com>
@silverwind you should give it another try, they seems to be much more responsive now. @jbergstroem we had a floating patch, and now c-ares team has landed it with fixes. In such cases we usually update to the latest upstream. |
@indutny hang on, did they land the patch you wrote a year ago? This should also mean we can start (optionally) linking against it again? 👍 |
@jbergstroem yeah, we can start linking against it after we will land this one. Though, I'm not sure if new version was already released, but it is in c-ares repo: c-ares/c-ares@53c2186 |
@jbergstroem and it was 2 years ago 😉 |
Huh, @bnoordhuis somehow I didn't get email notification from your last comment. Sorry about this, but thank you for reviewing it! |
No biggie. I've noticed GH notifications come in with a 30-60 minute delay today. |
PR-URL: #5090 Reviewed-By: Saúl Ibarra Corretgé <saghul@gmail.com>
PR-URL: #5090 Reviewed-By: Fedor Indutny <fedor@indutny.com>
PR-URL: #5090 Reviewed-By: Saúl Ibarra Corretgé <saghul@gmail.com>
PR-URL: #5090 Reviewed-By: Fedor Indutny <fedor@indutny.com>
PR-URL: nodejs#5090 Reviewed-By: Fedor Indutny <fedor@indutny.com>
PR-URL: #5090 Reviewed-By: Fedor Indutny <fedor@indutny.com>
PR-URL: nodejs#5090 Reviewed-By: Fedor Indutny <fedor@indutny.com>
PR-URL: nodejs#5090 Reviewed-By: Saúl Ibarra Corretgé <saghul@gmail.com>
PR-URL: nodejs#5090 Reviewed-By: Fedor Indutny <fedor@indutny.com>
PR-URL: nodejs#5090 Reviewed-By: Fedor Indutny <fedor@indutny.com>
Was 72c5458: PR-URL: nodejs#5090 Reviewed-By: Fedor Indutny <fedor@indutny.com> Reimplemented for c-ares 1.13.0 PR-URL: nodejs#15378
Was 72c5458: PR-URL: nodejs/node#5090 Reviewed-By: Fedor Indutny <fedor@indutny.com> Reimplemented for c-ares 1.13.0 PR-URL: nodejs/node#15378 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Was 72c5458: PR-URL: nodejs#5090 Reviewed-By: Fedor Indutny <fedor@indutny.com> Reimplemented for c-ares 1.13.0 PR-URL: nodejs#15378 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Was 72c5458: PR-URL: nodejs#5090 Reviewed-By: Fedor Indutny <fedor@indutny.com> Reimplemented for c-ares 1.13.0 PR-URL: nodejs#15378 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> PR-URL: nodejs#19939 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Was 72c5458: PR-URL: #5090 Reviewed-By: Fedor Indutny <fedor@indutny.com> Reimplemented for c-ares 1.13.0 PR-URL: #15378 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> PR-URL: #19939 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Was 72c5458: PR-URL: nodejs#5090 Reviewed-By: Fedor Indutny <fedor@indutny.com> Reimplemented for c-ares 1.13.0 PR-URL: nodejs#15378 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> PR-URL: nodejs#19939 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
R= @bnoordhuis
cc @nodejs/collaborators