Skip to content
Commits on Feb 18, 2014
  1. @tjfontaine

    build: readd missing installer resources

    tjfontaine committed
    This were accidentally moved during the website refactor
  2. @tjfontaine

    2014.02.18, Version 0.10.26 (Stable)

    tjfontaine committed
    * uv: Upgrade to v0.10.25 (Timothy J Fontaine)
    
    * npm: upgrade to 1.4.3 (isaacs)
    
    * v8: support compiling with VS2013 (Fedor Indutny)
    
    * cares: backport TXT parsing fix (Fedor Indutny)
    
    * crypto: throw on SignFinal failure (Fedor Indutny)
    
    * crypto: update root certificates (Ben Noordhuis)
    
    * debugger: Fix breakpoint not showing after restart (Farid Neshat)
    
    * fs: make unwatchFile() insensitive to path (iamdoron)
    
    * net: do not re-emit stream errors (Fedor Indutny)
    
    * net: make Socket destroy() re-entrance safe (Jun Ma)
    
    * net: reset `endEmitted` on reconnect (Fedor Indutny)
    
    * node: do not close stdio implicitly (Fedor Indutny)
    
    * zlib: avoid assertion in close (Fedor Indutny)
  3. @subzey @tjfontaine
  4. @nitroduna @tjfontaine

    doc: stdout blocking or non-blocking behaviour

    nitroduna committed with tjfontaine
    Makes clear that the behaviour of stdout is blocking
    in Linux/Unix even when they refer to pipes.
  5. @tjfontaine
  6. @tjfontaine

    uv: Upgrade to v0.10.25

    tjfontaine committed
  7. @Raynos @tjfontaine
  8. @alFReD-NSH @tjfontaine

    debugger: Fix breakpoint not showing after restart

    alFReD-NSH committed with tjfontaine
    The reason this wasn't working was because after restart, when restoring
    breakpoints the scripts wasn't loaded, so the breakpoint.script was
    undefined. As a fix I added another check to use breakpoint.scriptReq
    instead of breakpoint.script, which is the same except when the
    breakpoint is a function.
    
    fixes #7027
  9. @isaacs @tjfontaine

    npm: upgrade to 1.4.3

    isaacs committed with tjfontaine
Commits on Feb 17, 2014
  1. @indutny

    zlib: introduce pending close state

    indutny committed
    zlib should not crash in `close()` if the write is still in progress.
    
    fix #7101
Commits on Feb 14, 2014
  1. @tjfontaine

    doc: re-add node.1 man page

    tjfontaine committed
    The man page was accidentally removed in 37376de for the website
    refactor, bring it back.
    
    Fixes #7117
  2. @isaacs @tjfontaine

    npm: Upgrade to v1.4.0

    isaacs committed with tjfontaine
    - Removes 'npm publish -f'
    - Documentation
    - Bug-fixes
    - Update license etc to refer to npm, Inc. rather than @isaacs personally
Commits on Feb 13, 2014
  1. @tjfontaine

    website: move website to joyent/node-website

    tjfontaine committed
    The website will no longer be living in the source repository instead
    it can be found at http://github.com/joyent/node-website
Commits on Feb 12, 2014
  1. @makepanic @indutny

    doc: changed timer id to object

    makepanic committed with indutny
    fix #7074
Commits on Feb 10, 2014
  1. @indutny @tjfontaine
Commits on Feb 8, 2014
  1. @tjfontaine

    src: refactor buffer bounds checking

    tjfontaine committed
    Consolidate buffer bounds checking logic into Buffer namespace and use
    it consistently throughout the source.
  2. @isaacs @tjfontaine

    npm: upgrade to 1.3.26

    isaacs committed with tjfontaine
  3. @mscdex @indutny
Commits on Feb 7, 2014
  1. @indutny

    Revert "dns: validate arguments in resolve"

    indutny committed
    This reverts commit 56e80a3.
  2. @indutny
  3. @KenanSulayman @indutny

    dns: verify argument is valid function in resolve

    KenanSulayman committed with indutny
    Don't use argument as callback if it's not a valid callback function.
    Throw a valid exception instead explaining the issue. Adds to #7070
    ("DNS — Throw meaningful error(s)").
  4. @KenanSulayman @indutny

    dns: validate arguments in resolve

    KenanSulayman committed with indutny
    Mitigat  C++-land assertion error, add test accordingly.
    
    fix #7070
  5. @tjfontaine
Commits on Feb 6, 2014
  1. @iamdoron @indutny
Commits on Feb 4, 2014
  1. @Benjamin-Waters @indutny

    doc: fix references to error keyword

    Benjamin-Waters committed with indutny
    References for err.signal and err.code should be error.signal and
    error.code.
    
    Fixes nodejs/node-v0.x-archive#6862
Commits on Feb 3, 2014
  1. @bnoordhuis @indutny

    crypto: update root certificates

    bnoordhuis committed with indutny
    Update the list of root certificates in src/node_root_certs.h with
    tools/mk-ca-bundle.pl and update src/node_crypto.cc to make use of
    the new format.
    
    Fixes #6013.
  2. @mquandalle @indutny

    doc: add an example about multiple extensions

    mquandalle committed with indutny
    `path.extname` returns only the last extension
Commits on Jan 31, 2014
  1. @indutny

    dtrace: fix arguments warning

    indutny committed
    Add enough arguments to `NODE_NET_SOCKET_READ()` and
    `NODE_NET_SOCKET_WRITE()` stubs.
  2. @indutny

    deps: backport 883637bd from latest v8

    indutny committed
    Original commit message:
    
      VS2013 contains a number of improvements, most notably the addition
      of all C99 math functions.
    
      I'm a little bit concerned about the change I had to make in
      cpu-profiler.cc, but I spent quite a bit of time looking at it and was
      unable to figure out any rational explanation for the warning. It's
      possible it's spurious. Since it seems like a useful warning in
      general   though, I chose not to disable globally at the gyp level.
    
      I do think someone with expertise here should probably try to
      determine if this is a legitimate warning.
    
      BUG=288948
      R=dslomov@chromium.org
    
      Review URL: https://codereview.chromium.org/23449035
    
    NOTE: Path applied without `cpu-profiler.cc` changes because in our
    version it was looking totally different.
Commits on Jan 30, 2014
  1. @indutny

    node: do not ever close stdio

    indutny committed
    Even if stdio streams are opened as file streams, we should not ever try
    to close them. This could be accomplished by passing `autoClose: false`
    in options on their creation.
Commits on Jan 29, 2014
  1. @tjfontaine

    blog: Post for v0.11.11

    tjfontaine committed
Commits on Jan 28, 2014
  1. @geek @indutny
Commits on Jan 27, 2014
  1. @roamm @indutny

    net: make Socket destroy() re-entrance safe

    roamm committed with indutny
    So that we are free to call socket.destroy() in error event handler.
    
    fix #6769
Commits on Jan 26, 2014
  1. @indutny
Commits on Jan 25, 2014
  1. @indutny @tjfontaine
Something went wrong with that request. Please try again.