Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2016-10-11, Version 6.8.0 (Current) #9034

Merged
merged 216 commits into from
Oct 12, 2016
Merged

2016-10-11, Version 6.8.0 (Current) #9034

merged 216 commits into from
Oct 12, 2016

Conversation

Fishrock123
Copy link
Contributor

@Fishrock123 Fishrock123 commented Oct 11, 2016

This week's release. Aiming for tomorrow.

CI: https://ci.nodejs.org/job/node-test-pull-request/4469/
CITGM: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/410/

todo: Notable Changes

zkat and others added 30 commits September 29, 2016 15:21
PR-URL: #8706
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
PR-URL: #8706
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Should help with #8034.

PR-URL: #8528
Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
This test executes a simple debug session over the inspector protocol.

PR-URL: #8429
Reviewed-By: ofrobots - Ali Ijaz Sheikh <ofrobots@google.com>
Ctor has to be added as memset to 0 is no longer an option, since
the structure now has std::vector member.

Attempt at fixing #8155 (so far I was not able to repro it)

PR-URL: #8536
Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
Fixes: #8426
PR-URL: #8502
Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
Removes race condition when test relied on both sides of the socket
to be closed on the same UV event loop iteration.

Fixes: #8498
PR-URL: #8505
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Saúl Ibarra Corretgé <saghul@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-by: Fedor Indutny <fedor@indutny.com>
Embed the compressed and minified protocol.json from the bundled
v8_inspector and make it available through the /json/protocol endpoint.

Refs: nodejs/diagnostics#52
PR-URL: #7491
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Stress tests uncovered 2 race conditions, when IO events happened during
V8 entering event loop on pause or during Node.js shutdown.

Fixes: #8669
PR-URL: #8672
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
Remove obsolete build file entries.

Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Ilkka Myller <ilkka.myller@nodefield.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
PR-URL: #8753
PR-URL: #8835
Reviewed-By: Eugene Ostroukhov <eostroukhov@google.com>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Add example to show what running Node.js with `--inspect`
should look like.

Some IDEs do not show the link when running with `--inspect`.
This example hints to what the full output looks like.

PR-URL: #8845
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
The patch should have been bumped in aafc314 but it was missed.

Ref: aafc314
Ref: #8673

PR-URL: #8851
Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: #8525
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Evan Lucas <evanlucas@me.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Increase time allowed for startup from 1 second to 5 seconds to avoid
occasional flakiness. While at it, refactor a few minor things such as
var->const and using common.mustCall().

Fixes: #8483
PR-URL: #8484
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #8485
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Signed-off-by: Ilkka Myller <ilkka.myller@nodefield.com>

PR-URL: #8530
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
PR-URL: #8533
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Johan Bergström <bugs@bergstroem.nu>
PR-URL: #8489
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #8487
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Remove a duplicate sentence from the `rl.close()` method description.

PR-URL: #8497
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Prince John Wesley <princejohnwesley@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
`Client.prototype._addHandle()` in the `_debugger` module has conditions
around invalid properties that are not currently tested. This change
adds some minimal unit tests.

PR-URL: #8518
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Replace the description of the commit message requirements in
onboarding.md with a link to the commit message requirements as they
appear in the CONTRIBUTING.md.

Advantages include:

* Only one place to keep the commit message requirements up to date
* Most collaborators being onboarded will already have several commits
  in their name and already be familiar with the requirements. So
  repeating information here makes finding the new information (about
  metadata, for example) harder to find.

PR-URL: #8529
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Johan Bergström <bugs@bergstroem.nu>
Reviewed-By: Ilkka Myller <ilkka.myller@nodefield.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Wait for a sought-for symbol to appear instead of just hard-killing
subprocesses at 2s timeout.

Fix: #4427
PR-URL: #8542
Reviewed-By: Rich Trott <rtrott@gmail.com>
- Added dots to printed commands.
- Use spaces instead of tabs so there's no misalignment on terminals
  with a tab size other than 4.
- Improved the help text for .editor and .help.
- Automatically indent command help based on the longest command.

PR-URL: #8519
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Prince John Wesley <princejohnwesley@gmail.com>
Reviewed-By: Ilkka Myller <ilkka.myller@nodefield.com>
Previously, an attempt was made to make sure the links state is
inherited. Unfortunately, this support was not complete, which
results in various unresolved links in the JSON output (as an
example, [1] contains `initialized by calling
[<code>buf.fill(fill, encoding)</code>][<code>buf.fill()</code>]`).

