- Jul 12, 2020
-
-
Robert Nagy authored
Cleans up Readable.wrap and also ensures destroy is called for certain events. PR-URL: https://github.com/nodejs/node/pull/34204 Reviewed-By:
Anna Henningsen <anna@addaleax.net> Reviewed-By:
Luigi Pinca <luigipinca@gmail.com> Reviewed-By:
James M Snell <jasnell@gmail.com>
-
cjihrig authored
Notable changes: - A probable compiler bug in VS2019 was causing a failed assertion in libuv which appeared to the user as though the system clock was drifting. The `uv_hrtime()` code on Windows has been rearranged to work around the issue. - On Linux, `uv_loadavg()` attempts to read from `/proc/loadavg` before falling back to calling `sysinfo()`. This works around a bug in LXC. - A deadlock in the Windows TTY code has been fixed. - An issue on macOS related to monotonic clocks jumping back in time has been worked around. PR-URL: https://github.com/nodejs/node/pull/34187 Reviewed-By:
David Carlier <devnexen@gmail.com> Reviewed-By:
Richard Lau <riclau@uk.ibm.com> Reviewed-By:
Rich Trott <rtrott@gmail.com> Reviewed-By:
Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By:
Jiawen Geng <technicalcute@gmail.com> Reviewed-By:
Bartosz Sosnowski <bartosz@janeasystems.com>
-
cjihrig authored
Update ESLint to 7.4.0 PR-URL: https://github.com/nodejs/node/pull/34205 Reviewed-By:
Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By:
-
- Jul 11, 2020
-
-
James M Snell authored
PR-URL: https://github.com/nodejs/node/pull/34262 Reviewed-By:
-
James M Snell authored
PR-URL: https://github.com/nodejs/node/pull/34262 Reviewed-By:
-
James M Snell authored
Stop the madness. Only you can prevent excessive error code proliferation. PR-URL: https://github.com/nodejs/node/pull/34262 Reviewed-By:
-
- Jul 10, 2020
-
-
Ruy Adorno authored
PR-URL: https://github.com/nodejs/node/pull/34297 Reviewed-By:
Beth Griggs <Bethany.Griggs@uk.ibm.com> Reviewed-By:
Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By:
-
Rich Trott authored
I emailed with Kyle and they indicated a move to emeritus would be ok at this point in time. PR-URL: https://github.com/nodejs/node/pull/34258 Reviewed-By:
Anto Aravinth <anto.aravinth.cse@gmail.com> Reviewed-By:
Tobias Nießen <tniessen@tnie.de>
-
Guy Bedford authored
PR-URL: https://github.com/nodejs/node/pull/34117 Reviewed-By:
Jan Krems <jan.krems@gmail.com> Reviewed-By:
Bradley Farias <bradley.meck@gmail.com>
-
Benjamin Coe authored
Original commit message: [coverage] remove the last continuation range before synthetic return Rather than only removing the continuation range for the last return statement prior to a synthetic return statement, remove the continuation tracking for whatever statement occurs prior to the synthetic return. Bug: v8:10628 Change-Id: Ieb8e393479c9811cf1b9756840bbfdbe7f44a1b8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2280585 Commit-Queue: Benjamin Coe <bencoe@google.com> Reviewed-by:Toon Verwaest <verwaest@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#68719} Refs: https://github.com/v8/v8/commit/2d5017a0fc0203c9657394e7f86158bac8440ba4 PR-URL: https://github.com/nodejs/node/pull/34272 Refs: https://github.com/bcoe/c8/issues/229 Reviewed-By:
Gus Caplan <me@gus.host>
-
- Jul 09, 2020
-
-
James M Snell authored
Fixes: https://github.com/nodejs/node/issues/29739 PR-URL: https://github.com/nodejs/node/pull/34222 Reviewed-By:
-
James M Snell authored
Fixes: https://github.com/nodejs/node/issues/22804 PR-URL: https://github.com/nodejs/node/pull/34221 Reviewed-By:
Trivikram Kamat <trivikr.dev@gmail.com>
-
James M Snell authored
Fixes: https://github.com/nodejs/node/issues/29714 PR-URL: https://github.com/nodejs/node/pull/34223 Reviewed-By:
-
James M Snell authored
Fixes: https://github.com/nodejs/node/issues/8569 PR-URL: https://github.com/nodejs/node/pull/34227 Reviewed-By:
Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By:
-
James M Snell authored
Fixes: https://github.com/nodejs/node/issues/32431 PR-URL: https://github.com/nodejs/node/pull/34220 Reviewed-By:
-
James M Snell authored
Fixes: https://github.com/nodejs/node/issues/31244 PR-URL: https://github.com/nodejs/node/pull/34225 Reviewed-By:
-
James M Snell authored
Fixes: https://github.com/nodejs/node/issues/31279 PR-URL: https://github.com/nodejs/node/pull/34226 Reviewed-By:
-
James M Snell authored
PR-URL: https://github.com/nodejs/node/pull/34247 Reviewed-By:
-
James M Snell authored
PR-URL: https://github.com/nodejs/node/pull/34247 Reviewed-By:
-
James M Snell authored
PR-URL: https://github.com/nodejs/node/pull/34247 Reviewed-By:
-
James M Snell authored
PR-URL: https://github.com/nodejs/node/pull/34247 Reviewed-By:
-
James M Snell authored
PR-URL: https://github.com/nodejs/node/pull/34247 Reviewed-By:
-
James M Snell authored
Some of the flags were no longer being used. Switched to use an AliasedStruct for shared state to avoid extraneous expensive JS=>C++ calls. Removed unused QuicSocket option PR-URL: https://github.com/nodejs/node/pull/34247 Reviewed-By:
-
James M Snell authored
PR-URL: https://github.com/nodejs/node/pull/34247 Reviewed-By:
-
Anna Henningsen authored
0f97d606 accidentally removed this. Refs: https://github.com/nodejs/node/pull/34186 PR-URL: https://github.com/nodejs/node/pull/34247 Reviewed-By:
-
James M Snell authored
PR-URL: https://github.com/nodejs/node/pull/34247 Reviewed-By:
-
James M Snell authored
PR-URL: https://github.com/nodejs/node/pull/34247 Reviewed-By:
-
James M Snell authored
PR-URL: https://github.com/nodejs/node/pull/34247 Reviewed-By:
-
James M Snell authored
PR-URL: https://github.com/nodejs/node/pull/34247 Reviewed-By:
-
James M Snell authored
Also, change setServerBusy into a setter PR-URL: https://github.com/nodejs/node/pull/34247 Reviewed-By:
-
James M Snell authored
Errors thrown within the session event handler will be handled by destroying the session (allowing a proper connection close to be sent to the client peer). They will not crash the parent QuicSocket by default. Instead, a `'sessionError'` event will be emitted, allowing the error to be logged or handled. PR-URL: https://github.com/nodejs/node/pull/34247 Reviewed-By:
-
James M Snell authored
The argument will always be a boolean already PR-URL: https://github.com/nodejs/node/pull/34247 Reviewed-By:
-
James M Snell authored
PR-URL: https://github.com/nodejs/node/pull/34247 Reviewed-By:
-
Robert Nagy authored
PR-URL: https://github.com/nodejs/node/pull/34143 Reviewed-By:
-
rickyes authored
PR-URL: https://github.com/nodejs/node/pull/33991 Fixes: https://github.com/nodejs/node/issues/33582 Reviewed-By:
Denys Otrishko <shishugi@gmail.com> Reviewed-By:
Matteo Collina <matteo.collina@gmail.com> Reviewed-By:
Robert Nagy <ronagy@icloud.com>
-
Rich Trott authored
PR-URL: https://github.com/nodejs/node/pull/34228 Reviewed-By:
-
Gabriel Schulhof authored
Add assertions that conversion and coercion N-APIs return appropriate error statuses when given `NULL`s for parameters they expect to not be `NULL`. For `napi_get_value_string_*` this also checks that it returns `napi_string_expected` when passed a `napi_value` not containing a string. PR-URL: https://github.com/nodejs/node/pull/34142 Reviewed-By:
-
- Jul 08, 2020
-
-
Johannes Schöpp authored
Powershell defaults to tls 1.0 - This forces powershell to use tls 1.2 Tls 1.2 is supported in all current microsoft operating systems and needed to download chocolatey. Fixes: https://github.com/nodejs/node/issues/33140 PR-URL: https://github.com/nodejs/node/pull/33609 Reviewed-By:
-
rickyes authored
PR-URL: https://github.com/nodejs/node/pull/34156 Reviewed-By:
-
Xu Meng authored
Due to some unknown system configuration, the code `socket_ipv6.bind(0, 111::1)` does not throw the expected error EADDRNOTAVAIL on some IBM i systems. This issue is still being investigated. To get the IBM i CI passing, skip it for now. PR-URL: https://github.com/nodejs/node/pull/34209 Reviewed-By:
-
