Uh oh!
There was an error while loading. Please reload this page.
deps: upgrade libuv to 1.12.0 - #13306
Conversation
Solves #12853. As far as I see it, it's the only issue closed by the upgrade. |
There was a problem hiding this comment.
Surely this file can be ignored?
I believe one of the oldest still-open issues, #854, is fixed by this? Assuming |
bnoordhuis
left a comment
There was a problem hiding this comment.
LGTM
Anyone have opinions on whether to gitignore the uvbook files in docs/code and docs/src/guide? It adds another ~100 kB to the tarball (240 kB uncompressed) and I don't expect many people will look at it.
Important change: this version of libuv raises the minimum supported version from linux 2.6.18 + glibc 2.5 to linux 2.6.32 + glibc 2.12.
The support code for older systems is still there but going forward we won't bend over backwards to keep it in working shape.
jasnell
commented
May 30, 2017
+1 to ignoring the uvbook files |
jasnell
left a comment
There was a problem hiding this comment.
Rubber stamp LGTM but I'd like to see a CITGM run before this lands.
mhdawson
left a comment
There was a problem hiding this comment.
Rubber stamp approval from me as well provided CI passes.
cjihrig
commented
Jun 1, 2017
@bnoordhuis should the uvbook be explicitly added to .gitignore, or just not checked in? |
bnoordhuis
commented
Jun 1, 2017
@cjihrig I'd add it to the .gitignore, that prevents accidental check-ins in the future. |
cf680b8 to
59b0847Comparecjihrig
commented
Jun 1, 2017
Removed the uvbook and .github folders. PTAL |
richardlau
commented
Jun 1, 2017
We should also raise Node.js' minimum supported levels in |
871ed57 to
9b40352Comparecjihrig
commented
Jun 5, 2017
Added a commit to update |
bnoordhuis
commented
Jun 5, 2017
Still LGTM. The raised baseline might become non-academic in the future, see libuv/libuv#1372. |
Fishrock123
commented
Jun 5, 2017
@cjihrig could you please move the |
cjihrig
commented
Jun 5, 2017
Moved to separate commit. CI: https://ci.nodejs.org/job/node-test-pull-request/8482/ |
cjihrig
commented
Jun 5, 2017
CI seemed good. Ran CITGM (https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/854/). Can someone help interpreting the output? |
gibfahn
commented
Jun 5, 2017
cc/ @nodejs/citgm |
Fixes: nodejs#12853Fixes: nodejs#854 PR-URL: nodejs#13306 Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
The libuv 1.12.0 update bumped the minimum supported version of linux + glibc. This commit updates BUILDING.md to reflect the new values. PR-URL: nodejs#13306 Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
* **Async Hooks** * When one `Promise` leads to the creation of a new `Promise`, the parent `Promise` will be identified as the trigger [[`135f4e6643`](nodejs@135f4e6643)] [nodejs#13367](nodejs#13367). * **Dependencies** * libuv has been updated to 1.12.0 [[`968596ec77`](nodejs@968596ec77)] [nodejs#13306](nodejs#13306). * npm has been updated to 5.0.3 [[`ffa7debd7a`](nodejs@ffa7debd7a)] [nodejs#13487](nodejs#13487). * **File system** * The `fs.exists()` function now works correctly with `util.promisify()` [[`6e0eccd7a1`](nodejs@6e0eccd7a1)] [nodejs#13316](nodejs#13316). * fs.Stats times are now also available as numbers [[`c756efb25a`](nodejs@c756efb25a)] [nodejs#13173](nodejs#13173). * **Inspector** * It is now possible to bind to a random port using `--inspect=0` [[`cc6ec2fb27`](nodejs@cc6ec2fb27)] [nodejs#5025](nodejs#5025). * **Zlib** * A regression in the Zlib module that made it impossible to properly subclasses `zlib.Deflate` and other Zlib classes has been fixed. [[`6aeb555cc4`](nodejs@6aeb555cc4)] [nodejs#13374](nodejs#13374).
* **Async Hooks** * When one `Promise` leads to the creation of a new `Promise`, the parent `Promise` will be identified as the trigger [[`135f4e6643`](135f4e6643)] [#13367](#13367). * **Dependencies** * libuv has been updated to 1.12.0 [[`968596ec77`](968596ec77)] [#13306](#13306). * npm has been updated to 5.0.3 [[`ffa7debd7a`](ffa7debd7a)] [#13487](#13487). * **File system** * The `fs.exists()` function now works correctly with `util.promisify()` [[`6e0eccd7a1`](6e0eccd7a1)] [#13316](#13316). * fs.Stats times are now also available as numbers [[`c756efb25a`](c756efb25a)] [#13173](#13173). * **Inspector** * It is now possible to bind to a random port using `--inspect=0` [[`cc6ec2fb27`](cc6ec2fb27)] [#5025](#5025). * **Zlib** * A regression in the Zlib module that made it impossible to properly subclasses `zlib.Deflate` and other Zlib classes has been fixed. [[`6aeb555cc4`](6aeb555cc4)] [#13374](#13374).
* **Async Hooks** * When one `Promise` leads to the creation of a new `Promise`, the parent `Promise` will be identified as the trigger [[`135f4e6643`](135f4e6643)] [#13367](#13367). * **Dependencies** * libuv has been updated to 1.12.0 [[`968596ec77`](968596ec77)] [#13306](#13306). * npm has been updated to 5.0.3 [[`ffa7debd7a`](ffa7debd7a)] [#13487](#13487). * **File system** * The `fs.exists()` function now works correctly with `util.promisify()` [[`6e0eccd7a1`](6e0eccd7a1)] [#13316](#13316). * fs.Stats times are now also available as numbers [[`c756efb25a`](c756efb25a)] [#13173](#13173). * **Inspector** * It is now possible to bind to a random port using `--inspect=0` [[`cc6ec2fb27`](cc6ec2fb27)] [#5025](#5025). * **Zlib** * A regression in the Zlib module that made it impossible to properly subclasses `zlib.Deflate` and other Zlib classes has been fixed. [[`6aeb555cc4`](6aeb555cc4)] [#13374](#13374).
MylesBorins
commented
Jul 17, 2017
Can we get this backported to v6.x for a future semver minor |
MylesBorins
commented
Sep 19, 2017
@cjihrig@bnoordhuis do you see any issues with backporting this to v6.x? The minimal version of kernel + libc are slightly worrysome, but your comments appear to imply that it isn't a big deal. |
gibfahn
commented
Sep 19, 2017
Could we backport this version without backporting the supported versions update? @bnoordhuis you mentioned that it was academic for this release, and this is likely to be the last libuv update for 6.x. |
bnoordhuis
commented
Sep 19, 2017
None of the support code for old kernels was removed so yes, this is safe to back-port. |
PR-URL: #13306 Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
PR-URL: #13306 Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Notable Changes: * assert: - assert.fail() can now take one or two arguments (Rich Trott) #12293 * crypto: - add sign/verify support for RSASSA-PSS (Tobias Nießen) #11705 * deps: - upgrade openssl sources to 1.0.2m (Shigeki Ohtsu) #16691 - upgrade libuv to 1.15.0 (cjihrig) #15745 - upgrade libuv to 1.14.1 (cjihrig) #14866 - upgrade libuv to 1.13.1 (cjihrig) #14117 - upgrade libuv to 1.12.0 (cjihrig) #13306 * fs: - Add support for fs.write/fs.writeSync(fd, buffer, cb) and fs.write/fs.writeSync(fd, buffer, offset, cb) as documented (Andreas Lind) #7856 * inspector: - enable --inspect-brk (Refael Ackermann) #12615 * process: - add --redirect-warnings command line argument (James M Snell) #10116 * src: - allow CLI args in env with NODE_OPTIONS (Sam Roberts) #12028) - --abort-on-uncaught-exception in NODE_OPTIONS (Sam Roberts) #13932 - allow --tls-cipher-list in NODE_OPTIONS (Sam Roberts) #13172 - use SafeGetenv() for NODE_REDIRECT_WARNINGS (Sam Roberts) #12677 * test: - remove common.fail() (Rich Trott) #12293 PR-URL: #16263
Notable Changes: * assert: - assert.fail() can now take one or two arguments (Rich Trott) #12293 * crypto: - add sign/verify support for RSASSA-PSS (Tobias Nießen) #11705 * deps: - upgrade openssl sources to 1.0.2m (Shigeki Ohtsu) #16691 - upgrade libuv to 1.15.0 (cjihrig) #15745 - upgrade libuv to 1.14.1 (cjihrig) #14866 - upgrade libuv to 1.13.1 (cjihrig) #14117 - upgrade libuv to 1.12.0 (cjihrig) #13306 * fs: - Add support for fs.write/fs.writeSync(fd, buffer, cb) and fs.write/fs.writeSync(fd, buffer, offset, cb) as documented (Andreas Lind) #7856 * inspector: - enable --inspect-brk (Refael Ackermann) #12615 * process: - add --redirect-warnings command line argument (James M Snell) #10116 * src: - allow CLI args in env with NODE_OPTIONS (Sam Roberts) #12028) - --abort-on-uncaught-exception in NODE_OPTIONS (Sam Roberts) #13932 - allow --tls-cipher-list in NODE_OPTIONS (Sam Roberts) #13172 - use SafeGetenv() for NODE_REDIRECT_WARNINGS (Sam Roberts) #12677 * test: - remove common.fail() (Rich Trott) #12293 PR-URL: #16263
uttampawar
commented
Jun 14, 2018
Is there a timeline when this can land? Thanks. |
cjihrig
commented
Jun 14, 2018
Land where? Node 6 is the oldest supported release line and it has a newer version of libuv than this. |
uttampawar
commented
Jun 15, 2018
@cjihrig I thought that content of libuv/libuv#1372 is getting pulled in as part of this PR which I realized is not the case. I apologize for the confusion, it was misunderstanding on my part. |
If anyone knows of any Node.js issues that are resolved by this release, please link them here so they can be added to the commit metadata, and closed on landing.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesAffected core subsystem(s)
deps