Permalink
Commits on May 14, 2013
  1. 2013.05.14, Version 0.10.6 (Stable)

    * module: Deprecate require.extensions (isaacs)
    
    * stream: make Readable.wrap support objectMode, empty streams (Daniel Moore)
    
    * child_process: fix handle delivery (Ben Noordhuis)
    
    * crypto: Fix performance regression (isaacs)
    
    * src: DRY string encoding/decoding (isaacs)
    isaacs committed May 14, 2013
  2. buffer: DRY string encoding using StringBytes

    This also templatizes the Buffer::*Slice functions, and the template
    function probably cannot be safely used outside of Node.  However, it
    also SHOULD not be used outside of Node, so this is arguably a feature
    as well as a caveat.
    isaacs committed May 2, 2013
  3. src: use StringBytes for DecodeWrite/DecodeBytes/Encode

    Bonus: this makes node::Encode actually work properly with base64,
    ucs2, hex, etc.
    isaacs committed May 2, 2013
  4. src: Add StringBytes static util class

    Four functions:
    
    - StringBytes::StorageSize()
    - StringBytes::Size()
    - StringBytes::Write()
    - StringBytes::Encode()
    isaacs committed May 1, 2013
  5. tools: remove unnecessary cpplint rules

    We don't actually care about header order much, and since we never use
    stl classes, 'string' isn't an issue for node ever.
    isaacs committed May 1, 2013
  6. stream: Make default encoding configurable

    Pretty much everything assumes strings to be utf-8, but crypto
    traditionally used binary strings, so we need to keep the default
    that way until most users get off of that pattern.
    isaacs committed May 2, 2013
  7. stream: don't create unnecessary buffers in Readable

    If there is an encoding, and we do 'stream.push(chunk, enc)', and the
    encoding argument matches the stated encoding, then we're converting from
    a string, to a buffer, and then back to a string.  Of course, this is a
    completely pointless bit of work, so it's best to avoid it when we know
    that we can do so safely.
    isaacs committed Apr 30, 2013
  8. lint

    isaacs committed Apr 30, 2013
  9. benchmark: hash stream

    isaacs committed Apr 30, 2013
  10. blog: Release v0.11.2

    isaacs committed May 14, 2013
  11. test: increase workers to 8 in cluster-disconnect

    Increasing the number of workers from 2 to 8 makes this test
    more likely to trigger race conditions. See #5330 for background.
    Benoit Vallée committed with bnoordhuis Apr 30, 2013
Commits on May 13, 2013
  1. child_process: fix handle delivery

    Commit 9352c19 ("child_process: don't emit same handle twice") trades
    one bug for another.
    
    Before said commit, a handle was sometimes delivered with messages it
    didn't belong to.
    
    The bug fix introduced another bug that needs some explaining. On UNIX
    systems, handles are basically file descriptors that are passed around
    with the sendmsg() and recvmsg() system calls, using auxiliary data
    (SCM_RIGHTS) as the transport.
    
    node.js and libuv depend on the fact that none of the supported systems
    ever emit more than one SCM_RIGHTS message from a recvmsg() syscall.
    That assumption is something we should probably address someday for the
    sake of portability but that's a separate discussion.
    
    So, SCM_RIGHTS messages are never coalesced. SCM_RIGHTS and normal
    messages however _are_ coalesced. That is, recvmsg() might return this:
    
      recvmsg();  // { "message-with-fd", "message", "message" }
    
    The operating system implicitly breaks pending messages along
    SCM_RIGHTS boundaries. Most Unices break before such messages but Linux
    also breaks _after_ them.  When the sender looks like this:
    
      sendmsg("message");
      sendmsg("message-with-fd");
      sendmsg("message");
    
    Then on most Unices the receiver sees messages arriving like this:
    
      recvmsg();  // { "message" }
      recvmsg();  // { "message-with-fd", "message" }
    
    The bug fix in commit 9352c19 assumes this behavior. On Linux however,
    those messages can also come in like this:
    
      recvmsg();  // { "message", "message-with-fd" }
      recvmsg();  // { "message" }
    
    In other words, it's incorrect to assume that the file descriptor is
    always attached to the first message. This commit makes node wise up.
    
    Fixes #5330.
    bnoordhuis committed with piscisaureus May 10, 2013