This commit completes that attempt. After this commit, individual
instances of the parser (for descriptions) inherit the links state
from the root lexer, so that individual Markdown links in descriptions
could be resolved. That same example is now substituted with
`initialized by calling <a href=\"#buffer_buf_fill_value_offset_end_encoding\"><code>buf.fill(fill, encoding)</code></a>`.

[1]: https://nodejs.org/api/buffer.json

PR-URL: #8494
Reviewed-By: Roman Reiss <me@silverwind.io>
On line 40: replace '==' with '==='

On line 52: replace 'assert.equal' with 'assert.strictEqual'

Added some comments.

Changed 'var' to 'const' where possible.

Replaced console.log(res.statusCode); with and assertion.

Rather than logging the https request status on every loop it will now
assert the https status is correct on every loop.

Changed the error listener to throw the error rather than log it.

PR-URL: #8517
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Fixes: #8440
PR-URL: #8510
Reviewed-By: Brian White <mscdex@mscdex.net>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
It was treated as a link to "e.g. `Uint8Array.from()`".

PR-URL: #8553
Reviewed-By: Brian White <mscdex@mscdex.net>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Bryan English <bryan@bryanenglish.com>
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
PR-URL: #8557
Reviewed-By: Brian White <mscdex@mscdex.net>
Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Evan Lucas <evanlucas@me.com>
Reviewed-By: Prince John Wesley <princejohnwesley@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
cjihrig and others added 4 commits October 11, 2016 12:52
This commit adds a test for the killSignal option to spawnSync(),
and the other sync child process functions by extension.

PR-URL: #8960
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: #8941
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Make the internal `SyncWriteStream` a proper `stream.Writable`
subclass. This allows for quite a bit of simplification, since
`SyncWriteStream` predates the streams2/streams3 implementations.

Fixes: #8828
PR-URL: #8830
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>

(backport info)
Refs: #9030
PR-URL: #9029
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
@Fishrock123 Fishrock123 added meta Issues and PRs related to the general management of the project. v6.x labels Oct 11, 2016
@Fishrock123 Fishrock123 added this to the v6.8.0 milestone Oct 11, 2016
@nodejs-github-bot nodejs-github-bot added meta Issues and PRs related to the general management of the project. v6.x labels Oct 11, 2016
@Fishrock123
Copy link
Contributor Author

@nodejs/platform-freebsd & @nodejs/platform-solaris any idea what's up?

LOTS of freebsd errors :S

also cc @nodejs/build, are there freebsd problems right now?

@jbergstroem
Copy link
Member

@Fishrock123 I've been restarting nodes left and right to sort out issues. From this state and forward they are consistent and have no known "issues" (read: wrong running user, homedir, ccache or similar): https://ci.nodejs.org/job/node-test-commit-freebsd/4766/

@jbergstroem
Copy link
Member

Looking at smartos hosts I also see a heap of stalling processes :/

@addaleax
Copy link
Member

I think this PR should target v6.x?

@Fishrock123 Fishrock123 changed the base branch from v6.x-staging to v6.x October 12, 2016 14:07
@Fishrock123
Copy link
Contributor Author

