GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||
GeezerVison is showing github.com — v6.10.3 proposal by MylesBorins · Pull Request #12498 · nodejs/node Conversation
|
|
@sam-github how did you generate this list? Most of those have not landed for a variety of reasons
FWIW it is not important that EVERYTHING that can backport makes it to each release, more so that we make a good effort to land them. Please feel free to audit your list and land anything that obviously should land. Randomly clicking on handful had them all in one of the states of LTS-purgatory, perhaps we need a label for things in that stage to filter |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@MylesBorins I forgot to exclude the backport-requested, oops. Updated: So, I think what's left either should land or is not yet labelled. I know many of the PRs have comments from you asking if they should land ("LTS purgatory"), so they are not yet labelled as to their disposition because its unknown. Maybe a label for that would be useful, maybe that's what |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@sam-github that's what I've been using LTS watch for... fwiw now that I've cut the RC I do not plan to backport anything else unless it is an obvious bug or fix. We can start landing other stuff in staging once the release goes out |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
PR-URL: #11286 Fixes: #11244 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ron Korving <[email protected]>
#11863 adds _O_RDWR to node.cc which is defined in fcntl.h. This adds this include directly to node.cc. PR-URL: #12540 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Myles Borins <[email protected]>
This commit adds lldbinit files from upstream V8 and also adds these so
that they get installed when `make install` is run.
Original commit message:
[tools] add lldbinit
The goal of this commit is to add the equivalent to gdbinit but
for lldb. I've tried to replicate the commands as close as possible
but I'm unsure about the jss command and hoping to get some feedback
on it in addition to the bta command which I'm not sure how/when
this could be used. This is probably just inexperience on my part.
The lldbinit file can be placed into a directory prefixed with dot
(.lldbinit) and the python script is currently expected to be in the
same directory. The path to the script can be changed manually if
needed as well.
NOTRY=true
Review-Url: https://codereview.chromium.org/2758373002
Cr-Commit-Position: refs/heads/master@{#44136}
PR-URL: #12061
Reviewed-By: Ben Noordhuis <[email protected]>
* Replace `var` by `const`. * Fix semicolons. * Add missing code marks. * Unify quotes. * Comment out ellipsis. * Use object destructuring. * Replace snake_case by camelCase. Backport-PR-URL: #12500 PR-URL: #12224 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Alexey Orlenko <[email protected]>
Also allows someone to reassign `$RM`, e.g. with `RM=rm -v` instead of `rm -f` (the default) should they want to. We're currently using a mixture of `$(RM)` and `rm -f`. There are a couple of places which aren't doing -f, have them do it for consistency. Backport-PR-URL: #12515 PR-URL: #12157 Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Johan Bergström <[email protected]>
Original commit message:
Don't treat catch scopes as possibly-shadowing for sloppy eval
Scope analysis is over-conservative when treating variable
resolutions as possibly-shadowed by a sloppy eval. In the attached
bug, this comes into play since catch scopes have different behavior
with respect to the "calls eval" in eager vs lazy compilation (in
the latter, they are never marked as "calls eval" because
CatchContexts don't have an associated ScopeInfo).
This patch changes the scope-type check to also eliminate a few
other cases where shadowing isn't possible, such as non-declaration
block scopes.
BUG=chromium:608279
LOG=n
Committed:
https://crrev.com/75f2d65f003ebb22815489e9970913ba37234f1b
Cr-Commit-Position: refs/heads/master@{#36046}
Fixes: #12308
PR-URL: #12535
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
21b1929 to
0440447
Compare
Change var to const/let. Simplify test-timers-uncaught-exception. Backport-PR-URL: #12401 PR-URL: #10524 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Jeremiah Senkpiel <[email protected]>
0440447 to
d90a948
Compare
Notable Changes: Coming Soon PR-URL: #12498
There was an error while loading. Please reload this page.
|
ci: https://ci.nodejs.org/job/node-test-pull-request/7650/ rc.1: https://nodejs.org/download/rc/v6.10.3-rc.1/ edit: CI is looking good but we have an absurd amount of failures on citgm |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
citgm issue addressed @ nodejs/citgm#399 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
One more run: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/744/ thanks @gibfahn |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
This reverts commit 587857e. It was found to have subtle behavior changes in deleting objects. PR-URL: #12721 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Franziska Hinkelmann <[email protected]>
d90a948 to
9ecb9e0
Compare
Notable Changes: Coming Soon PR-URL: #12498
There was an error while loading. Please reload this page.
|
rc.2: https://nodejs.org/download/rc/v6.10.3-rc.2/ ci: https://ci.nodejs.org/job/node-test-pull-request/7743/ |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Review of failures ubuntu1604-64
fedora 22:
fedora 23
To Be Continued in an edit |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
One more for prosperity https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/755/ |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
All CITGM failures are expected. @nodejs/build as mentioned in other thread we should get to the bottom of the inconsistent failures with uglify |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Notable Changes:
* module:
- The module loading global fallback to the Node executable's
directory now works correctly on Windows.
(Richard Lau) #9283
* src:
- fix base64 decoding in rare edgecase
(Nikolai Vavilov) #11995
* tls:
- fix rare segmentation faults when using TLS
* (Trevor Norris) #11947
* (Ben Noordhuis) #11898
* (jBarz) #11776
PR-URL: #12497
9ecb9e0 to
a0bfd4f
Compare
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.