Commits on May 9, 2013
  1. test: fix pummel/test-net-many-clients.js

    client sockets no longer emit 'connect' event inside the
    requestListener, update test-net-many-clients to reflect that
    tjfontaine committed May 6, 2013
Commits on May 8, 2013
  1. stream: make Readable.wrap support empty streams

    This makes Readable.wrap behave properly when the wrapped stream ends
    before emitting any data events.
    danielmoore committed with isaacs May 1, 2013
  2. stream: make Readable.wrap support objectMode

    Added a check to see if the stream is in objectMode before deciding
    whether to include or exclude data from an old-style wrapped stream.
    danielmoore committed with isaacs Apr 29, 2013
Commits on May 7, 2013
Commits on May 6, 2013
  1. build: only use DESTDIR instead of PREFIX for pkg

    Preserve default install prefix seen in process.config, but use DESTDIR
    for installing to deliniate 32/64 versions, avoid conflicts with PREFIX
    settings in config.mk
    tjfontaine committed May 2, 2013
Commits on May 3, 2013
  1. doc: update options for exec and execFile

    The stdio and customFds options are never used by exec or execFile,
    remove them from the documentation for these functions.
    kevinoid committed with bnoordhuis Apr 26, 2013
  2. build: vcbuild.bat fix for Visual Studio 2012

    Change vcbuild.bat to ignore VCINSTALLDIR environment variable,
    always check for specific VS version and set GYP_MSVS_VERSION
    accordingly. Otherwise GYP generates project files in format
    that cannot be compiled by VS2012.
    bajtos committed with piscisaureus May 3, 2013
Commits on May 2, 2013
  1. debugger: breakpoints in scripts not loaded yet

    When developer calls setBreakpoint with an unknown script name,
    we convert the script name into regular expression matching all
    paths ending with given name (name can be a relative path too).
    
    To create such breakpoint in V8, we use type `scriptRegEx`
    instead of `scriptId` for `setbreakpoint` request.
    
    To restore such breakpoint, we save the original script name
    send by the user. We use this original name to set (restore)
    breakpoint in the new child process.
    
    This is a back-port of commit 5db936d from the master branch.
    bajtos committed with bnoordhuis Apr 26, 2013
Commits on May 1, 2013
  1. Revert "deps: downgrade openssl to v1.0.0f"

    After much investigation it turns out that the affected servers are
    buggy.  user-service.condenastdigital.com:443 in particular seems to
    reject large TLS handshake records. Cutting down the number of
    advertised ciphers or disabling SNI fixes the issue.
    
    Similarly, passing { secureOptions: constants.SSL_OP_NO_TLSv1_2 }
    seems to fix most connection issues with IIS servers.
    
    Having to work around buggy servers is annoying for our users but not
    a reason to downgrade OpenSSL. Therefore, revert it.
    
    This reverts commit 4fdb8ac.
    bnoordhuis committed May 1, 2013
Commits on Apr 30, 2013
  1. doc: Fix require.extensions documentation

    1. The stability index must come first, or it messes up the markdown
    2. require.extensions is an Object, not an Array.
    
    Close #5387
    isaacs committed Apr 30, 2013
Commits on Apr 29, 2013
  1. deps: downgrade openssl to v1.0.0f

    Several people have reported issues with IIS and Resin servers (or maybe
    SSL terminators sitting in front of those servers) that are fixed by
    downgrading OpenSSL. The AESNI performance improvements were nice but
    stability is more important. Downgrade OpenSSL from 1.0.1e to 1.0.0f.
    
    Fixes #5360 (and others).
    bnoordhuis committed Apr 26, 2013