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

Commit Graph

Author	SHA1	Message	Date
Sam Roberts	155df9ca76	doc: document node signal handling Partly lifted from uv.h, partly from observation of node.cc.	11 years ago
Timothy J Fontaine	9f7f9d1240	blog: Post for v0.11.8	11 years ago
Ben Noordhuis	0c5981b226	doc: dgram: reword dgram.Socket#send() docs Make it clear that the address argument is not really optional and fix some Engrish and long lines while we're here. Fixes #6433.	11 years ago
isaacs	4b5e6a38df	npm@1.3.13	11 years ago
Phillip Alexander	977c54adb5	doc: fs: clarify fs.symlink Windows specific args	11 years ago
Ryan Graham	5ac6f4de13	doc: improve module documentation Expands on when to use module.exports vs. exports. This is a recurring question on mailing list and continues to confuse new devs.	11 years ago
Sam Roberts	a60f67192f	doc: fix missing backtick in `2e16037`	11 years ago
Brian White	21265e20d3	doc: streams: document default objectMode setting	11 years ago
Maxim Bogushevich	9c6e06bed3	debugger: Fix bug in sb() with unnamed script setBreakpoint() cause error when unnamed script is loaded	11 years ago
isaacs	f6f176e108	npm@1.3.12	11 years ago
Ben Noordhuis	808a968409	build: fix test-gc weakref build rule 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	11 years ago
Zarko Stankovic	eb291de00e	doc: add nodejs.rs to the community page	11 years ago
Ben Noordhuis	91a0e52c03	src: IsInt64() should return bool, not int	11 years ago
isaacs	97813ae58d	blog: HTTP server DoS vulnerability details CVE-2013-4450	11 years ago
Timothy J Fontaine	028e524bce	blog: Post for v0.10.21	11 years ago
Timothy J Fontaine	2649ae8395	blog: Post for v0.8.26	11 years ago
Timothy J Fontaine	85b2aaea3d	Now working on 0.10.22	11 years ago
Timothy J Fontaine	7940833773	Merge branch 'v0.10.21-release' into v0.10	11 years ago
Timothy J Fontaine	e2da042844	2013.10.18, Version 0.10.21 (Stable) * 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)	11 years ago
Timothy J Fontaine	5e41c022af	crypto: clear errors from verify failure 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	11 years ago
Timothy J Fontaine	8fc48bcf4c	uv: Upgrade to v0.10.18	11 years ago
isaacs	b97c28f59e	http: provide backpressure for pipeline flood 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`	11 years ago
Timothy J Fontaine	f051b8919f	http_parser: expose pause/resume method for parser	11 years ago
Sam Roberts	2e16037201	doc: cluster documentation cleanup and corrections - 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.	12 years ago
Sam Roberts	ed186c971c	doc: child_process corrections and cleanups - 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	12 years ago
Ben Noordhuis	5bc5210b92	doc: http: reword IncomingMessage 'close' event The bit that says "before response.end() was called or able to flush" doesn't apply to incoming streams. Fixes #6359.	11 years ago
Ben Noordhuis	5ef03bc3ee	doc: http: add cross-links for easier clicking Make it a little easier to navigate the http module documentation by turning class names and methods into links to the appropriate section.	11 years ago
Ben Noordhuis	9a3a0ccc50	doc: expand os.loadavg() section 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`.	11 years ago
Ben Noordhuis	56c5806da3	doc: document os.loadavg() behavior on windows The load average is a very UNIX-y concept. That's why os.loadavg() always returns zeros on Windows. Mention that in the documentation.	11 years ago
Dave Pacheco	720675e7db	test: use proper findjsobjects output format Closes #6329	11 years ago
Ben Noordhuis	ff1efdd6ee	doc: net: remove bad net.Server description net.Server is not an instance of net.Socket so don't say it is.	11 years ago
Ben Noordhuis	51cdce8322	doc: addon: fix object instantiation examples * 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.	11 years ago
isaacs	9c65387673	blog: Remove wp-to-markdown script	11 years ago
Ben Noordhuis	9777890f5d	tls: fix premature connection termination 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.	11 years ago
Dave Pacheco	98c57c7c07	dtrace: backport two byte string fix This is a partial backport of `5921158` Re #6309 Closes #6319	11 years ago
Ben Noordhuis	b011811a9f	fs: fix fs.truncate() file content zeroing bug 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.	11 years ago
Ben Noordhuis	d97ea06d88	doc: add warning to fs.exists() documentation Warn against the open-if-exists anti-pattern, it's susceptible to race conditions.	11 years ago
Ben Noordhuis	b7f36e187d	doc: link to pre-built binaries, add install note lLnk to http://nodejs.org/download/ and add a short primer on how to extract the tarballs. Fixes #6292.	11 years ago
Timothy J Fontaine	a63079f34c	blog: Post for v0.10.20	11 years ago
Timothy J Fontaine	d537992d57	Now working on 0.10.21	11 years ago
Timothy J Fontaine	451497c81e	Merge branch 'v0.10.20-release' into v0.10	11 years ago
Timothy J Fontaine	d7234c8d50	2013.09.30, Version 0.10.20 (Stable) * tls: fix sporadic hang and partial reads (Fedor Indutny) - fixes "npm ERR! cb() never called!"	11 years ago
Ben Noordhuis	994ce4c99f	src: turn uv_pipe_open() failures into exceptions uv_pipe_open() is unlikely to fail but when it does, the failure should not be quietly ignored. Raise the error as an exception. See joyent/libuv#941.	11 years ago
Fedor Indutny	671b5be6e9	tls: fix sporadic hang and partial reads Do not decrement size in read loop, its used later, when comparing to `bytesRead`. fix #6270 NOTE: Original patch contributed by @roadrunner2	11 years ago
Timothy J Fontaine	cfa03ad2e3	blog: add missing shasums for v0.10.19 release	11 years ago
Timothy J Fontaine	9135c7fea8	blog: Post for v0.10.19	11 years ago
Timothy J Fontaine	093efafce3	Now working on 0.10.20	11 years ago
Timothy J Fontaine	cb150406c8	Merge branch 'v0.10.19-release' into v0.10	11 years ago
Timothy J Fontaine	6b5e6a5a3e	2013.09.24, Version 0.10.19 (Stable) * uv: Upgrade to v0.10.17 * npm: upgrade to 1.3.11 * readline: handle input starting with control chars (Eric Schrock) * configure: add mips-float-abi (soft, hard) option (Andrei Sedoi) * stream: objectMode transforms allow falsey values (isaacs) * tls: prevent duplicate values returned from read (Nathan Rajlich) * tls: NPN protocols are now local to connections (Fedor Indutny)	11 years ago
Timothy J Fontaine	55546f55d4	uv: Upgrade to v0.10.17	11 years ago

... 2 3 4 5 6 ...

8757 Commits (ae418f974d78e52c22b8d49a84963b8b416b1438) All Branches Search

8757 Commits (ae418f974d78e52c22b8d49a84963b8b416b1438)

All Branches