- Mar 05, 2014
-
-
Ben Noordhuis authored
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.
-
- Mar 04, 2014
-
-
Greg Brail authored
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.
-
Timothy J Fontaine authored
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.
-
- Feb 27, 2014
-
-
Nathan Rajlich authored
This is just the test portion from #7012 / #7189, but targetted for the v0.10 branch.
-
Nathan Rajlich authored
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.
-
- Feb 26, 2014
-
-
Mike Pennisi authored
Ensure that the behavior of `assert.deepEqual` does not depend on argument ordering when comparing an `arguments` object with a non-`arguments` object.
-
- Feb 24, 2014
-
-
Brian White authored
-
- Feb 23, 2014
-
-
Nicolas Talle authored
Update assert.throws() and assert.doesNotThrow() docs
-
- Feb 21, 2014
-
-
Fedor Indutny authored
-
Fedor Indutny authored
-
Fedor Indutny authored
-
Fedor Indutny authored
`node.d` should use `psinfo.d` instead of `procfs.d` and have statically defined architecture on FreeBSD.
-
- Feb 19, 2014
-
-
Timothy J Fontaine authored
-
Timothy J Fontaine authored
-
Timothy J Fontaine authored
-
Timothy J Fontaine authored
This were accidentally moved during the website refactor
-
Timothy J Fontaine authored
* 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)
-
Anton Khlynovskiy authored
-
Pedro Ballesteros authored
Makes clear that the behaviour of stdout is blocking in Linux/Unix even when they refer to pipes.
-
Timothy J Fontaine authored
-
Timothy J Fontaine authored
-
Raynos authored
-
- Feb 18, 2014
-
-
Farid Neshat authored
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
-
isaacs authored
-
Fedor Indutny authored
zlib should not crash in `close()` if the write is still in progress. fix #7101
-
- Feb 15, 2014
-
-
Timothy J Fontaine authored
The man page was accidentally removed in 37376deb for the website refactor, bring it back. Fixes #7117
-
- Feb 14, 2014
-
-
isaacs authored
- Removes 'npm publish -f' - Documentation - Bug-fixes - Update license etc to refer to npm, Inc. rather than @isaacs personally
-
Timothy J Fontaine authored
The website will no longer be living in the source repository instead it can be found at http://github.com/joyent/node-website
-
- Feb 13, 2014
-
-
Christian authored
fix #7074
-
- Feb 11, 2014
-
-
Fedor Indutny authored
fix #7015
-
- Feb 09, 2014
-
-
Timothy J Fontaine authored
Consolidate buffer bounds checking logic into Buffer namespace and use it consistently throughout the source.
-
isaacs authored
-
Brian White authored
-
- Feb 08, 2014
-
-
Fedor Indutny authored
This reverts commit 56e80a37.
-
Fedor Indutny authored
This reverts commit 2ee86c62.
-
Kenan Sulayman authored
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)"). -
Kenan Sulayman authored
Mitigat C++-land assertion error, add test accordingly. fix #7070
-
Timothy J Fontaine authored
-
- Feb 06, 2014
-
-
iamdoron authored
-
- Feb 04, 2014
-
-
Benjamin Waters authored
References for err.signal and err.code should be error.signal and error.code. Fixes joyent/node#6862
-