Skip to content
Commits on Oct 18, 2013
  1. @tjfontaine

    2013.10.18, Version 0.10.21 (Stable)

    tjfontaine committed
    * uv: Upgrade to v0.10.18
    * crypto: clear errors from verify failure (Timothy J Fontaine)
    * dtrace: interpret two byte strings (Dave Pacheco)
    * fs: fix fs.truncate() file content zeroing bug (Ben Noordhuis)
    * http: provide backpressure for pipeline flood (isaacs)
    * tls: fix premature connection termination (Ben Noordhuis)
  2. @tjfontaine

    crypto: clear errors from verify failure

    tjfontaine committed
    OpenSSL will push errors onto the stack when a verify fails, which can
    disrupt TLS and other routines if we don't clear the error stack
    Fixes #6304
  3. @tjfontaine

    uv: Upgrade to v0.10.18

    tjfontaine committed
Commits on Oct 17, 2013
  1. @isaacs @trevnorris

    http: provide backpressure for pipeline flood

    isaacs committed with trevnorris
    If a client sends a lot more pipelined requests than we can handle, then
    we need to provide backpressure so that the client knows to back off.
    Do this by pausing both the stream and the parser itself when the
    responses are not being read by the downstream client.
    Backport of 085dd30
  2. @tjfontaine @trevnorris
Commits on Oct 16, 2013
  1. @sam-github @trevnorris

    doc: cluster documentation cleanup and corrections

    sam-github committed with trevnorris
    - fixed some incomprehensible wording ("event assigned to..."?)
    - removed undocumented and unnecessary process properties from example
    - corrected the docs on the default for the exec setting
    - described when workers are removed from cluster.workers
    - described addressType, which was documented as existing, but not what
      values it might have
    - spell out more clearly the limitations of setupMaster
    - describe disconnect in sufficient detail that why a child does or does
      not exit can be understood
    - clarify which cluster functions and events are available on process or
      just on the worker, as well as which are not available in children,
    - don't describe events as the same, when they have receive different
    - fix misleading disconnect example: since disconnect already calls
      close on all servers, doing it again in the example is a no-op, not
      the "force close" it was claimed to be
    - document the error event, not catching it will kill your node
    - describe suicide better, it is important, and a bit unintuitive
      (process.exit() is not suicide?)
    - use worker consistently throughout, instead of child.
  2. @sam-github @trevnorris

    doc: child_process corrections and cleanups

    sam-github committed with trevnorris
    - Make explicit that .disconnected is set before the disconnect event,
      and it is not allowed to send messages after calling .disconnect(),
      even while waiting for a delayed disconect event.
    - Remove obsolete claim that explicit exit is required
    - Describe silent: in the options for fork()
    - Describe .connected as the property it is, not just as an aside in
      the disconnect() method
  3. @bnoordhuis

    doc: http: reword IncomingMessage 'close' event

    bnoordhuis committed
    The bit that says "before response.end() was called or able to flush"
    doesn't apply to incoming streams.
    Fixes #6359.
  4. @bnoordhuis

    doc: http: add cross-links for easier clicking

    bnoordhuis committed
    Make it a little easier to navigate the http module documentation by
    turning class names and methods into links to the appropriate section.
Commits on Oct 15, 2013
  1. @bnoordhuis

    doc: expand os.loadavg() section

    bnoordhuis committed
    Add a short explanation of what the load average is and why it's
    unavailable on Windows.
    Also sneak in a fix for a typo that I introduced in commit 56c5806.
Commits on Oct 14, 2013
  1. @bnoordhuis

    doc: document os.loadavg() behavior on windows

    bnoordhuis committed
    The load average is a very UNIX-y concept.  That's why os.loadavg()
    always returns zeros on Windows.  Mention that in the documentation.
Commits on Oct 10, 2013
  1. @davepacheco @tjfontaine
  2. @bnoordhuis

    doc: net: remove bad net.Server description

    bnoordhuis committed
    net.Server is not an instance of net.Socket so don't say it is.
  3. @bnoordhuis

    doc: addon: fix object instantiation examples

    bnoordhuis committed
    * Extend examples to show how to handle non-constructor invocation in
      constructor callback functions.
    * Fix up examples to initialize member variables at object construction.
    * Fix up a few naming inconsistencies.
    Fixes #5701.
