Age | Commit message (Collapse) | Author |
|
Conflicts:
ChangeLog
deps/uv/src/unix/udp.c
deps/uv/src/win/fs.c
deps/uv/src/win/udp.c
deps/uv/test/test-fs.c
doc/index.html
doc/logos/index.html
doc/template.html
src/node_version.h
|
|
* check exit code of child processes
* wait 1000 ms to exit the child process
* prefix log messages with [PARENT] or [CHILD] to help debugging
* kill all child processes before exiting
Conflicts:
test/simple/test-dgram-multicast-multi-process.js
|
|
When using isolate the .fork would break because it had
no .disconnect method. This remove the exit handler there
would call .disconnect since it was not required.
It also change .disconnect to throw if the channel is closed,
this was not possible before because .disconnect would be called
twice.
|
|
Somehow windows doesn't want to bind to 224.0.0.1. Let's test with a multicast
address that has no special meaning.
|
|
|
|
|
|
|
|
Fixes #1138, #2610.
|
|
when the status code is 100 (Continue).
Fixes #2636.
|
|
If a timer callback throws and the user's uncaughtException handler ignores the
exception, other timers that expire on the current tick should still run.
If #2582 goes through, this hack should be removed.
Fixes #2631.
|
|
|
|
Also, if an error is already provided, then raise the provided
error, rather than throwing it with a less helpful 'stdout cannot
be closed' message.
This is important for properly handling EPIPEs.
|
|
- watch for the death of child processes and fail the test if they all die
- use setTimeout to fail the test if responses are not received and processed in 5000ms
|
|
|
|
|
|
|
|
|
|
The socket is not part of any multicast group. Bug wasn't visible until 6999fb3.
|
|
Conflicts:
ChangeLog
doc/template.html
lib/cluster.js
lib/http.js
lib/tls.js
src/node.h
src/node_version.h
test/simple/test-cluster-kill-workers.js
|
|
Fixes #1333.
|
|
|
|
As RFC 2616 says we should, assume that servers will provide a persistent
connection by default.
> A significant difference between HTTP/1.1 and earlier versions of
> HTTP is that persistent connections are the default behavior of any
> HTTP connection. That is, unless otherwise indicated, the client
> SHOULD assume that the server will maintain a persistent connection,
> even after error responses from the server.
> HTTP/1.1 applications that do not support persistent connections MUST
> include the "close" connection option in every message.
Fixes #2436.
|
|
`path.exists*` functions show a deprecation warning and call functions
from `fs`. They should be removed later.
test: fix references to `path.exists*` in tests
test fs: add test for `fs.exists` and `fs.existsSync`
doc: reflect moving `path.exists*` to `fs`
|
|
Removed during the early stages of node 0.5 refactoring to libuv.
|
|
Removed during the early stages of node 0.5 refactoring to libuv.
|
|
Removed during the early stages of node 0.5 refactoring to libuv.
|
|
|
|
Fixes #2577.
|
|
Fix zlib crashes on error due to improper use of removeListener
in the error handler
|
|
Fixes #2470
|
|
|
|
Closes GH-2526
|
|
uncaughtException handlers installed by the user override the default one that
the cluster module installs, the one that kills off the master process.
Fixes #2556.
|
|
Fixes #2564
|
|
|
|
|
|
Fixes #2549.
|
|
Make obj.toString and Object.prototype.toString work correctly for typed arrays.
|
|
Conflicts:
deps/uv/src/win/util.c
src/udp_wrap.cc
|
|
|
|
* fix limiting when parser was reused
* fix maxHeadersCount = 0 is ignored ( credit to @koichik )
* add test-http-max-headers-count.js ( credit to @koichik )
|
|
|
|
|
|
|
|
Passing a non-buffer or non-string argument to Socket.prototype.write triggered
an assert:
Assertion failed: (Buffer::HasInstance(args[0])), function Write,
file ../src/stream_wrap.cc, line 289.
Fixes #2532.
|
|
With Upgrade or CONNECT request, http.ClientRequest emits 'close' event
after its socket is closed. However, after receiving a response, the socket
is not under management by the request.
http.ClientRequest should detach the socket before 'upgrade'/'connect'
event is emitted to pass the socket to a user. After that, it should
emit 'close' event immediately without waiting for closing of the socket.
Fixes #2510.
|
|
* ammended test-zlib-dictionary to cover reusing streams
|
|
|
|
|
|
|