Skip to content
Commits on Feb 19, 2013
  1. @isaacs

    2013.02.19, Version 0.9.10 (Unstable)

    isaacs committed
    * V8: Upgrade to 3.15.11.15
    
    * npm: Upgrade to 1.2.12
    
    * fs: Change default WriteStream config, increase perf (isaacs)
    
    * process: streamlining tick callback logic (Trevor Norris)
    
    * stream_wrap, udp_wrap: add read-only fd property (Ben Noordhuis)
    
    * buffer: accept negative indices in Buffer#slice() (Ben Noordhuis)
    
    * tls: Cycle data when underlying socket drains (isaacs)
    
    * stream: read(0) should not always trigger _read(n,cb) (isaacs)
    
    * stream: Empty strings/buffers do not signal EOF any longer (isaacs)
    
    * crypto: improve cipher/decipher error messages (Ben Noordhuis)
    
    * net: Respect the 'readable' flag on sockets (isaacs)
    
    * net: don't suppress ECONNRESET (Ben Noordhuis)
    
    * typed arrays: copy Buffer in typed array constructor (Ben Noordhuis)
    
    * typed arrays: make DataView throw on non-ArrayBuffer (Ben Noordhuis)
    
    * windows: MSI installer enhancements (Scott Blomquist, Jim Schubert)
  2. @isaacs

    npm: Upgrade to 1.2.12

    isaacs committed
  3. @isaacs
  4. @isaacs

    test: Fix regression in tls test

    isaacs committed
    Undefined reference, introduced by a77c29a.
  5. @isaacs @indutny

    test: Fix tls tests which fail sporadically

    isaacs committed with indutny
    The count of ECONNRESETs is dependent on timing, and thus unreliable,
    especially on Linux machines.
Commits on Feb 18, 2013
  1. @isaacs
  2. @isaacs
  3. @isaacs

    Merge remote-tracking branch 'ry/v0.8' into master

    isaacs committed
    Conflicts:
    	AUTHORS
    	ChangeLog
    	lib/http.js
    	src/node_version.h
    	test/simple/test-http-header-response-splitting.js
Commits on Feb 16, 2013
  1. @kanongil @isaacs

    stream: Pipe data in chunks matching read data

    kanongil committed with isaacs
    This creates better flow for large values of lowWaterMark.
  2. @isaacs

    fs: Change default WriteStream config, increase perf

    isaacs committed
    This increases fs.WriteStream throughput dramatically by removing the
    "higher default water marks" for fs.WriteStream.
    
    Also includes a benchmark.  Current performance is significantly higher
    than v0.8 for strings at all tested levels except size=1.  Buffer
    performance is still lackluster.
    
    Further improvement in the stream.Writable base class is required, but
    this is a start.
  3. @isaacs

    test: Bump up debugger timeouts

    isaacs committed
    200ms is still short enough for occasional spurious failures.
  4. @trevnorris @isaacs

    process: allow ticker to cross communicate better

    trevnorris committed with isaacs
    Using external memory values allows for quick communication between js
    and cc land, so we can check if the js land callback needs to be run.
    (this is where I meant that manually tracking nextTickQueue.length would
    be helpful)
    
    Also did some minor cleanup of removing the old Tick and
    StartTickSpinner functions, and a few unneeded comments.
    
    Conflicts:
    
    	src/node.cc
  5. @trevnorris @isaacs

    process: streamlining tick callback logic

    trevnorris committed with isaacs
    * Callbacks from spinner now calls its own function, separate from the
      tickCallback logic
    * MakeCallback will call a domain specific function if a domain is
      detected
    * _tickCallback assumes no domains, until nextTick receives a callback
      with a domain. After that _tickCallback is overridden with the domain
      specific implementation.
    * _needTickCallback runs in startup() instead of nextTick (isaacs)
    * Fix bug in _fatalException where exit would be called twice (isaacs)
    * Process.domain has a default value of null
    * Manually track nextTickQueue.length (will be useful later)
    * Update tests to reflect internal api changes
  6. @isaacs

    Revert "Move MakeCallback to JS"

    isaacs committed
    This reverts commit 0109a9f.
    
    Also included:  Port all the changes to process._makeCallback into the
    C++ version.  Immediate nextTick, etc.
    
    This yields a slight boost in several benchmarks.  V8 is optimizing and
    deoptimizing process._makeCallback repeatedly.
  7. @shigeki @isaacs
  8. @shigeki @isaacs

    timer: move setImmediate from timer to uv_check

    shigeki committed with isaacs
    uv_check is the robust place to invoke setImmediate callbacks after
    process.nextTick and before timers(setTimeout/setInterval)