@thealphanerd looks like citgm ran out of memory here: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/410/nodes=fedora22/testReport/(root)/citgm/async_v2_0_1/

       > async@2.0.1 test /tmp/1731806a-89ae-425e-95f3-6b0ea3001319/async
 > npm run-script lint && npm run mocha-node-test
 > async@2.0.1 lint /tmp/1731806a-89ae-425e-95f3-6b0ea3001319/async
 > eslint lib/ mocha_test/ perf/memory.js perf/suites.js perf/benchmark.js support/build/ support/*.js karma.conf.js
 > async@2.0.1 mocha-node-test /tmp/1731806a-89ae-425e-95f3-6b0ea3001319/async
 > mocha mocha_test/ --compilers js:babel-core/register
 <--- Last few GCs --->
    16939 ms: Mark-sweep 727.1 (1067.6) -> 717.0 (1063.6) MB, 281.4 / 0.0 ms [allocation failure] [GC in old space requested].
    17211 ms: Mark-sweep 717.0 (1063.6) -> 714.5 (1067.6) MB, 272.0 / 0.0 ms [allocation failure] [GC in old space requested].
    17485 ms: Mark-sweep 714.5 (1067.6) -> 711.7 (1010.6) MB, 273.7 / 0.0 ms [last resort gc].
    17761 ms: Mark-sweep 711.7 (1010.6) -> 711.6 (992.6) MB, 276.1 / 0.0 ms [last resort gc].
 <--- JS stacktrace --->
 ==== JS stack trace =========================================
 Security context: 0x276a119cfb51 <JS Object>
     1: SparseJoinWithSeparatorJS(aka SparseJoinWithSeparatorJS) [native array.js:~75] [pc=0x272751feae57] (this=0x276a11904381 <undefined>,w=0x3d4cd0651af1 <JS Array[15083]>,F=0x27daa1f90299 <JS Array[15083]>,x=15083,I=0x276a119b46e1 <JS Function ConvertToString (SharedFunctionInfo 0x276a11952dc9)>,J=0x27daa1f90259 <String[4]\: ,\n  >)
     2: DoJoin(aka DoJoin) [native array.js:137] [pc=0x27275...
 FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
  1: node::Abort() [/home/iojs/build/workspace/citgm-smoker/nodes/fedora22/smoker/bin/node]
  2: 0x108c17c [/home/iojs/build/workspace/citgm-smoker/nodes/fedora22/smoker/bin/node]
  3: v8::Utils::ReportApiFailure(char const*, char const*) [/home/iojs/build/workspace/citgm-smoker/nodes/fedora22/smoker/bin/node]
  4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/home/iojs/build/workspace/citgm-smoker/nodes/fedora22/smoker/bin/node]
  5: v8::internal::Factory::NewRawTwoByteString(int, v8::internal::PretenureFlag) [/home/iojs/build/workspace/citgm-smoker/nodes/fedora22/smoker/bin/node]
  6: v8::internal::Runtime_SparseJoinWithSeparator(int, v8::internal::Object**, v8::internal::Isolate*) [/home/iojs/build/workspace/citgm-smoker/nodes/fedora22/smoker/bin/node]
  7: 0x2727512092a7
 sh: line 1:  2073 Aborted                 (core dumped) npm run mocha-node-test
 npm ERR! Test failed.  See above for more details.

@Fishrock123
Copy link
Contributor Author

@Fishrock123
Copy link
Contributor Author

@Fishrock123
Copy link
Contributor Author

Also some interesting output at https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/411/nodes=fedora22/testReport/(root)/citgm/ember_cli_v2_8_0/ but seems unrelated... I hope.

* fs:
  - `SyncWriteStream` now inherits from `Stream.Writable`. (Anna
Henningsen) #8830
    - Practically, this means that when stdio is piped to a file,
stdout and stderr will still be `Writable` streams.
  - `fs.existsSync()` has been undeprecated. `fs.exists()` remains
deprecated. (Dan Fabulich) #8364
* http: `http.request()` now accepts a `timeout` option. (Rene Weber)
#8101
* module: The module loader now maintains its own realpath cache. (Anna
Henningsen) #8100
* npm: Upgraded to 3.10.8 (Kat Marchán)
#8706
* stream: `Duplex` streams now show proper `instanceof
Stream.Writable`. (Anna Henningsen)
#8834
* timers: Improved `setTimeout`/`Interval` performance by up to 22%.
(Brian White) #8661

PR-URL: #9034
@Fishrock123
Copy link
Contributor Author

@Fishrock123 Fishrock123 merged commit 17145bd into v6.x Oct 12, 2016
Fishrock123 added a commit that referenced this pull request Oct 12, 2016
Fishrock123 added a commit that referenced this pull request Oct 12, 2016
* fs:
  - `SyncWriteStream` now inherits from `Stream.Writable`. (Anna
Henningsen) #8830
    - Practically, this means that when stdio is piped to a file,
stdout and stderr will still be `Writable` streams.
  - `fs.existsSync()` has been undeprecated. `fs.exists()` remains
deprecated. (Dan Fabulich) #8364
* http: `http.request()` now accepts a `timeout` option. (Rene Weber)
#8101
* module: The module loader now maintains its own realpath cache. (Anna
Henningsen) #8100
* npm: Upgraded to 3.10.8 (Kat Marchán)
#8706
* stream: `Duplex` streams now show proper `instanceof
Stream.Writable`. (Anna Henningsen)
#8834
* timers: Improved `setTimeout`/`Interval` performance by up to 22%.
(Brian White) #8661

PR-URL: #9034
Fishrock123 added a commit to nodejs/nodejs.org that referenced this pull request Oct 12, 2016
@Fishrock123
Copy link
Contributor Author

@Fishrock123 Fishrock123 deleted the v6.8.0-propose branch October 12, 2016 20:29
Fishrock123 added a commit to nodejs/nodejs.org that referenced this pull request Oct 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.