Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Branch: v0.11.8-release
Commits on Oct 30, 2013
  1. @tjfontaine

    2013.10.30, Version 0.11.8 (Unstable)

    tjfontaine authored
    * uv: Upgrade to v0.11.14
    * v8: upgrade
    * assert: indicate if exception message is generated (Glen Mailer)
    * buffer: add buf.toArrayBuffer() API (Trevor Norris)
    * cluster: fix premature 'disconnect' event (Ben Noordhuis)
    * crypto: add SPKAC support (Jason Gerfen)
    * debugger: count space for line numbers correctly (Alex Kocharin)
    * debugger: make busy loops SIGUSR1-interruptible (Ben Noordhuis)
    * debugger: repeat last command (Alex Kocharin)
    * debugger: show current line, fix for #6150 (Alex Kocharin)
    * dgram: send() can accept strings (Trevor Norris)
    * dns: rename domain to hostname (Ben Noordhuis)
    * dns: set hostname property on error object (Ben Noordhuis)
    * dtrace, mdb_v8: support more string, frame types (Dave Pacheco)
    * http: add statusMessage (Patrik Stutz)
    * http: expose supported methods (Ben Noordhuis)
    * http: provide backpressure for pipeline flood (isaacs)
    * process: Add exitCode property (isaacs)
    * tls: socket.renegotiate(options, callback) (Fedor Indutny)
    * util: format as Error if instanceof Error (Rod Vagg)
Commits on Oct 29, 2013
  1. @tjfontaine
  2. @tjfontaine

    uv: Upgrade to v0.11.14

    tjfontaine authored
  3. @trevnorris

    src: shorten Object{Wrap,Unwrap}

    trevnorris authored
    Going back to the original names of Wrap/Unwrap now that most all the
    class members that duplicate the name and functionality have been
  4. @trevnorris

    src: don't use class specific Unwrap methods

    trevnorris authored
    Instead use the template functions in util.h.
  5. @trevnorris

    src: don't use WeakObject::Unwrap

    trevnorris authored
    Switch out to use UnwrapObject from util.h.
  6. @trevnorris

    src: use function to get internal pointer

    trevnorris authored
    Remove the NODE_{WRAP,UNWRAP} macros and instead use template functions.
  7. @trevnorris

    node: don't share state with in_tick/last_threw

    trevnorris authored
    There was no need to share state between C++ and JS for these two
    values. So they have been moved to their respective locations. This will
    help performance only a tiny bit, but it does help code complexity much
  8. @sblom @trevnorris

    doc: Update documentation to reflect ObjectWrap changes

    sblom authored trevnorris committed
  9. @sblom @trevnorris

    win: fix ObjectWrap for latest v8

    sblom authored trevnorris committed
    We need to keep ObjectWrap around for module authors (we think), but
    v8 3.21 broke node_object_wrap.h with respect to MSVC. Coincidentally,
    we no longer use ObjectWrap at all in core, and native modules might
    as well use their own entirely internal implementation if they need it.
  10. @sblom

    src: Remove unused refs to node_object_wrap.h

    sblom authored
    Turns out that we don't use node_object_wrap.h any more in core,
    and, with v8 3.21, it's breaking our Windows build. Removing refs
    to it everywhere (and adding node.h in one case where it was the
    only way node.h was being included), we have restored the Windows
  11. @thomseddon @indutny

    src: accept passphrase when crypto signing with private key

    thomseddon authored indutny committed
    Previous behaviour was to drop to an openssl prompt
    ("Enter PEM pass phrase:") when supplying a private key with a
    passphrase. This change adds a fourth, optional, paramter that
    will be used as the passphrase.
    To include this parameter in a backwards compatible way it was
    necessary to expose the previously undocumented (and unexposed)
    feature of being able to explitly setting the output encoding.
