- Apr 21, 2016
-
-
Bryan English authored
Clarify in docs for require.cache that reloading native modules isn't supported. Related: #6160 PR-URL: https://github.com/nodejs/node/pull/6168 Reviewed-By:
Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By:
Brian White <mscdex@mscdex.net> Reviewed-By:
James M Snell <jasnell@gmail.com>
-
Rich Trott authored
The message argument for `assert.fail()` is the third argument, not the first. Correct minor misuse in internal module. PR-URL: https://github.com/nodejs/node/pull/6211 Reviewed-By:
Brian White <mscdex@mscdex.net> Reviewed-By:
Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By:
James M Snell <jasnell@gmail.com> Reviewed-By:
Evan Lucas <evanlucas@me.com> Reviewed-By:
Colin Ihrig <cjihrig@gmail.com>
-
Alexander Makarenko authored
Also add `EvalError`, `RangeError`, `ReferenceError`, `SyntaxError`, `TypeError`, `URIError` to list of global types. Fix errors.markdown copy accordingly. Fixes: https://github.com/nodejs/node/issues/5325. PR-URL: https://github.com/nodejs/node/pull/5329 Reviewed-By:
James M Snell <jasnell@gmail.com>
-
Joran Dirk Greef authored
On Linux and OS X systems, `fs.watch()` resolves the watched path to an inode. This clarifies that `fs.watch()` watches the inode and not the path. If the inode of the path subsequently changes, `fs.watch()` will continue watching the original inode and events for the path will no longer be emitted. This is expected behavior. Fixes: https://github.com/nodejs/node/issues/5039 PR-URL: https://github.com/nodejs/node/pull/6099 Reviewed-By:
James M Snell <jasnell@gmail.com>
-
Rich Trott authored
Some vm tests are not in strict mode because they need to create and use global variables. By using `global.foo` instead of just `foo`, we can still enable strict mode. PR-URL: https://github.com/nodejs/node/pull/6209 Reviewed-By:
James M Snell <jasnell@gmail.com> Reviewed-By:
Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By:
Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By:
Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By:
Minwoo Jung <jmwsoft@gmail.com>
-
Trevor Norris authored
Do to various reasons, outlined in the committed document, domains were only in core for 2 years before being deprecated. This outline explains why they received criticism from the community and never gained traction with module authors. Also included is an example script that accompanies the postmortem analysis. PR-URL: https://github.com/nodejs/node/pull/6159 Reviewed-By:
Robert Lindstädt <robert.lindstaedt@gmail.com> Reviewed-By:
Kelvin Knighton <keltheceo@gmail.com> Reviewed-By:
James M Snell <jasnell@gmail.com> Reviewed-By:
Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By:
Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By:
Brian White <mscdex@mscdex.net>
-
Stefan Budeanu authored
PR-URL: https://github.com/nodejs/node/pull/6227 Reviewed-By:
Evan Lucas <evanlucas@me.com> Reviewed-By:
Rich Trott <rtrott@gmail.com> Reviewed-By:
Myles Borins <myles.borins@gmail.com>
-
Imran Iqbal authored
PR-URL: https://github.com/nodejs/node/pull/6226 Reviewed-By:
Evan Lucas <evanlucas@me.com> Reviewed-By:
Rich Trott <rtrott@gmail.com>
-
Santiago Gimeno authored
PR-URL: https://github.com/nodejs/node/pull/6225 Reviewed-By:
Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By:
Evan Lucas <evanlucas@me.com> Reviewed-By:
Rich Trott <rtrott@gmail.com> Reviewed-By:
James M Snell <jasnell@gmail.com> Reviewed-By:
Myles Borins <myles.borins@gmail.com>
-
Anna Henningsen authored
PR-URL: https://github.com/nodejs/node/pull/6224 Reviewed-By:
James M Snell <jasnell@gmail.com> Reviewed-By:
Evan Lucas <evanlucas@me.com> Reviewed-By:
Rich Trott <rtrott@gmail.com> Reviewed-By:
Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By:
Myles Borins <myles.borins@gmail.com>
-
Brian White authored
PR-URL: https://github.com/nodejs/node/pull/5172 Reviewed-By:
James M Snell <jasnell@gmail.com>
-
Kat Marchán authored
Upstream PR: https://github.com/npm/npm/pull/12310 PR-URL: https://github.com/nodejs/node/pull/6153 Reviewed-By:
Jeremiah Senkpiel <fishrock123@rocketmail.com>
-
Kat Marchán authored
PR-URL: https://github.com/nodejs/node/pull/6153 Reviewed-By:
Jeremiah Senkpiel <fishrock123@rocketmail.com>
-
Amery authored
PR-URL: https://github.com/nodejs/node/pull/6194 Reviewed-By:
Colin Ihrig <cjihrig@gmail.com> Reviewed-By:
Brian White <mscdex@mscdex.net> Reviewed-By:
Michaël Zasso <mic.besace@gmail.com>
-
Anna Henningsen authored
Change the regular expression that recognizes “simple” JS expressions to requiring that the full line needs to match it. Previously, in terms like `a().b.`, `b.` would be a partial match. This meant that completion would evaluate `b` and either fail with a `ReferenceError` or, if `b` was some global, return the properties of the global `b` object. PR-URL: https://github.com/nodejs/node/pull/6192 Reviewed-By:
Colin Ihrig <cjihrig@gmail.com> Reviewed-By:
Ben Noordhuis <info@bnoordhuis.nl>
-
Matteo Collina authored
net streams can request multiple chunks to be written in a synchronous fashion. If this is combined with cork/uncork, en error is currently thrown because of a regression introduced in: https://github.com/nodejs/node/commit/89aeab901ac9e34c79be3854f1aa41f2a4fb6888 (https://github.com/nodejs/node/pull/4354). Fixes: https://github.com/nodejs/node/issues/6154 PR-URL: https://github.com/nodejs/node/pull/6164 Reviewed-By:
Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By:
Mathias Buus <mathiasbuus@gmail.com> Reviewed-By:
James M Snell <jasnell@gmail.com>
-
Fedor Indutny authored
Original commit message: tools: fix tickprocessor Cpp symbols on mac Despite man page documentation: -f Display the symbol table of a dynamic library flat (as one file not separate modules). `nm` on mac treats `-f` as a shorthand for `-format`. The `-f` argument does not seem to be required, so just remove it completely. (For `-format` documentation - see `nm --help` on mac). BUG= Review URL: https://codereview.chromium.org/1840633002 Cr-Commit-Position: refs/heads/master@{#35445} Fix: #5903 PR-URL: https://github.com/nodejs/node/pull/6179 Reviewed-By:James M Snell <jasnell@gmail.com> Reviewed-By:
Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By:
Michaël Zasso <mic.besace@gmail.com>
-
Rich Trott authored
Reduce client connections from 10 to 4 in a test that is causing issues on Raspberry Pi 2 devices in CI. Fixes: https://github.com/nodejs/node/issues/5122 PR-URL: https://github.com/nodejs/node/pull/6138 Reviewed-By:
Benjamin Gruenbaum <benjamingr@gmail.com>
-
Sakthipriyan Vairamani authored
As Node.js expects either Python 2.6 or 2.7 installed to work properly, simplejson module is no longer necessary. It was included in Python 2.6 as the json module. PR-URL: https://github.com/nodejs/node/pull/6101 Reviewed-By:
Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By:
James M Snell <jasnell@gmail.com> Reviewed-By:
Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By:
Johan Bergström <bugs@bergstroem.nu>
-
Anna Henningsen authored
In 68990948 (https://github.com/nodejs/node/pull/2325), the conditions for increasing `readableState.awaitDrain` when writing to a piping destination returns false were changed so that they could not actually be met, effectively leaving `readableState.awaitDrain` with a constant value of 0. This patch changes the conditions to testing whether the stream for which `.write()` returned false is still a piping destination, which was likely the intention of the original patch. Fixes: https://github.com/nodejs/node/issues/5820 Fixes: https://github.com/nodejs/node/issues/5257 PR-URL: https://github.com/nodejs/node/pull/6023 Reviewed-By:
Brian White <mscdex@mscdex.net> Reviewed-By:
Matteo Collina <matteo.collina@gmail.com> Reviewed-By:
James M Snell <jasnell@gmail.com>
-
Myles Borins authored
Currently we include instructions on how to check the sha of a downloaded tar-ball, but do not include instruction on how to get the `SHA256.txt` file. This has led to confusion with people thinking that the SHA256.txt is included in that tarball. This commit includes instructions on how to use curl to download the `SHA256.txt` prior to the instructions on how to verify the sha. Refs: https://github.com/nodejs/help/issues/113 Refs: https://github.com/nodejs/help/issues/137 PR-URL: https://github.com/nodejs/node/pull/6120 Reviewed-By:
Colin Ihrig <cjihrig@gmail.com> Reviewed-By:
James M Snell <jasnell@gmail.com>
-
James M Snell authored
Clarify caveats on `maxBuffer` with regards to Unicode output. Refs: https://github.com/nodejs/node/issues/1901 PR-URL: https://github.com/nodejs/node/pull/6030 Reviewed-By:
Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By:
Benjamin Gruenbaum <benjamingr@gmail.com>
-
Robert Jefe Lindstaedt authored
This commit refines the documentation around child.kill(), where kill attempts against shells will lead to unexpected results. Namely, on linux the child process of a child process will not terminate, when its parent gets terminated. This is different across the the platforms. PR-URL: https://github.com/nodejs/node/issues/2098 Reviewed-By:
Benjamin Gruenbaum <benjamingr@gmail.com> Closes: https://github.com/nodejs/node/issues/2098
-
firedfox authored
Current tools/doc/json.js only supports one bracket style for optional params methodName(param0[,param1],param2). Add support to other styles such as methodName(param0,[param1,]param2) or methodName(param0[,param1,param2]) or methodName(param0[,param1[,param2]]). PR-URL: https://github.com/nodejs/node/pull/5977 Fixes: https://github.com/nodejs/node/issues/5976 Reviewed-By:
Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By:
James M Snell <jasnell@gmail.com> Reviewed-By:
Robert Lindstädt <robert.lindstaedt@gmail.com> Reviewed-By:
Roman Reiss <me@silverwind.io>
-
firedfox authored
Doc tool produces incomplete json when it meets unordered lists that directly following a heading. Add a default case to processList function to handle the lists. PR-URL: https://github.com/nodejs/node/pull/5966 Fixes: https://github.com/nodejs/node/issues/1545 Reviewed-By:
James M Snell <jasnell@gmail.com> Reviewed-By:
Robert Lindstädt <robert.lindstaedt@gmail.com> Reviewed-By:
Roman Reiss <me@silverwind.io>
-
Luigi Pinca authored
Fixes an issue that prevented scrolling from going past large code blocks on iOS devices. Also fixes a few minor styling issues that came up in the discussion. Fixes: https://github.com/nodejs/node/issues/5861 PR-URL: https://github.com/nodejs/node/pull/5878 Reviewed-By:
Roman Reiss <me@silverwind.io> Reviewed-By:
James M Snell <jasnell@gmail.com> Reviewed-By:
Robert Lindstädt <robert.lindstaedt@gmail.com>
-
Rich Trott authored
Fixes: https://github.com/nodejs/node/issues/6080 PR-URL: https://github.com/nodejs/node/pull/6124 Reviewed-By:
Colin Ihrig <cjihrig@gmail.com> Reviewed-By:
Brian White <mscdex@mscdex.net> Reviewed-By:
James M Snell <jasnell@gmail.com>
-
Mike Kaufman authored
A win32-only test was verifying that path.win32._makeLong('C:') would return the current working directory. This would only work if current working directory was also on the C: device. Fix is to grab the device letter for current working directory, and pass that to _makeLong(). PR-URL: https://github.com/nodejs/node/pull/6067 Reviewed-By:Trott - Rich Trott <rtrott@gmail.com> Reviewed-By:
Joao Reis <reis@janeasystems.com> Reviewed-By:
Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By:
James M Snell <jasnell@gmail.com> Reviewed-By:
Johan Bergström <bugs@bergstroem.nu>
-
Rich Trott authored
There is some unnecessary logic in repl.js. Remove it. PR-URL: https://github.com/nodejs/node/pull/6071 Reviewed-By:
James M Snell <jasnell@gmail.com>
-
Jeff Harris authored
Adds a new topic that provides an overview of the event loop, timers, and `process.nextTick()` that is based upon a NodeSource "Need to Node" presentation hosted by @trevnorris: Event Scheduling and the Node.js Event Loop (https://nodesource.com/resources ). PR-URL: #4936 Reviewed-By:
James M Snell <jasnell@gmail.com> Reviewed-By:
Calvin W. Metcalf <calvin.metcalf@gmail.com> Reviewed-By:
Matteo Collina <matteo.collina@gmail.com>
-
Trevor Norris authored
ParseArrayIndex() was requesting a Uint32Value(), but assigning it to an in32_t. This caused slight differences in error message reported in edge cases of argument parsing. Fixed by getting the IntegerValue() before checking if the value is < 0. Added test of API that was affected. PR-URL: https://github.com/nodejs/node/pull/6084 Reviewed-By:
James M Snell <jasnell@gmail.com>
-
Brad Hill authored
PR-URL: https://github.com/nodejs/node/pull/6108 Reviewed-By:
James M Snell <jasnell@gmail.com> Reviewed-By:
Fedor Indutny <fedor.indutny@gmail.com>
-
Rich Trott authored
* use common.mustCall() to verify all tests have run * eliminate unneeded removeTestFile() * eliminate unneeded var leaking into global scope * var -> const * remove instance of let PR-URL: https://github.com/nodejs/node/pull/6050 Reviewed-By:
James M Snell <jasnell@gmail.com>
-
Myles Borins authored
As requested in #5221 Original commit message: fix debug command processor wrt restart frame. R=jkummerow@chromium.org BUG=v8:4757 LOG=N Review URL: https://codereview.chromium.org/1700693002 Cr-Commit-Position: refs/heads/master@{#33983} PR-URL: https://github.com/nodejs/node/pull/6086 Reviewed-By:
Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By:
Michaël Zasso <mic.besace@gmail.com> Reviewed-By:
James M Snell <jasnell@gmail.com>
-
Steven R. Loomis authored
* due to: openssl bump in 1f434787 PR-URL: https://github.com/nodejs/node/pull/6065 Reviewed-By:
Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By:
Myles Borins <myles.borins@gmail.com> Reviewed-By:
James M Snell <jasnell@gmail.com>
-
Brendon Pierson authored
decipher.setAuthPadding canged to decipher.setAutoPadding PR-URL: https://github.com/nodejs/node/pull/6041 Reviewed-By:
Brian White <mscdex@mscdex.net> Reviewed-By:
James M Snell <jasnell@gmail.com> Reviewed-By:
Roman Klauke <romaaan.git@gmail.com>
-
Ben Noordhuis authored
We don't link with `--gc-sections` because it's unreliable with some toolchains, so all these flags do is make the compiler generate slightly worse code. Drop them. Refs: https://github.com/nodejs/node/pull/6056 PR-URL: https://github.com/nodejs/node/pull/6077 Reviewed-By:
Trevor Norris <trev.norris@gmail.com>
-
Rich Trott authored
The last change to this test landed before a nit about strict mode was addressed, so this change addresses that. PR-URL: https://github.com/nodejs/node/pull/6047 Refs: https://github.com/nodejs/node/pull/6017 Reviewed-By:
Colin Ihrig <cjihrig@gmail.com> Reviewed-By:
Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By:
Roman Klauke <romaaan.git@gmail.com>
-
Rich Trott authored
PR-URL: https://github.com/nodejs/node/pull/6040 Refs: https://github.com/nodejs/node/issues/6035 Reviewed-By:
Colin Ihrig <cjihrig@gmail.com> Reviewed-By:
James M Snell <jasnell@gmail.com> Reviewed-By:
Brian White <mscdex@mscdex.net>
-
Ben Noordhuis authored
The BaseObject constructor and destructor should not have external linkage because BaseObject is a header-only construct. Add the necessary 'inline' keywords. PR-URL: https://github.com/nodejs/node/pull/6056 Reviewed-By:
Colin Ihrig <cjihrig@gmail.com>
-