Switch branches/tags
Commits on Apr 3, 2013
  1. 2013.04.03, Version 0.10.3 (Stable)

    * npm: Upgrade to 1.2.17
    * child_process: acknowledge sent handles (Fedor Indutny)
    * etw: update prototypes to match dtrace provider (Timothy J Fontaine)
    * dtrace: pass more arguments to probes (Dave Pacheco)
    * build: allow building with dtrace on osx (Dave Pacheco)
    * http: Remove legacy ECONNRESET workaround code (isaacs)
    * http: Ensure socket cleanup on client response end (isaacs)
    * tls: Destroy socket when encrypted side closes (isaacs)
    * repl: isSyntaxError() catches "strict mode" errors (Nathan Rajlich)
    * crypto: Pass options to ctor calls (isaacs)
    * src: tie process.versions.uv to uv_version_string() (Ben Noordhuis)
    isaacs committed Apr 3, 2013
  2. npm: Upgrade to 1.2.17

    isaacs committed Apr 3, 2013
  3. child_process: acknowledge sent handles

    Fix race-condition when multiple handles are sent and SCM_RIGHTS
    messages are gets merged by OS by avoiding sending multiple handles at
    fix #4885
    indutny committed with isaacs Apr 1, 2013
  4. etw: update prototypes to match dtrace provider

    The DTrace probes were updated to accomodate platforms that can't
    handle structs, update the prototypes for ETW but it's not necessary
    to do anything with the new arguments as it's redundant information.
    tjfontaine committed with isaacs Mar 30, 2013
  5. dtrace: check if _handle property is set

    Check that _handle is an object before trying to read its `fd`
    property, avoids bogus values.
    bnoordhuis committed with isaacs Mar 30, 2013
  6. dtrace: actually use the _handle.fd value

    When using the DTrace/systemtap subsystems it would be helpful to
    actually have an fd associated with the requests and responses.
    tjfontaine committed with isaacs Mar 28, 2013
  7. dtrace: pass more arguments to probes

    OSX and other DTrace implementations don't support dereferencing
    structs in probes. To accomodate that pass members from the struct as
    arguments so that DTrace is useful on those systems.
    davepacheco committed with isaacs Mar 28, 2013
Commits on Apr 2, 2013
  1. src: remove unused variables

    mscdex committed with bnoordhuis Apr 2, 2013
  2. http client: Ensure socket cleanup on response end

    If an http response has an 'end' handler that throws, then the socket
    will never be released back into the pool.
    Granted, we do NOT guarantee that throwing will never have adverse
    effects on Node internal state.  Such a guarantee cannot be reasonably
    made in a shared-global mutable-state side-effecty language like
    JavaScript.  However, in this case, it's a rather trivial patch to
    increase our resilience a little bit, so it seems like a win.
    There is no semantic change in this case, except that some event
    listeners are removed, and the `'free'` event is emitted on nextTick, so
    that you can schedule another request which will re-use the same socket.
    From the user's point of view, there should be no detectable difference.
    Closes #5107
    isaacs committed with indutny Apr 2, 2013
Commits on Apr 1, 2013
  1. test: test intended code-paths

    The tests did not agree with the test comments. Tests first and second
    were both testing the !state.reading case. Now second tests the
    state.reading && state.length case.
    Fixes nodejs/node-v0.x-archive#5183
    arhart committed with isaacs Mar 31, 2013
  2. tls: Destroy socket when encrypted side closes

    The v0.8 Stream.pipe() method automatically destroyed the destination
    stream whenever the src stream closed.  However, this caused a lot of
    problems, and was removed by popular demand.  (Many userland modules
    still have a no-op destroy() method just because of this.) It was also
    very hazardous because this would be done even if { end: false } was
    passed in the pipe options.
    In v0.10, we decided that the 'close' event and destroy() method are
    application-specific, and pipe() doesn't automatically call destroy().
    However, TLS actually depended (silently) on this behavior.  So, in this
    case, we should just go ahead and destroy the thing when close happens.
    Closes #5145
    isaacs committed Mar 30, 2013
  3. querystring: Removing unnecessary binding

    Binding of `http_parser` in querystring isn't used anywhere and should
    be removed.
    mitar committed with indutny Mar 31, 2013
Commits on Mar 30, 2013
  1. repl: use more readable RegExp syntax for spaces

    This is just a cosmetic change really, nothing major.
    TooTallNate committed Mar 30, 2013
Commits on Mar 29, 2013
Commits on Mar 28, 2013
  1. blog: v0.11.0 release

    isaacs committed Mar 28, 2013
  2. blog: Update linux binary tarball shasums

    I just accidentally the binary release.
    isaacs committed Mar 28, 2013
  3. blog: Post about v0.10.2

    isaacs committed Mar 28, 2013
  4. Node working on 0.10.3

    isaacs committed Mar 28, 2013
  5. 2013.03.28, Version 0.10.2 (Stable)

    * npm: Upgrade to 1.2.15
    * uv: Upgrade to 0.10.3
    * tls: handle SSL_ERROR_ZERO_RETURN (Fedor Indutny)
    * tls: handle errors before calling C++ methods (Fedor Indutny)
    * tls: remove harmful unnecessary bounds checking (Marcel Laverdet)
    * crypto: make getCiphers() return non-SSL ciphers (Ben Noordhuis)
    * crypto: check randomBytes() size argument (Ben Noordhuis)
    * timers: do not calculate Timeout._when property (Alexey Kupershtokh)
    * timers: fix off-by-one ms error (Alexey Kupershtokh)
    * timers: handle signed int32 overflow in enroll() (Fedor Indutny)
    * stream: Fix stall in Transform under very specific conditions (Gil Pedersen)
    * stream: Handle late 'readable' event listeners (isaacs)
    * stream: Fix early end in Writables on zero-length writes (isaacs)
    * domain: fix domain callback from MakeCallback (Trevor Norris)
    * child_process: don't emit same handle twice (Ben Noordhuis)
    * child_process: fix sending utf-8 to child process (Ben Noordhuis)
    isaacs committed Mar 28, 2013
  6. npm: Upgrade to v1.2.15

    isaacs committed Mar 28, 2013
  7. tls: handle SSL_ERROR_ZERO_RETURN

    see #5004
    indutny committed Mar 28, 2013
  8. setTimeout: do not calculate Timeout._when property

    Dramatically improves Timer performance.
    wicked committed with isaacs Oct 25, 2012
  9. stream: Emit readable on ended streams via read(0)

    cc: @mjijackson
    isaacs committed Mar 27, 2013
  10. stream: Handle late 'readable' event listeners

    In cases where a stream may have data added to the read queue before the
    user adds a 'readable' event, there is never any indication that it's
    time to start reading.
    True, there's already data there, which the user would get if they
    checked However, as we use 'readable' event listening as the signal to
    start the flow of data with a read(0) call internally, we ought to
    trigger the same effect (ie, emitting a 'readable' event) even if the
    'readable' listener is added after the first emission.
    To avoid confusing weirdness, only the *first* 'readable' event listener
    is granted this privileged status.  After we've started the flow (or,
    alerted the consumer that the flow has started) we don't need to start
    it again.  At that point, it's the consumer's responsibility to consume
    the stream.
    Closes #5141
    isaacs committed Mar 26, 2013
  11. doc: Add 'don't ignore errors' section to domain

    Also, an example program of using cluster and domain to handle errors
    safely, with zero downtime, using process isolation.
    isaacs committed Mar 28, 2013