summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* 2013.11.12, Version 0.10.22 (Stable)v0.10.22v0.10.22-releaseTimothy J Fontaine2013-11-123-2/+26
| | | | | | | | | | | | | | | | | | | | * npm: Upgrade to 1.3.14 * uv: Upgrade to v0.10.19 * child_process: don't assert on stale file descriptor events (Fedor Indutny) * darwin: Fix "Not Responding" in Mavericks activity monitor (Fedor Indutny) * debugger: Fix bug in sb() with unnamed script (Maxim Bogushevich) * repl: do not insert duplicates into completions (Maciej Małecki) * src: Fix memory leak on closed handles (Timothy J Fontaine) * tls: prevent stalls by using read(0) (Fedor Indutny) * v8: use correct timezone information on Solaris (Maciej Małecki)
* src: add HandleScope in HandleWrap::OnCloseTimothy J Fontaine2013-11-122-0/+13
| | | | | | | | | | | | | | | Fixes a 4 byte leak on handles closing. AKA The Walmart leak. MakeCallback doesn't have a HandleScope. That means the callers scope will retain ownership of created handles from MakeCallback and related. There is by default a wrapping HandleScope before uv_run, if the caller doesn't have a HandleScope on the stack the global will take ownership which won't be reaped until the uv loop exits. If a uv callback is fired, and there is no enclosing HandleScope in the cb, you will appear to leak 4-bytes for every invocation. Take heed. cc @hueniverse
* uv: Upgrade to v0.10.19Timothy J Fontaine2013-11-1221-37/+528
|
* v8: use correct timezone information on Solarisyangguo@chromium.org2013-11-121-6/+2
| | | | | | | | | | | | | | | | | `timezone` variable contains the difference, in seconds, between UTC and local standard time (see `man 3 localtime` on Solaris). Call to `tzset` is required to apply contents of `TZ` variable to `timezone` variable. BUG=v8:2064 Review URL: https://chromiumcodereview.appspot.com/10967066 Patch from Maciej Małecki <me@mmalecki.com>. This is a back-port of upstream commit r12802 and a forward port of commit 9fa953d from the v0.8 branch. V8 3.22 in the master branch contains the patch so no further forward-porting is necessary.
* repl: do not insert duplicates into completionsMaciej Małecki2013-11-112-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | Fix invalid `hasOwnProperty` function usage. For example, before in the REPL: ``` > Ar<Tab> Array Array ArrayBuffer ``` Now: ``` > Ar<Tab> Array ArrayBuffer ``` Fixes #6255. Closes #6498.
* gyp: update to bebdceaTimothy J Fontaine2013-11-1040-2139/+2225
|
* v8: unbreak `make native` buildBen Noordhuis2013-11-091-11/+0
| | | | | | | | | | | | The security fix from commit 6b92a713 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/test-api.cc: In function ‘void TestRegress260106()’: ../test/cctest/test-api.cc:17712:34: error: ‘class v8::Context’ has no member named ‘GetIsolate’
* tls: prevent stalls by using read(0)Fedor Indutny2013-11-092-4/+85
| | | | | | | Do not `.push()` the same data as just passed to `.ondata()`, it may be read by 'data' event listeners. fix #6277
* npm: Upgrade to 1.3.14isaacs2013-11-08209-217/+235
|
* doc: encoding is ignored if input is a BufferFedor Indutny2013-11-071-0/+3
| | | | | | NOTE: it wasn't in 0.8 fixes #6386
* doc: Correct and add several itemsisaacs2013-10-311-27/+50
| | | | | Several names/urls were out of date, and some really awesome stuff was missing.
* doc: document node signal handlingSam Roberts2013-10-311-2/+27
| | | | Partly lifted from uv.h, partly from observation of node.cc.
* blog: Post for v0.11.8Timothy J Fontaine2013-10-301-0/+96
|
* doc: dgram: reword dgram.Socket#send() docsBen Noordhuis2013-10-291-15/+19
| | | | | | | Make it clear that the address argument is not really optional and fix some Engrish and long lines while we're here. Fixes #6433.
* npm@1.3.13isaacs2013-10-28158-210/+928
|
* doc: fs: clarify fs.symlink Windows specific argsPhillip Alexander2013-10-271-2/+2
|
* doc: improve module documentationRyan Graham2013-10-272-24/+58
| | | | | Expands on when to use module.exports vs. exports. This is a recurring question on mailing list and continues to confuse new devs.
* doc: fix missing backtick in 2e16037Sam Roberts2013-10-251-1/+1
|
* doc: streams: document default objectMode settingBrian White2013-10-251-1/+1
|
* debugger: Fix bug in sb() with unnamed scriptMaxim Bogushevich2013-10-251-1/+3
| | | | setBreakpoint() cause error when unnamed script is loaded
* npm@1.3.12isaacs2013-10-24291-1186/+1712
|
* build: fix test-gc weakref build ruleBen Noordhuis2013-10-241-3/+3
| | | | | | | | | | | | | | | 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
* doc: add nodejs.rs to the community pageZarko Stankovic2013-10-241-0/+2
|
* src: IsInt64() should return bool, not intBen Noordhuis2013-10-231-1/+1
|
* blog: HTTP server DoS vulnerability detailsisaacs2013-10-221-0/+37
| | | | CVE-2013-4450
* blog: Post for v0.10.21Timothy J Fontaine2013-10-181-0/+71
|
* blog: Post for v0.8.26Timothy J Fontaine2013-10-181-0/+71
|
* Now working on 0.10.22Timothy J Fontaine2013-10-181-2/+2
|
* Merge branch 'v0.10.21-release' into v0.10Timothy J Fontaine2013-10-182-2/+17
|\
| * 2013.10.18, Version 0.10.21 (Stable)v0.10.21v0.10.21-releaseTimothy J Fontaine2013-10-182-2/+17
|/ | | | | | | | | | | | | | * 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)
* crypto: clear errors from verify failureTimothy J Fontaine2013-10-182-0/+84
| | | | | | | 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
* uv: Upgrade to v0.10.18Timothy J Fontaine2013-10-189-540/+301
|
* http: provide backpressure for pipeline floodisaacs2013-10-162-5/+151
| | | | | | | | | 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
* http_parser: expose pause/resume method for parserTimothy J Fontaine2013-10-161-0/+11
|
* doc: cluster documentation cleanup and correctionsSam Roberts2013-10-161-85/+141
| | | | | | | | | | | | | | | | | | | | | | | - 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 arguments - 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.
* doc: child_process corrections and cleanupsSam Roberts2013-10-161-19/+25
| | | | | | | | | | - 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
* doc: http: reword IncomingMessage 'close' eventBen Noordhuis2013-10-161-5/+2
| | | | | | | The bit that says "before response.end() was called or able to flush" doesn't apply to incoming streams. Fixes #6359.
* doc: http: add cross-links for easier clickingBen Noordhuis2013-10-161-24/+33
| | | | | Make it a little easier to navigate the http module documentation by turning class names and methods into links to the appropriate section.
* doc: expand os.loadavg() sectionBen Noordhuis2013-10-151-1/+8
| | | | | | | 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.
* doc: document os.loadavg() behavior on windowsBen Noordhuis2013-10-141-0/+1
| | | | | The load average is a very UNIX-y concept. That's why os.loadavg() always returns zeros on Windows. Mention that in the documentation.
* test: use proper findjsobjects output formatDave Pacheco2013-10-101-1/+1
| | | | Closes #6329
* doc: net: remove bad net.Server descriptionBen Noordhuis2013-10-101-1/+0
| | | | net.Server is not an instance of net.Socket so don't say it is.
* doc: addon: fix object instantiation examplesBen Noordhuis2013-10-101-41/+71
| | | | | | | | | | | * Extend examples to show how to handle non-constructor invocation in constructor callback functions. * Fix up examples to initialize member variables at object construction. * Fix up a few naming inconsistencies. Fixes #5701.
* blog: Remove wp-to-markdown scriptisaacs2013-10-091-189/+0
|
* tls: fix premature connection terminationBen Noordhuis2013-10-091-1/+1
| | | | | | | | | | Destroying the TLS session implies destroying the underlying socket but before this commit, that was done with net.Socket#destroy() rather than net.Socket#destroySoon(). The former closes the connection right away, even when there is still data to write. In other words, sometimes the final TLS record got truncated. Fixes #6107.
* dtrace: backport two byte string fixDave Pacheco2013-10-092-27/+125
| | | | | | | This is a partial backport of 5921158 Re #6309 Closes #6319
* fs: fix fs.truncate() file content zeroing bugBen Noordhuis2013-10-082-2/+46
| | | | | | | | | | | | | | | | fs.truncate() and its synchronous sibling are implemented in terms of open() + ftruncate(). Unfortunately, it opened the target file with mode 'w' a.k.a. 'write-only and create or truncate at open'. The subsequent call to ftruncate() then moved the end-of-file pointer from zero to the requested offset with the net result of a file that's neatly truncated at the right offset and filled with zero bytes only. This bug was introduced in commit 168a5557 but in fairness, before that commit fs.truncate() worked like fs.ftruncate() so it seems we've never had a working fs.truncate() until now. Fixes #6233.
* doc: add warning to fs.exists() documentationBen Noordhuis2013-10-051-0/+7
| | | | | Warn against the open-if-exists anti-pattern, it's susceptible to race conditions.
* doc: link to pre-built binaries, add install noteBen Noordhuis2013-10-011-0/+13
| | | | | | | lLnk to http://nodejs.org/download/ and add a short primer on how to extract the tarballs. Fixes #6292.
* blog: Post for v0.10.20Timothy J Fontaine2013-09-301-0/+59
|
View Lorry Controller Status