Commits on Oct 28, 2013
  1. @trevnorris

    dgram: send() can accept strings

    trevnorris authored
    Strings passed to Socket#send() will be passed to Buffer and parsed as
  2. @isaacs
  3. @isaacs


    isaacs authored
  4. @isaacs

    vm: Copy missing properties from context

    isaacs authored
    This addresses a current shortcoming of the V8 SetNamedPropertyHandler
    It does not provide a way to intercept Object.defineProperty(..) calls.
    As a result, these properties are not copied onto the contextified
    sandbox when a new global property is added via either a function
    declaration or a Object.defineProperty(global, ...) call.
    Note that any function declarations or Object.defineProperty() globals
    that are created asynchronously (in a setTimeout, callback, etc.) will
    happen AFTER the call to copy properties, and thus not be caught.
    The way to properly fix this is to add some sort of a
    Object::SetNamedDefinePropertyHandler() function that takes a callback,
    which receives the property name and property descriptor as arguments.
    Luckily, such situations are rare, and asynchronously-added globals
    weren't supported by Node's VM module until 0.12 anyway.  But, this
    should be fixed properly in V8, and this copy function should be removed
    once there is a better way.
    Fix #6416
  5. @bnoordhuis

    http: remove MethodToString()

    bnoordhuis authored
    The list of supported HTTP methods is available in JS land now so there
    is no longer any need to pass a stringified version of the method to the
    parser callback, it can look up the method name for itself.
    Saves a call to v8::Eternal::Get() in the common case and a costly
    v8::String::NewFromOneByte() in the uncommon case.
  6. @bnoordhuis

    http: expose supported methods

    bnoordhuis authored
    Expose the list of supported HTTP methods as a property on the 'http'
    module object.
    Fixes #6422.
Commits on Oct 27, 2013
  1. @phillipalexander @bnoordhuis
  2. @rmg @bnoordhuis

    doc: improve module documentation

    rmg authored bnoordhuis committed
    Expands on when to use module.exports vs. exports. This is a recurring
    question on mailing list and continues to confuse new devs.
Commits on Oct 25, 2013
  1. @sam-github @bnoordhuis

    doc: fix missing backtick in 2e16037

    sam-github authored bnoordhuis committed
  2. @tjfontaine

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

    tjfontaine authored
  3. @mscdex @tjfontaine

    doc: streams: document default objectMode setting

    mscdex authored tjfontaine committed
  4. @bogushevich @indutny

    debugger: Fix bug in sb() with unnamed script

    bogushevich authored indutny committed
    setBreakpoint() cause error when unnamed script is loaded
Commits on Oct 24, 2013
  1. @isaacs


    isaacs authored
  2. @bnoordhuis

    build: fix test-gc weakref build rule

    bnoordhuis authored
    Make the build rule depend on the build artifact (weakref.node) itself
    rather than the directory it's built in.  Depending on the directory
    means that a build failure won't trigger a rebuild on the next
    invocation because the directory's timestamp has been updated.
    This is a back-port of commit 1189571 from the master branch that
    hopefully fixes the following CI error:
        executing:  make test/gc/node_modules/weak/build/
        make: *** No rule to make target `test/gc/node_modules/weak/build/'.
        Command exited with non-zero: make test/gc/node_modules/weak/build/
        Build step 'Execute NodeJS script' marked build as failure
  3. @ManInTheBox @bnoordhuis

    doc: add to the community page

    ManInTheBox authored bnoordhuis committed
Commits on Oct 23, 2013
  1. @isaacs

    http client: pull last chunk on socket close

    isaacs authored
    When the socket closes, the client's http incoming message object was
    emitting an 'aborted' event if it had not yet been ended.
    However, it's possible, when a response is being repeatedly paused and
    resumed (eg, if piped to a slow FS write stream), that there will be a
    final chunk remaining in the js-land buffer when the socket is torn
    When that happens, the socketCloseListener function detects that we have
    not yet reached the end of the response message data, and treats this as
    an abrupt abort, immediately (and forcibly) ending the incoming message
    data stream, and discarding that final chunk of data.
    The result is that, for example, npm will have problems because tarballs
    are missing a few bytes off the end, every time.
    Closes GH-6402
  2. @bnoordhuis @tjfontaine

    test: fix up after v8 api change

    bnoordhuis authored tjfontaine committed
  3. @bnoordhuis @tjfontaine

    build: fix test-gc weakref build rule

    bnoordhuis authored tjfontaine committed
    Make the build rule depend on the build artifact (weakref.node) itself
    rather than the directory it's built in.  Depending on the directory
    means that a build failure won't trigger a rebuild on the next
    invocation because the directory's timestamp has been updated.
  4. @bnoordhuis @tjfontaine

    src: update after v8 api changes

    bnoordhuis authored tjfontaine committed
  5. @tjfontaine

    v8: upgrade

    tjfontaine authored
  6. @bnoordhuis
Commits on Oct 22, 2013
  1. @isaacs

    blog: HTTP server DoS vulnerability details

    isaacs authored
Commits on Oct 18, 2013
  1. @tjfontaine

    blog: Post for v0.10.21

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