Commits on Nov 10, 2013
  1. gyp: update to bebdcea

    tjfontaine committed Nov 10, 2013
Commits on Nov 9, 2013
  1. v8: unbreak `make native` build

    The security fix from commit 6b92a71 also back-ported the test case.
    Said test case relies on API that is only available in newer versions
    of V8 and, as a result, broke the `make native` and `make <arch.mode>`
    builds.  This commit reverts that part of the back-port.  Fixes the
    following build error:
      ../test/cctest/ In function ‘void TestRegress260106()’:
      ../test/cctest/ error: ‘class v8::Context’ has
      no member named ‘GetIsolate’
    bnoordhuis committed Nov 9, 2013
Commits on Nov 8, 2013
  1. tls: prevent stalls by using read(0)

    Do not `.push()` the same data as just passed to `.ondata()`, it
    may be read by 'data' event listeners.
    fix #6277
    indutny committed Nov 7, 2013
  2. npm: Upgrade to 1.3.14

    isaacs committed Nov 8, 2013
Commits on Nov 7, 2013
  1. doc: encoding is ignored if input is a Buffer

    NOTE: it wasn't in 0.8
    fixes #6386
    indutny committed with tjfontaine Oct 21, 2013
Commits on Oct 31, 2013
  1. doc: Correct and add several items

    Several names/urls were out of date, and some really
    awesome stuff was missing.
    isaacs committed Oct 31, 2013
  2. doc: document node signal handling

    Partly lifted from uv.h, partly from observation of
    sam-github committed with bnoordhuis Oct 30, 2013
Commits on Oct 30, 2013
  1. blog: Post for v0.11.8

    tjfontaine committed Oct 30, 2013
Commits on Oct 29, 2013
  1. doc: dgram: reword dgram.Socket#send() docs

    Make it clear that the address argument is not really optional and fix
    some Engrish and long lines while we're here.
    Fixes #6433.
    bnoordhuis committed Oct 29, 2013
Commits on Oct 28, 2013
  1. npm@1.3.13

    isaacs committed Oct 28, 2013
Commits on Oct 27, 2013
  1. doc: improve module documentation

    Expands on when to use module.exports vs. exports. This is a recurring
    question on mailing list and continues to confuse new devs.
    rmg committed with bnoordhuis Oct 26, 2013
Commits on Oct 25, 2013
  1. debugger: Fix bug in sb() with unnamed script

    setBreakpoint() cause error when unnamed script is loaded
    bogushevich committed with indutny Oct 22, 2013
Commits on Oct 24, 2013
  1. npm@1.3.12

    isaacs committed Oct 24, 2013
  2. build: fix test-gc weakref build rule

    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
    bnoordhuis committed Oct 23, 2013
Commits on Oct 23, 2013
Commits on Oct 22, 2013
  1. blog: HTTP server DoS vulnerability details

    isaacs committed Oct 22, 2013
Commits on Oct 18, 2013
  1. blog: Post for v0.10.21

    tjfontaine committed Oct 18, 2013
  2. blog: Post for v0.8.26

    tjfontaine committed Oct 18, 2013
  3. Now working on 0.10.22

    tjfontaine committed Oct 18, 2013
  4. 2013.10.18, Version 0.10.21 (Stable)

    * 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)
    tjfontaine committed Oct 18, 2013
  5. crypto: clear errors from verify failure

    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
    tjfontaine committed Oct 18, 2013
  6. uv: Upgrade to v0.10.18

    tjfontaine committed Oct 18, 2013
Commits on Oct 17, 2013
  1. http: provide backpressure for pipeline flood

    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
    isaacs committed with trevnorris Oct 16, 2013
Commits on Oct 16, 2013
  1. doc: cluster documentation cleanup and corrections

    - 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.
    sam-github committed with trevnorris Jul 26, 2013
  2. doc: child_process corrections and cleanups

    - 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
    sam-github committed with trevnorris Jul 26, 2013
  3. doc: http: reword IncomingMessage 'close' event

    The bit that says "before response.end() was called or able to flush"
    doesn't apply to incoming streams.
    Fixes #6359.
    bnoordhuis committed Oct 16, 2013
  4. doc: http: add cross-links for easier clicking

    Make it a little easier to navigate the http module documentation by
    turning class names and methods into links to the appropriate section.
    bnoordhuis committed Oct 16, 2013
Commits on Oct 15, 2013
  1. doc: expand os.loadavg() section

    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.
    bnoordhuis committed Oct 15, 2013
Commits on Oct 14, 2013
  1. doc: document os.loadavg() behavior on windows

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