| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
| |
This reverts commit 56e80a37e0df0d131d3a3ad6426d52f887ef8e94.
|
| |
|
|
| |
This reverts commit 2ee86c624ecd6b9dbaad10989143325fc64778cd.
|
| |
|
|
|
|
| |
Don't use argument as callback if it's not a valid callback function.
Throw a valid exception instead explaining the issue. Adds to #7070
("DNS — Throw meaningful error(s)").
|
| |
|
|
|
|
| |
Mitigat C++-land assertion error, add test accordingly.
fix #7070
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
References for err.signal and err.code should be error.signal and
error.code.
Fixes joyent/node#6862
|
| |
|
|
|
|
|
|
| |
Update the list of root certificates in src/node_root_certs.h with
tools/mk-ca-bundle.pl and update src/node_crypto.cc to make use of
the new format.
Fixes #6013.
|
| |
|
|
| |
`path.extname` returns only the last extension
|
| |
|
|
|
| |
Add enough arguments to `NODE_NET_SOCKET_READ()` and
`NODE_NET_SOCKET_WRITE()` stubs.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Original commit message:
VS2013 contains a number of improvements, most notably the addition
of all C99 math functions.
I'm a little bit concerned about the change I had to make in
cpu-profiler.cc, but I spent quite a bit of time looking at it and was
unable to figure out any rational explanation for the warning. It's
possible it's spurious. Since it seems like a useful warning in
general though, I chose not to disable globally at the gyp level.
I do think someone with expertise here should probably try to
determine if this is a legitimate warning.
BUG=288948
R=dslomov@chromium.org
Review URL: https://codereview.chromium.org/23449035
NOTE: Path applied without `cpu-profiler.cc` changes because in our
version it was looking totally different.
|
| |
|
|
|
|
| |
Even if stdio streams are opened as file streams, we should not ever try
to close them. This could be accomplished by passing `autoClose: false`
in options on their creation.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
So that we are free to call socket.destroy() in error event handler.
fix #6769
|
| |
|
|
| |
fix #6963
|
| |
|
|
| |
fix #6908
|
| |
|
|
|
|
|
|
|
|
|
| |
Original commit message:
ares_parse_txt_reply: return a ares_txt_reply node for each sub-string
Previously, the function would wrongly return all substrings merged into
one.
fix #6931
|
| |
|
|
| |
fix #6933
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The test was calling server.close() after write on the socket
had completed. However the fact that the write had completed was
not valid indication that the server had received the data.
This would result in a premutaure closing of the server and
an ECONNRESET event on the client.
|
| |
|
|
|
| |
The test was calling server.close() without waiting for the server
to have received all the requests. This would cause an ECONNRESET.
|
| | |
|
| | |
|
| |\ |
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* uv: Upgrade to v0.10.23
* npm: Upgrade to v1.3.24
* v8: Fix enumeration for objects with lots of properties
* child_process: fix spawn() optional arguments (Sam Roberts)
* cluster: report more errors to workers (Fedor Indutny)
* domains: exit() only affects active domains (Ryan Graham)
* src: OnFatalError handler must abort() (Timothy J Fontaine)
* stream: writes may return false but forget to emit drain (Yang Tianyang)
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
fix #6679
|
| | |
|
| |
|
|
|
|
|
| |
Spawn's arguments were documented to be optional, as they are for the
other similar child_process APIs, but the code was missing. Result was
`child_process.spawn('node', {})` errored when calling slice() on an
Object, now it behaves as the documentation said it would.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
domain.create().exit() should not clear the domain stack if the domain
instance does not exist within the stack.
Signed-off-by: Trevor Norris <trev.norris@gmail.com>
|
| | |
|
| |
|
|
| |
fix #6859
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
spawn stdio options can be a 'stream', but the following code
fails with "Incorrect value for stdio stream: [object Object]",
despite being a stream. The problem is the test isn't really
for a stream, its for an object with a numeric `.fd` property,
and streams do not have an fd until their async 'open' event
has occurred. This is reasonable, but was not documented.
child_process.spawn('date', [], {stdio: [
'ignore',
fs.createWriteStream('out.txt',{flags:'a'}),
'ignore']})
|
| |
|
|
|
| |
Killing the debuggee without first closing the socket can result
in an ECONNRESET error.
|
| |
|
|
|
|
|
| |
If node was compiled with --no-ifaddrs to support older operating
systems, don't throw instead simply return an empty object
Fixes #6846
|
| |
|
|
|
|
|
| |
Keep the number of descriptors below
DescriptorArray::kMaxNumberOfDescriptors even for accessors
Review URL: https://codereview.chromium.org/11362182
|
| | |
|
| |
|
|
|
|
|
| |
We are in an unrecoverable state if v8 throws a FatalError, actually
ask the operating system to dump core in this case.
Fixes #6836
|
| | |
|