Commits on Feb 15, 2013
  1. @isaacs

    blog: Release v0.8.20

    isaacs committed
  2. @isaacs

    Now working on v0.8.21

    isaacs committed
  3. @isaacs
  4. @isaacs

    2013.02.15, Version 0.8.20 (Stable)

    isaacs committed
    * npm: Upgrade to v1.2.11
    
    * http: Do not let Agent hand out destroyed sockets (isaacs)
    
    * http: Raise hangup error on destroyed socket write (isaacs)
    
    * http: protect against response splitting attacks (Bert Belder)
  5. @isaacs

    npm: Upgrade to v1.2.11

    isaacs committed
  6. @isaacs
  7. @isaacs

    http: Raise hangup error on destroyed socket write

    isaacs committed
    Prior to v0.10, Node ignored ECONNRESET errors in many situations.
    There *are* valid cases in which ECONNRESET should be ignored as a
    normal part of the TCP dance, but in many others, it's a very relevant
    signal that must be heeded with care.
    
    Exacerbating this problem, if the OutgoingMessage does not have a
    req.connection._handle, it assumes that it is in the process of
    connecting, and thus buffers writes up in an array.
    
    The problem happens when you reuse a socket between two requests, and it
    is destroyed abruptly in between them.  The writes will be buffered,
    because the socket has no handle, but it's not ever going to GET a
    handle, because it's not connecting, it's destroyed.
    
    The proper fix is to treat ECONNRESET correctly.  However, this is a
    behavior/semantics change, and cannot land in a stable branch.
    
    Fix #4775
Commits on Feb 14, 2013
  1. @bnoordhuis

    doc: clarify child_process.exec() stdio option

    bnoordhuis committed
    It only works for stdin, not stdout/stderr, for obvious reasons.
  2. @bnoordhuis
Commits on Feb 13, 2013
  1. @dankohn @bnoordhuis

    doc: add prompt to fix repl_test.js example

    dankohn committed with bnoordhuis
    Running repl.start without the prompt set produces this error:
    
    repl.js:95
        throw new Error('An options Object, or a prompt String are required');
              ^
    Error: An options Object, or a prompt String are required
        at new REPLServer (repl.js:95:11)
        at Object.exports.start (repl.js:321:14)
        at Object.<anonymous> (/Users/dan/Dropbox/Documents/dev/nextgen/repl_test.js:5:6)
        at Module._compile (module.js:449:26)
        at Object.Module._extensions..js (module.js:467:10)
        at Module.load (module.js:356:32)
        at Function.Module._load (module.js:312:12)
        at Module.runMain (module.js:492:10)
        at process.startup.processNextTick.process._tickCallback (node.js:244:9)
  2. @bnoordhuis

    stream_wrap, udp_wrap: add read-only fd property

    bnoordhuis committed
    Expose the file descriptor as a read-only property on the internal
    handle objects. Intended for debugging purposes, not part of the API
    proper. The property is always null on Windows.
    
    Fixes #4754.
  3. @bnoordhuis
  4. @bnoordhuis

    udp_wrap: don't use namespace imports in header

    bnoordhuis committed
    It's not really harmful but it's inconsistent with the other header
    files.
  5. @bnoordhuis @isaacs

    buffer: accept negative indices in Buffer#slice()

    bnoordhuis committed with isaacs
    A negative start or end parameter now indexes from the end of the
    buffer. More in line with String#slice() and ArrayBuffer#slice().
  6. @isaacs

    net: Respect the 'readable' flag on sockets

    isaacs committed
    Previously, we were only destroying sockets on end if their readable
    side had already been ended.  This causes a problem for non-readable
    streams, since we don't expect to ever see an 'end' event from those.
    
    Treat the lack of a 'readable' flag the same as if it was an ended
    readable stream.
    
    Fix #4751
  7. @isaacs
Commits on Feb 12, 2013
  1. @isaacs

    blog: Peer Dependencies article

    isaacs committed
    Thanks, @domenic
  2. @bnoordhuis
  3. @indutny
Something went wrong with that request. Please try again.