Commits on Oct 9, 2013
  1. @isaacs
  2. @bnoordhuis

    tls: fix premature connection termination

    bnoordhuis committed
    Destroying the TLS session implies destroying the underlying socket but
    before this commit, that was done with net.Socket#destroy() rather than
    net.Socket#destroySoon().  The former closes the connection right away,
    even when there is still data to write.  In other words, sometimes the
    final TLS record got truncated.
    Fixes #6107.
  3. @davepacheco @tjfontaine

    dtrace: backport two byte string fix

    davepacheco committed with tjfontaine
    This is a partial backport of 5921158
    Re #6309
    Closes #6319
Commits on Oct 8, 2013
  1. @bnoordhuis

    fs: fix fs.truncate() file content zeroing bug

    bnoordhuis committed
    fs.truncate() and its synchronous sibling are implemented in terms of
    open() + ftruncate().  Unfortunately, it opened the target file with
    mode 'w' a.k.a. 'write-only and create or truncate at open'.
    The subsequent call to ftruncate() then moved the end-of-file pointer
    from zero to the requested offset with the net result of a file that's
    neatly truncated at the right offset and filled with zero bytes only.
    This bug was introduced in commit 168a555 but in fairness, before that
    commit fs.truncate() worked like fs.ftruncate() so it seems we've never
    had a working fs.truncate() until now.
    Fixes #6233.
Commits on Oct 5, 2013
  1. @bnoordhuis

    doc: add warning to fs.exists() documentation

    bnoordhuis committed
    Warn against the open-if-exists anti-pattern, it's susceptible to
    race conditions.
Commits on Oct 1, 2013
  1. @bnoordhuis

    doc: link to pre-built binaries, add install note

    bnoordhuis committed
    lLnk to and add a short primer on how to
    extract the tarballs.
    Fixes #6292.
Commits on Sep 30, 2013
  1. @tjfontaine

    blog: Post for v0.10.20

    tjfontaine committed
  2. @tjfontaine

    Now working on 0.10.21

    tjfontaine committed
  3. @tjfontaine
  4. @tjfontaine

    2013.09.30, Version 0.10.20 (Stable)

    tjfontaine committed
    * tls: fix sporadic hang and partial reads (Fedor Indutny)
      - fixes "npm ERR! cb() never called!"
Commits on Sep 28, 2013
  1. @bnoordhuis

    src: turn uv_pipe_open() failures into exceptions

    bnoordhuis committed
    uv_pipe_open() is unlikely to fail but when it does, the failure should
    not be quietly ignored.  Raise the error as an exception.
    See joyent/libuv#941.
Commits on Sep 27, 2013
  1. @indutny

    tls: fix sporadic hang and partial reads

    indutny committed
    Do not decrement size in read loop, its used later, when comparing to
    fix #6270
    NOTE: Original patch contributed by @roadrunner2
Commits on Sep 24, 2013
  1. @tjfontaine
  2. @tjfontaine

    blog: Post for v0.10.19

    tjfontaine committed
  3. @tjfontaine

    Now working on 0.10.20

    tjfontaine committed
  4. @tjfontaine
  5. @tjfontaine

    2013.09.24, Version 0.10.19 (Stable)

    tjfontaine committed
    * uv: Upgrade to v0.10.17
    * npm: upgrade to 1.3.11
    * readline: handle input starting with control chars (Eric Schrock)
    * configure: add mips-float-abi (soft, hard) option (Andrei Sedoi)
    * stream: objectMode transforms allow falsey values (isaacs)
    * tls: prevent duplicate values returned from read (Nathan Rajlich)
    * tls: NPN protocols are now local to connections (Fedor Indutny)
  6. @tjfontaine

    uv: Upgrade to v0.10.17

    tjfontaine committed
Commits on Sep 23, 2013
  1. @tjfontaine

    readline: handle input starting with control chars

    Eric Schrock committed with tjfontaine
    Handle control characters only when there is a single byte in the
    stream, otherwise fall through to the standard multibyte handling.
Commits on Sep 19, 2013
  1. @bnoordhuis
Commits on Sep 16, 2013
  1. @TooTallNate
Something went wrong with that request. Please try again.