lukechilds/node - node - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
Fedor Indutny	25f9e92813	gyp: fix non-ninja build	11 years ago
isaacs	f645c40fcd	npm: Upgrade to v1.3.24	11 years ago
Timothy J Fontaine	1d57a5caa4	blog: nodejs v0.12 roadmap update	11 years ago
Fedor Indutny	61c0d571bf	gyp: fix `ninja` build on linux fix #6679	11 years ago
Sam Roberts	abe02553f2	doc: clarify Windows signal sending emulation	11 years ago
Sam Roberts	67e9298fb6	child_process: fix spawn() optional arguments Spawn's arguments were documented to be optional, as they are for the other similar child_process APIs, but the code was missing. Result was `child_process.spawn('node', {})` errored when calling slice() on an Object, now it behaves as the documentation said it would.	11 years ago
Sam Roberts	198ed0bd0d	doc: describe child_process.fork() silent option	11 years ago
Sam Roberts	549be1caa8	doc: child_process.execFile arguments are optional	11 years ago
Ryan Graham	7f81ca2c47	domains: exit() only affects active domains domain.create().exit() should not clear the domain stack if the domain instance does not exist within the stack. Signed-off-by: Trevor Norris <trev.norris@gmail.com>	11 years ago
isaacs	e7f7e2aeca	blog: TJ is the new node core project lead	11 years ago
Fedor Indutny	a05dae2ced	gyp: fix build with python 2.6 fix #6859	11 years ago
Fedor Indutny	346b59e4a3	deps: update gyp to 1eae492b	11 years ago
Sam Roberts	7bd6e33318	doc: streams must be open to be passed to child spawn stdio options can be a 'stream', but the following code fails with "Incorrect value for stdio stream: [object Object]", despite being a stream. The problem is the test isn't really for a stream, its for an object with a numeric `.fd` property, and streams do not have an fd until their async 'open' event has occurred. This is reasonable, but was not documented. child_process.spawn('date', [], {stdio: [ 'ignore', fs.createWriteStream('out.txt',{flags:'a'}), 'ignore']})	11 years ago
Alexis Campailla	1b74892807	test: close debug client in test-debugger-client Killing the debuggee without first closing the socket can result in an ECONNRESET error.	11 years ago
Timothy J Fontaine	8753bb3859	src: return empty set on ENOSYS for interfaces If node was compiled with --no-ifaddrs to support older operating systems, don't throw instead simply return an empty object Fixes #6846	11 years ago
svenpanne@chromium.org	196184d332	v8: backport codereview.chromium.org/11362182 Keep the number of descriptors below DescriptorArray::kMaxNumberOfDescriptors even for accessors Review URL: https://codereview.chromium.org/11362182	12 years ago
gluxon	56913d2cde	doc: Fix argument typo in SimpleProtocol example	11 years ago
Timothy J Fontaine	270c2deb84	src: OnFatalError handler must abort() We are in an unrecoverable state if v8 throws a FatalError, actually ask the operating system to dump core in this case. Fixes #6836	11 years ago
Lorenz Leutgeb	fc7e217a30	doc: fix typo in cluster page	11 years ago
Timothy J Fontaine	30b3bc2f7c	uv: Upgrade to v0.10.22	11 years ago
isaacs	1be9365930	npm: Upgrade to 1.3.23	11 years ago
ayanamist	b922b5e90d	stream: writes may return false but forget to emit drain If a write is above the highWaterMark, _write still manages to fully send it synchronously, _writableState.length will be adjusted down to 0 synchronously with the write returning false, but 'drain' will not be emitted until process.nextTick. If another small write which is below highWaterMark is issued before process.nextTick happens, _writableState.needDrain will be reset to false, and the drain event will never be fired. So we should check needDrain before setting it up, which prevents it from inproperly resetting to false.	11 years ago
Timothy J Fontaine	aa56d9d354	blog: Post for v0.11.10	11 years ago
Maciej Małecki	5a8de857f0	doc: document that `process.send` is synchronous Ref #2598	11 years ago
Timothy J Fontaine	ffb718b5a3	doc: clarify process on exit safe usage	11 years ago
Ron Korving	3917232030	docs: process.on('exit') receives exit code The fact that the "exit" event passes the exit code as an argument as omitted from the documentation. This adds the explanation and augments the example code to show that.	11 years ago
Timothy J Fontaine	6f8aa24d1e	test: fix test-cluster-eaccess to work on windows	11 years ago
Fedor Indutny	3e9f2e61db	cluster: report more errors to workers Some errors for listening and binding to a socket were not properly delivered to workers. fix #6767	11 years ago
Fedor Indutny	cb5da7b443	deps: update gyp to 828ce09	11 years ago
Dav Glass	34b9280da4	doc: Fix missing backtick in debugger doc	12 years ago
Lev Gimelfarb	d2d56d04f8	build: add settings for VS 2013 to vcbuild.bat Search for VS2013 compiler 1st, before falling back to older ones. This allows compiling using the latest VS2013.	11 years ago
isaacs	7f82faee30	npm: Upgrade to v1.3.22	11 years ago
T.C. Hollingsworth	55b0bd639d	build: install common.gypi along with headers node-gyp requires this file	11 years ago
Timothy J Fontaine	f84c7a2776	blog: Post for v0.10.24	11 years ago
Timothy J Fontaine	00e28ee6a8	Now working on 0.10.25	11 years ago
Timothy J Fontaine	696ae46fd7	Merge branch 'v0.10.24-release' into v0.10	11 years ago
Timothy J Fontaine	b7fd6bc899	2013.12.18, Version 0.10.24 (Stable) * uv: Upgrade to v0.10.21 * npm: upgrade to 1.3.21 * v8: backport fix for CVE-2013-{6639\|6640} * build: unix install node and dep library headers (Timothy J Fontaine) * cluster, v8: fix --logfile=%p.log (Ben Noordhuis) * module: only cache package main (Wyatt Preul)	11 years ago
Timothy J Fontaine	9371be0aa1	uv: Upgrade to v0.10.21	11 years ago
Ben Noordhuis	2eaef9f6da	cluster, v8: fix --logfile=%p.log The %p is replaced with the current PID. This used to work in node.js v0.9.7 but it seems to have been lost somewhere along the way. This commit makes the fix from `6b713b52` ("cluster: make --prof work for workers") work again. Without it, all log data ends up in a single file and is unusable because the addresses are all wrong.	11 years ago
Timothy J Fontaine	32478acf94	build: unix install node and dep library headers Restores functionality from v0.8 where module authors may not be relying on gyp for building their modules.	11 years ago
isaacs	2a741f2d12	npm: upgrade to 1.3.21	11 years ago
isaacs	e10c223eb6	npm: upgrade to 1.3.20 The 1.3.19 release had a critical bug: any packages published with it could not be installed, because the shasum would be incorrect. Thankfully, 1.3.19 was published using 1.3.19, so could not be installed by any users! However, if it goes out as part of a Node.js release, then obviously that would be a problem.	11 years ago
isaacs	97738994e0	npm: Upgrade to 1.3.19	11 years ago
jkummerow@chromium.org	39e2426b20	v8: backport fix for CVE-2013-{6639\|6640} Quoting CVE-2013-6639: The DehoistArrayIndex function in hydrogen-dehoist.cc in Google V8 before 3.22.24.7, as used in Google Chrome before 31.0.1650.63, allows remote attackers to cause a denial of service (out-of-bounds write) or possibly have unspecified other impact via JavaScript code that sets the value of an array element with a crafted index. Quoting CVE-2013-6640: The DehoistArrayIndex function in hydrogen-dehoist.cc in Google V8 before 3.22.24.7, as used in Google Chrome before 31.0.1650.63, allows remote attackers to cause a denial of service (out-of-bounds read) via JavaScript code that sets a variable to the value of an array element with a crafted index. Like 6b92a7, this is unlikely to affect node.js because it only runs local, trusted code. However, if there exists some module somewhere that populates an array index with remotely provided data this could very well be used to crash a remote server running node. Defense in depth and all. This is a backport of upstream commit r17801. Original commit log: Limit size of dehoistable array indices LOG=Y BUG=chromium:319835,chromium:319860 R=dslomov@chromium.org Review URL: https://codereview.chromium.org/74113002	11 years ago
Wyatt Preul	1d5e797445	module: only cache package main	11 years ago
Timothy J Fontaine	7dca8d714f	blog: Post for v0.10.23	11 years ago
Timothy J Fontaine	bb1575b4c4	Now working on 0.10.24	11 years ago
Timothy J Fontaine	593672c33d	Merge branch 'v0.10.23-release' into v0.10	11 years ago
Timothy J Fontaine	0462bc2356	2013.12.12, Version 0.10.23 (Stable) * uv: Upgrade to v0.10.20 (Timothy J Fontaine) * npm: Upgrade to 1.3.17 (isaacs) * gyp: update to 78b26f7 (Timothy J Fontaine) * build: include postmortem symbols on linux (Timothy J Fontaine) * crypto: Make Decipher._flush() emit errors. (Kai Groner) * dgram: fix abort when getting `fd` of closed dgram (Fedor Indutny) * events: do not accept NaN in setMaxListeners (Fedor Indutny) * events: avoid calling `once` functions twice (Tim Wood) * events: fix TypeError in removeAllListeners (Jeremy Martin) * fs: report correct path when EEXIST (Fedor Indutny) * process: enforce allowed signals for kill (Sam Roberts) * tls: emit 'end' on .receivedShutdown (Fedor Indutny) * tls: fix potential data corruption (Fedor Indutny) * tls: handle `ssl.start()` errors appropriately (Fedor Indutny) * tls: reset NPN callbacks after SNI (Fedor Indutny)	11 years ago
Nicolas Kaiser	4bc2ec90d7	doc: fix typos in node.1	11 years ago

1 2 3 4 5 ...

8708 Commits (25f9e92813eda927c3d3eaa56dab3a397afadebe) All Branches Search

8708 Commits (25f9e92813eda927c3d3eaa56dab3a397afadebe)

All Branches