- Jan 14, 2014
-
-
Alex Kocharin authored
-
- Jan 11, 2014
-
-
Tom Gallacher authored
Fixes #6835
-
- Jan 10, 2014
-
-
Ryan Graham authored
We want to clear the found domain and the domains after it. Signed-off-by:Trevor Norris <trev.norris@gmail.com>
-
Trevor Norris authored
Now will process all write() that were done on a single tick in a single writev().
-
Jeff Barczewski authored
The RR cluster scheduler replaces the normal StreamWrap handle. Because of this the AsyncListener method failed to be in place when domains were in use. The issue was resolved in 828f1455 by reverting having domains use AsyncListeners. Signed-off-by:
Trevor Norris <trev.norris@gmail.com>
-
Trevor Norris authored
Before when an AsyncListener object was created and the "create" callback returned a value, it was necessary to construct a new Object with the same callbacks but add a place for the new storage value. Now, instead, a separate storage array is kept on the context which is used for any return value of the "create" callback. This significantly reduces the number of Objects that need to be created. Also added a flags property to the context to quickly check if a specific callback was available either on the context or on the AsyncListener instance itself. Few other minor changes for readability that were difficult to separate into their own commit. This has not been optimized yet.
-
Trevor Norris authored
This is a slightly modified revert of bc39bdd9. Getting domains to use AsyncListeners became too much of a challenge with many edge cases. While this is still a goal, it will have to be deferred for now until more test coverage can be provided.
-
- Jan 09, 2014
-
-
Fedor Indutny authored
When not specified as a configure flag, and not derived from system configuration, `arm_float_abi` should be set to `'default'`. fix #6789
-
Fedor Indutny authored
Report path to executable and argv on error, stderr is not enough in many cases. fix #6796
-
Fedor Indutny authored
`x86masm.pl` was mistakenly using .486 instruction set, why `cpuid` (and perhaps others) are requiring .686 .
-
- Jan 08, 2014
-
-
Fedor Indutny authored
-
Ben Noordhuis authored
Forcibly disable -Werror, the old { 'werror': '' } hack in node.gyp no longer works with newer versions of V8. We support a wide range of compilers, it's simply not feasible to squelch all warnings, never mind that the libraries in deps/ are not under our control. Fixes #6817.
-
- Jan 05, 2014
-
-
Lorenz Leutgeb authored
This fixes confusion connected to comparison of ECDH with RSA and wrong information on forward secrecy.
-
Fedor Indutny authored
-
- Jan 04, 2014
-
-
Trevor Norris authored
Instead of checking the uid on the array index of the queue, instead the object property "uid" was checked on the queue iteself. Because this will always evaluate to "undefined" the same listener could be added multiple times to the same context.
-
Trevor Norris authored
There was a flaw in the old API that has been fixed. Now the asyncListener callback is now the "create" object property in the callback object, and is optional.
-
- Jan 01, 2014
-
-
Timothy J Fontaine authored
-
Timothy J Fontaine authored
-
Timothy J Fontaine authored
-
Timothy J Fontaine authored
-
Timothy J Fontaine authored
* http_parser: update to 2.2 * uv: Upgrade to v0.11.17 * v8: Upgrade to 3.22.24.10 * buffer: optimize writeInt* methods (Paul Loyd) * child_process: better error handling (Alexis Campailla) * cluster: do not synchronously emit 'setup' event (Sam Roberts) * cluster: restore backwards compatibility and various fixes (Sam Roberts) * crypto: remove unnecessary OpenSSL_add_all_digests (Yorkie) * crypto: support GCM authenticated encryption mode. (Ingmar Runge) * dns: add resolveSoa and 'SOA' rrtype (Tuğrul Topuz) * events: move EE c'tor guts to EventEmitter.init (Bert Belder) * http: DELETE shouldn't default to chunked encoding (Lalit Kapoor) * http: parse the status message in a http response. (Cam Swords) * node: fix removing AsyncListener in callback (Vladimir Kurchatkin) * node: follow specification, zero-fill ArrayBuffers (Trevor Norris) * openssl: use ASM optimized routines (Fedor Indutny) * process: allow nextTick infinite recursion (Trevor Norris) * querystring: remove `name` from `stringify()` (Yorkie) * timers: setImmediate v8 optimization fix (pflannery) * tls: add serialNumber to getPeerCertificate() (Ben Noordhuis) * tls: reintroduce socket.encrypted (Fedor Indutny) * tls: fix handling of asterisk in SNI context (Fedor Indutny) * util: Format negative zero as '-0' (David Chan) * vm: fix race condition in timeout (Alexis Campailla) * windows: fix dns lookup of localhost with ipv6 (Alexis Campailla)
-
Timothy J Fontaine authored
-
Timothy J Fontaine authored
-
Maciej Małecki authored
Ref #2598
-
Timothy J Fontaine authored
-
Ron Korving authored
The fact that the "exit" event passes the exit code as an argument as omitted from the documentation. This adds the explanation and augments the example code to show that.
-
Tuğrul Topuz authored
You can now query for SOA records by either passing 'SOA' to `resolve` or by using the new `resolveSoa`
-
Timothy J Fontaine authored
Conflicts: lib/cluster.js lib/dgram.js lib/net.js
-
Timothy J Fontaine authored
-
Sam Roberts authored
Master was disconnecting its workers as soon as they both started up. Meanwhile, the workers were trying to listen. Its a race, sometimes the disconnect would happen between when worker gets the response message, and acks that message with a 'listening'. This worked OK after v0.11 introduced a behaviour where disconnect would always exit the worker, but once that backwards-incompatible behaviour is removed, the worker lives long enough to try and respond to the master, and child_process errors at the attempt to send from a disconnected child.
-
Sam Roberts authored
This is a problem present in both v0.10, and v0.11, where the 'setup' event is synchronously emitted by `cluster.setupMaster()`, a mostly harmless anti-pattern.
-
Sam Roberts authored
Fix inadvertent v0.11 changes to the definition of suicide, particularly the relationship between suicide state, the disconnect event, and when exit should occur. In v0.10, workers don't forcibly exit on disconnect, it doesn't give them time to do a graceful finish of open client connections, they exit under normal node rules - when there is nothing left to do. But on unexpected disconnect they do exit so the workers aren't left around after the master. Note that a test as-written was invalid, it failed against the v0.10 cluster API, demonstrating that it was an undocumented API change.
-
Sam Roberts authored
Fixes issue in 0.11 where callback doesn't occur if worker count is currently zero. In 0.10 callback occurs after worker count is zero, and occurs in next tick if worker count is currently zero.
-
Sam Roberts authored
-
Timothy J Fontaine authored
-
Fedor Indutny authored
Some errors for listening and binding to a socket were not properly delivered to workers. fix #6767
-
- Dec 31, 2013
-
-
Benjamin Waters authored
Add colon to event heading to ensure it matches other events. Fixes joyent/node#5687
-
Timothy J Fontaine authored
-
Fedor Indutny authored
-
pflannery authored
Prevent v8 disabling optimization for scenario "bad value context for arguments value". Solves #6631 Signed-off-by:Trevor Norris <trev.norris@gmail.com>
-