summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* npm: upgrade to 1.4.6isaacs2014-03-25318-4042/+5566
| | | | | | | | | * Documentation upgrades * Fix glob bug which prevents proper README publishing * node-gyp upgrade to 0.13 * Documentation updates * Add --save-exact to save an exact dep (instead of a range) * alias 't' to 'test'
* build: fix g++ 4.8 build, disable -WerrorBen Noordhuis2014-03-232-3/+1
| | | | | | | | | Turn off -Werror when building V8, it hits -Werror=unused-local-typedefs with g++ 4.8. The warning itself is harmless so don't abort the build. This was originally implemented in commit d2ab314e back in 2011 but the build process has gone through a few iterations since then, that change no longer works.
* doc: remove an unused arg in process.stdin.Shuhei Kagawa2014-03-101-1/+1
| | | | The argument of process.stdin's readable event handler is not used.
* crypto: do not lowercase cipher/hash namesFedor Indutny2014-03-112-3/+10
| | | | | | | `crypto.getCiphers()` and `crypto.getHashes()` should prefer lower-case variants of names, but should not introduce them. fix #7282
* deps: fix v8 valgrind warningBen Noordhuis2014-03-071-1/+1
| | | | | | | | | | | | | | | | Fix the following valgrind warning: Conditional jump or move depends on uninitialised value(s) at 0x7D64E7: v8::internal::GlobalHandles::IterateAllRootsWithClassIds(v8::internal::ObjectVisitor*) (global-handles.cc:613) by 0x94DCDC: v8::internal::NativeObjectsExplorer::FillRetainedObjects() (profile-generator.cc:2849) # etc. This was fixed upstream in r12903 and released in 3.15.2 but that commit was never back-ported to the 3.14 branch that node.js v0.10 uses. The code itself works okay; this commit simply shuffles the clauses in an `if` statement to check that the node is in use before checking its class id (which is uninitialized if the node is not in use.)
* child_process: fix sending handle twiceFedor Indutny2014-03-051-1/+10
| | | | | | | | | | | | | | | When sending a socket to a child process via IPC pipe, `child_process.js` picks a raw UV handle from `_handle` property, sends it, and assigns `null` to the property. Sending the same socket twice was resulting in a runtime error, since we weren't handling the empty `_handle` case. In case of `null` `_handle` we should send just a plain text message as passed it was passed to `.send()` and ignore the handle, letting users handle such cases themselves instead of throwing the error at runtime. fix #5469
* test: test sending a handle twiceBenoit Vallée2014-03-051-0/+56
| | | | | Added test-cluster-send-handle-twice.js testing to send a handle twice to the parent process.
* src: add default visibility to NODE_MODULEBen Noordhuis2014-03-051-1/+1
| | | | | | | | | | | | | | | It's currently not really possible to compile native add-ons with -fvisibility=hidden because that also hides the struct containing the module definition. The NODE_MODULE() and NODE_MODULE_DECL() macros are structured in a way that makes it impossible to add a visibility attribute manually so there is no escape hatch there. That's why this commit adds an explicit visibility attribute to the module definition. It doesn't help with node.js releases that are already out there but at least it improves the situation going forward.
* timer: don't reschedule timer bucket in a domainGreg Brail2014-03-032-0/+82
| | | | | | | | | | | | | | | | If two timers run on the same tick, and the first timer uses a domain, and then catches an exception and disposes of the domain, then the second timer never runs. (And even if the first timer does not dispose of the domain, the second timer could run under the wrong domain.) This happens because timer.js uses "process.nextTick()" to schedule continued processing of the timers for that tick. However, there was an exception inside a domain, then "process.nextTick()" runs under the domain of the first timer function, and will do nothing if the domain has been disposed. To avoid this, we temporarily save the value of "process.domain" before calling nextTick so that it does not run inside any domain.
* src: domain should not replace nextTick functionTimothy J Fontaine2014-03-034-3/+38
| | | | | | | | Previously if you cached process.nextTick and then require('domain') subsequent nextTick() calls would not be caught because enqueued functions were taking the wrong path. This keeps nextTick to a single function reference and changes the implementation details after domain has been required.
* test: add `agent: null` http client request testNathan Rajlich2014-02-261-0/+47
| | | | | This is just the test portion from #7012 / #7189, but targetted for the v0.10 branch.
* http: invoke createConnection when no agentNathan Rajlich2014-02-262-1/+50
| | | | | | | | | | | This makes it so that the user may pass in a `createConnection()` option, and they don't have to pass `agent: false` at the same time. Also adding a test for the `createConnection` option, since none was in place before. See #7014.
* assert: Ensure reflexivity of deepEqualMike Pennisi2014-02-252-4/+10
| | | | | | Ensure that the behavior of `assert.deepEqual` does not depend on argument ordering when comparing an `arguments` object with a non-`arguments` object.
* stream: remove useless checkBrian White2014-02-241-2/+1
|
* doc: update assert.markdownNicolas Talle2014-02-231-2/+2
| | | | Update assert.throws() and assert.doesNotThrow() docs
* installer: copy `node.d` only with node_use_dtraceFedor Indutny2014-02-211-4/+2
|
* dtrace: workaround linker bug on FreeBSDFedor Indutny2014-02-211-2/+2
|
* configure: allow --with-dtrace on freebsdFedor Indutny2014-02-211-0/+2
|
* gyp: specialize node.d for freebsdFedor Indutny2014-02-213-3/+65
| | | | | `node.d` should use `psinfo.d` instead of `procfs.d` and have statically defined architecture on FreeBSD.
* tools: update to support separate website repoTimothy J Fontaine2014-02-181-11/+11
|
* Now working on v0.10.27Timothy J Fontaine2014-02-181-2/+2
|
* Merge branch 'v0.10.26-release' into v0.10Timothy J Fontaine2014-02-186-2/+39
|\
| * build: readd missing installer resourcesv0.10.26v0.10.26-releaseTimothy J Fontaine2014-02-183-0/+0
| | | | | | | | This were accidentally moved during the website refactor
| * 2014.02.18, Version 0.10.26 (Stable)Timothy J Fontaine2014-02-183-2/+39
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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)
* docs: clarify process.stdin and old modeAnton Khlynovskiy2014-02-181-5/+17
|
* doc: stdout blocking or non-blocking behaviourPedro Ballesteros2014-02-181-6/+14
| | | | | Makes clear that the behaviour of stdout is blocking in Linux/Unix even when they refer to pipes.
* test: make test-net-error-twice less raceyTimothy J Fontaine2014-02-181-2/+5
|
* uv: Upgrade to v0.10.25Timothy J Fontaine2014-02-1811-13/+143
|
* doc: mention objectMode for Writable streamsRaynos2014-02-181-0/+3
|
* debugger: Fix breakpoint not showing after restartFarid Neshat2014-02-172-3/+13
| | | | | | | | | | 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
* npm: upgrade to 1.4.3isaacs2014-02-17175-609/+1556
|
* zlib: introduce pending close stateFedor Indutny2014-02-182-1/+52
| | | | | | zlib should not crash in `close()` if the write is still in progress. fix #7101
* doc: re-add node.1 man pageTimothy J Fontaine2014-02-141-0/+448
| | | | | | | The man page was accidentally removed in 37376de for the website refactor, bring it back. Fixes #7117
* npm: Upgrade to v1.4.0isaacs2014-02-13176-2139/+1261
| | | | | | | - Removes 'npm publish -f' - Documentation - Bug-fixes - Update license etc to refer to npm, Inc. rather than @isaacs personally
* website: move website to joyent/node-websiteTimothy J Fontaine2014-02-13333-24345/+4
| | | | | The website will no longer be living in the source repository instead it can be found at http://github.com/joyent/node-website
* doc: changed timer id to objectChristian2014-02-131-6/+6
| | | | fix #7074
* net: do not re-emit stream errorsFedor Indutny2014-02-103-3/+56
| | | | fix #7015
* src: refactor buffer bounds checkingTimothy J Fontaine2014-02-085-9/+23
| | | | | Consolidate buffer bounds checking logic into Buffer namespace and use it consistently throughout the source.
* npm: upgrade to 1.3.26isaacs2014-02-08213-250/+238
|
* doc: fix diffieHellman.getGenerator() descriptionBrian White2014-02-091-1/+1
|
* Revert "dns: validate arguments in resolve"Fedor Indutny2014-02-082-32/+0
| | | | This reverts commit 56e80a37e0df0d131d3a3ad6426d52f887ef8e94.
* Revert "dns: verify argument is valid function in resolve"Fedor Indutny2014-02-081-3/+1
| | | | This reverts commit 2ee86c624ecd6b9dbaad10989143325fc64778cd.
* dns: verify argument is valid function in resolveKenan Sulayman2014-02-081-1/+3
| | | | | | 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)").
* dns: validate arguments in resolveKenan Sulayman2014-02-082-0/+32
| | | | | | Mitigat C++-land assertion error, add test accordingly. fix #7070
* website: update cla email addressTimothy J Fontaine2014-02-071-2/+2
|
* fs: make unwatchFile() insensitive to pathiamdoron2014-02-062-0/+25
|
* doc: fix references to error keywordBenjamin Waters2014-02-041-2/+2
| | | | | | | References for err.signal and err.code should be error.signal and error.code. Fixes joyent/node#6862
* crypto: update root certificatesBen Noordhuis2014-02-042-3587/+3565
| | | | | | | | 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.
* doc: add an example about multiple extensionsMaxime Quandalle2014-02-031-0/+4
| | | | `path.extname` returns only the last extension
* dtrace: fix arguments warningFedor Indutny2014-02-011-2/+2
| | | | | Add enough arguments to `NODE_NET_SOCKET_READ()` and `NODE_NET_SOCKET_WRITE()` stubs.