Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Branch: run-in-closing…
Commits on Jan 5, 2014
  1. @trevnorris
Commits on Jan 4, 2014
  1. @trevnorris
  2. @trevnorris
  3. @trevnorris

    cluster: remove custom close callback

    trevnorris authored
    Now that the net close callbacks don't run until after libuv has had a
    chance to properly close the uv_handle_t the custom close callback in
    cluster is no longer necessary.
  4. @trevnorris

    net: run close callbacks in correct eloop phase

    trevnorris authored
    Instead of running the close callbacks seemingly synchronously instead
    of when the handle has actually been closed by libuv, instead run the
    callbacks in the uv__run_closing_handles() phase of the eloop.
  5. @trevnorris

    node: properly check uid when adding AsyncListener

    trevnorris 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.
Commits on Jan 3, 2014
  1. @trevnorris

    node: change AsyncListener API

    trevnorris 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.
Commits on Jan 1, 2014
  1. @tjfontaine
  2. @tjfontaine

    blog: Post for v0.11.10

    tjfontaine authored
  3. @tjfontaine

    Now working on 0.11.11

    tjfontaine authored
  4. @tjfontaine
Commits on Dec 31, 2013
  1. @tjfontaine

    2013.12.31, Version 0.11.10 (Unstable)

    tjfontaine authored
    * http_parser: update to 2.2
    * uv: Upgrade to v0.11.17
    * v8: Upgrade to
    * 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)
  2. @tjfontaine

    v8: Upgrade to

    tjfontaine authored
  3. @tjfontaine
  4. @mmalecki @tjfontaine

    doc: document that `process.send` is synchronous

    mmalecki authored tjfontaine committed
    Ref #2598
  5. @tjfontaine
  6. @ronkorving @tjfontaine

    docs: process.on('exit') receives exit code

    ronkorving authored tjfontaine committed
    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.
  7. @tugrul @tjfontaine

    dns: add resolveSoa and 'SOA' rrtype

    tugrul authored tjfontaine committed
    You can now query for SOA records by either passing 'SOA' to `resolve`
    or by using the new `resolveSoa`
  8. @tjfontaine

    Merge remote-tracking branch 'upstream/v0.10'

    tjfontaine authored
  9. @tjfontaine
  10. @sam-github @tjfontaine

    test: fix assumption of worker exit on disconnect

    sam-github authored tjfontaine committed
    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.
  11. @sam-github @tjfontaine

    cluster: do not synchronously emit 'setup' event

    sam-github authored tjfontaine committed
    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.
  12. @sam-github @tjfontaine

    cluster: only forcibly exit worker on unclean exit

    sam-github authored tjfontaine committed
    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.
  13. @sam-github @tjfontaine

    cluster: disconnect callback should always occur

    sam-github authored tjfontaine committed
    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.
  14. @sam-github @tjfontaine

    cluster: replace erroneous comma with semicolon

    sam-github authored tjfontaine committed
  15. @tjfontaine

    uv: Upgrade to v0.11.17

    tjfontaine authored
  16. @indutny @tjfontaine

    cluster: report more errors to workers

    indutny authored tjfontaine committed
    Some errors for listening and binding to a socket were not properly
    delivered to workers.
    fix #6767
  17. @Benjamin-Waters @indutny

    doc: Fix doc heading for 'response' event

    Benjamin-Waters authored indutny committed
    Add colon to event heading to ensure it matches other events.
    Fixes joyent/node#5687
Commits on Dec 30, 2013
  1. @tjfontaine
  2. @indutny @tjfontaine

    deps: update gyp to 828ce09

    indutny authored tjfontaine committed
  3. @pflannery @trevnorris

    timers: setImmediate v8 optimization fix

    pflannery authored trevnorris committed
    Prevent v8 disabling optimization for scenario "bad value context for
    arguments value".
    Solves #6631
    Signed-off-by: Trevor Norris <>
  4. @davglass @tjfontaine

    doc: Fix missing backtick in debugger doc

    davglass authored tjfontaine committed
  5. @yorkie @trevnorris

    querystring: remove `name` from `stringify()`

    yorkie authored trevnorris committed
    QueryString.stringify() allowed a fourth argument that was used as a
    conditional in the return value, but was undocumented, not used by core
    and always was always false/undefiend. So the argument and conditional
    have been removed.
    Signed-off-by: Trevor Norris <>
Commits on Dec 28, 2013
  1. @gimelfarb @indutny

    build: add settings for VS 2013 to vcbuild.bat

    gimelfarb authored indutny committed
    Search for VS2013 compiler 1st, before falling back to older ones. This
    allows compiling using the latest VS2013.
Commits on Dec 27, 2013
  1. @indutny

    deps: update gyp to 828ce09

    indutny authored
Something went wrong with that request. Please try again.