| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
This error code export was mistakingly introduced in a 2012 commit which added more error codes. The correct export.BADNAME was added in nodejs#3051. Semver: Major PR-URL: nodejs#3051 Fixes: nodejs#3050 Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
common.debug() is just util.debug() and emits a deprecation notice. Per docs, use console.error() instead. PR-URL: nodejs#3082 Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
common.print() is just util.print() and as such prints a deprecation warning. Per docs, update to console.log(). PR-URL: nodejs#3083 Reviewed-By: Michaël Zasso <mic.besace@gmail.com> Reviewed-By: Brendan Ashworth <brendan.ashworth@me.com>
Bye bye, smalloc. I'm not sure why this was still here; it was removed in 70d1f32 and hasn't worked since. It wasn't packaged in the binary, either. Reviewed-By: Michaël Zasso <mic.besace@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> PR-URL: nodejs#3099
Very minor update in benchmark/common.js Not exactly a critical change, just continued cleaning out of old joyent/node PRs that never landed. Ref: nodejs/node-v0.x-archive#8515 PR-URL: nodejs#2399 Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Brendan Ashworth <brendan.ashworth@me.com> Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Notable changes
|
55a1f94e44 ("remove nonexistant exports.ADNAME") is for v5.x? |
Sorry, something went wrong.
|
@alexlamsl yes, it's semver-major, even though trivial These are the commits on master that are not coming over to v4.x:
|
Sorry, something went wrong.
|
argh, I see what you were getting at, it's listed above ... @silverwind has mistakenly marked it as PR-URL #3051 but it's actually #3076. I'll remove it from v4.x. |
Sorry, something went wrong.
|
ok, force pushed v4.x and this PR to remove the offending commit, thanks for picking that up @alexlamsl! |
Sorry, something went wrong.
Sorry, something went wrong.
|
+1 to libuv and v8 if CI is happy. |
Sorry, something went wrong.
|
yes to the libuv and v8 updates, just get some lgtm's on those and merge them in to master and it'll happen |
Sorry, something went wrong.
|
@cjihrig don't let this release stop you from landing semver-minor in master, I'm just going to avoid cherry-picking those for this one. They'll get in to v4.2.0 which will probably be the final semver-major for v4.x |
Sorry, something went wrong.
|
FYI I posted a comment here #3000 (comment) about timing of v4.1.2 and v4.2.0 and how LTS and v5 is likely going to play out according to current policies and TSC decisions. |
Sorry, something went wrong.
|
Current list of commits in OP is up to date, I think I'm going to stop cherry-picking and this list is near-final minus an embargoed change for #3138 that's still being tested. Will work on Notable Changes list soon. |
Sorry, something went wrong.
Notable changes
Part of the Notable Changes section going out shortly for 4.1.2 |
Sorry, something went wrong.
Changes to `stream_base.cc` are required to support empty writes. Fixes CVE-2015-7384, #3138 Fix: #2639 PR-URL: #3128
Account pending response data to decide whether pause the socket or not. Writable stream state is a not reliable measure, because it just says how much data is pending on a **current** request, thus not helping much with problem we are trying to solve here. PR-URL: #3128
Decrement `vcount` in `DoTryWrite` even if some of the buffers are empty. PR-URL: #3128
Notable changes
* http:
- Fix out-of-order 'finish' event bug in pipelining that can abort
execution, fixes DoS vulnerability CVE-2015-7384
(Fedor Indutny) #3128
- Account for pending response data instead of just the data on the
current request to decide whether pause the socket or not
(Fedor Indutny) #3128
* libuv: Upgraded from v1.7.4 to v1.7.5, see release notes for details
(Saúl Ibarra Corretgé) #3010
- A better rwlock implementation for all Windows versions
- Improved AIX support
* v8:
- Upgraded from v4.5.103.33 to v4.5.103.35 (Ali Ijaz Sheikh) #3117
- Backported f782159 from v8's upstream to help speed up Promise
introspection (Ben Noordhuis) #3130
- Backported c281c15 from v8's upstream to add JSTypedArray length
in post-mortem metadata (Julien Gilli) #3031
PR-URL: #3128
|
v4.1.2 released, even ARMv6 binaries are available now without the usual delay. |
Sorry, something went wrong.
Related: nodejs/docker-node#49 Related: nodejs/node#3128
Changes to `stream_base.cc` are required to support empty writes. Fixes CVE-2015-7384, nodejs#3138 Fix: nodejs#2639 PR-URL: nodejs#3128
Account pending response data to decide whether pause the socket or not. Writable stream state is a not reliable measure, because it just says how much data is pending on a **current** request, thus not helping much with problem we are trying to solve here. PR-URL: nodejs#3128
Decrement `vcount` in `DoTryWrite` even if some of the buffers are empty. PR-URL: nodejs#3128
Notable changes
* http:
- Fix out-of-order 'finish' event bug in pipelining that can abort
execution, fixes DoS vulnerability CVE-2015-7384
(Fedor Indutny) nodejs#3128
- Account for pending response data instead of just the data on the
current request to decide whether pause the socket or not
(Fedor Indutny) nodejs#3128
Notable changes
* http:
- Fix out-of-order 'finish' event bug in pipelining that can abort
execution, fixes DoS vulnerability CVE-2015-7384
(Fedor Indutny) #3128
- Account for pending response data instead of just the data on the
current request to decide whether pause the socket or not
(Fedor Indutny) #3128
Related: nodejs/docker-node#49 Related: nodejs/node#3128
Changes to `stream_base.cc` are required to support empty writes. Fixes CVE-2015-7384, nodejs/node#3138 Fix: nodejs/node#2639 PR-URL: nodejs/node#3128
Account pending response data to decide whether pause the socket or not. Writable stream state is a not reliable measure, because it just says how much data is pending on a **current** request, thus not helping much with problem we are trying to solve here. PR-URL: nodejs/node#3128
Decrement `vcount` in `DoTryWrite` even if some of the buffers are empty. PR-URL: nodejs/node#3128
Notable changes
* http:
- Fix out-of-order 'finish' event bug in pipelining that can abort
execution, fixes DoS vulnerability CVE-2015-7384
(Fedor Indutny) #3128
- Account for pending response data instead of just the data on the
current request to decide whether pause the socket or not
(Fedor Indutny) #3128
* libuv: Upgraded from v1.7.4 to v1.7.5, see release notes for details
(Saúl Ibarra Corretgé) #3010
- A better rwlock implementation for all Windows versions
- Improved AIX support
* v8:
- Upgraded from v4.5.103.33 to v4.5.103.35 (Ali Ijaz Sheikh) #3117
- Backported f782159 from v8's upstream to help speed up Promise
introspection (Ben Noordhuis) #3130
- Backported c281c15 from v8's upstream to add JSTypedArray length
in post-mortem metadata (Julien Gilli) #3031
PR-URL: nodejs/node#3128
| Back | FazBrowse Home | New Git URL |
Aiming for Monday release. This is not the release where we shift to LTS, that'll probably be soon after.
Some important bugfixes still need to be finalised for this release yet.