| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
LGTM |
Sorry, something went wrong.
Sorry, something went wrong.
|
Added a new commit to match the improved error message upon ArrayBuffer allocation failure. New CI: https://ci.nodejs.org/job/node-test-pull-request/1071/ looking green. @targos PTAL. /cc @skomski |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
Pick up V8 4.8 branch-head. This branch brings in @@isConcatSpreadable, @@toPrimitive and ToLength ES6 changes. For full details see: http://v8project.blogspot.de/2015/11/v8-release-48.html PR-URL: nodejs#4399 Reviewed-By: targos - Michaël Zasso <mic.besace@gmail.com>
Original commit message:
This commit adds some postmortem data that is otherwise unavailable.
I have discovered need in those values when writing:
https://github.com/indutny/llnode
BUG=
Review URL: https://codereview.chromium.org/1436473002
Cr-Commit-Position: refs/heads/master@{nodejs#31947}
This postmortem information is useful for both object inspection, and
function's context variables inspection.
Ref: nodejs#3779
PR-URL: nodejs#4106
Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: targos - Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: rvagg - Rod Vagg <rod@vagg.org>
Original commit message: [tools] Make gen-postmortem-metadata.py more reliable Instead of basing matches off of whitespace, walk the inheritance chain and include any classes that inherit from Object. R=machenbach@chromium.org,jkummerow@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1435643002 Cr-Commit-Position: refs/heads/master@{nodejs#31964} This adds some missing classes to postmortem info like JSMap and JSSet. Ref: nodejs#3792 PR-URL: nodejs#4106 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: targos - Michaël Zasso <mic.besace@gmail.com> Reviewed-By: rvagg - Rod Vagg <rod@vagg.org>
The error message returned on ArrayBuffer allocation failure is now different as per https://codereview.chromium.org/1393263003. PR-URL: nodejs#4399 Reviewed-By: targos - Michaël Zasso <mic.besace@gmail.com>
|
Landed onto a new vee-eight-4.8 branch as b123c692786c^...00251b2. |
Sorry, something went wrong.
The error message returned on ArrayBuffer allocation failure is now different as per https://codereview.chromium.org/1393263003. PR-URL: nodejs#4399 Reviewed-By: targos - Michaël Zasso <mic.besace@gmail.com>
Pick up V8 4.8 branch-head. This branch brings in @@isConcatSpreadable, @@toPrimitive and ToLength ES6 changes. For full details see: http://v8project.blogspot.de/2015/11/v8-release-48.html v8/v8@fa163e2 Ref: nodejs#4399
The error message returned on ArrayBuffer allocation failure is now different as per https://codereview.chromium.org/1393263003. Ref: nodejs#4399
Pick up V8 4.8 branch-head. This branch brings in @@isConcatSpreadable, @@toPrimitive and ToLength ES6 changes. For full details see: http://v8project.blogspot.de/2015/11/v8-release-48.html v8/v8@fa163e2 Ref: #4399 PR-URL: #4785 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
The error message returned on ArrayBuffer allocation failure is now different as per https://codereview.chromium.org/1393263003. Ref: #4399 PR-URL: #4785 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
Pick up V8 4.8 branch-head. This branch brings in @@isConcatSpreadable, @@toPrimitive and ToLength ES6 changes. For full details see: http://v8project.blogspot.de/2015/11/v8-release-48.html v8/v8@fa163e2 Ref: nodejs#4399 PR-URL: nodejs#4785 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
The error message returned on ArrayBuffer allocation failure is now different as per https://codereview.chromium.org/1393263003. Ref: nodejs#4399 PR-URL: nodejs#4785 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
| Back | FazBrowse Home | New Git URL |
Do not land on master
Pick up V8 4.8 into a new vee-eight-4.8 branch so that we can start testing with this V8 version. This branch brings in @@isConcatSpreadable, @@toPrimitive and ToLength ES6 changes. For full details see:
http://v8project.blogspot.de/2015/11/v8-release-48.html
There are no API changes anticipated in this branch.
/cc @nodejs/v8