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

Commit Graph

Author	SHA1	Message	Date
iamdoron	1317032c97	fs: make unwatchFile() insensitive to path	11 years ago
Benjamin Waters	d2147c55c2	doc: fix references to error keyword References for err.signal and err.code should be error.signal and error.code. Fixes joyent/node#6862	11 years ago
Ben Noordhuis	09c51d5e40	crypto: update root certificates 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.	11 years ago
Maxime Quandalle	154d9d2163	doc: add an example about multiple extensions `path.extname` returns only the last extension	11 years ago
Fedor Indutny	643a7d8c16	dtrace: fix arguments warning Add enough arguments to `NODE_NET_SOCKET_READ()` and `NODE_NET_SOCKET_WRITE()` stubs.	11 years ago
Fedor Indutny	fac8f396cc	deps: backport 883637bd from latest v8 Original commit message: VS2013 contains a number of improvements, most notably the addition of all C99 math functions. I'm a little bit concerned about the change I had to make in cpu-profiler.cc, but I spent quite a bit of time looking at it and was unable to figure out any rational explanation for the warning. It's possible it's spurious. Since it seems like a useful warning in general though, I chose not to disable globally at the gyp level. I do think someone with expertise here should probably try to determine if this is a legitimate warning. BUG=288948 R=dslomov@chromium.org Review URL: https://codereview.chromium.org/23449035 NOTE: Path applied without `cpu-profiler.cc` changes because in our version it was looking totally different.	11 years ago
Fedor Indutny	e796e11087	node: do not ever close stdio Even if stdio streams are opened as file streams, we should not ever try to close them. This could be accomplished by passing `autoClose: false` in options on their creation.	11 years ago
Timothy J Fontaine	a98d541733	blog: Post for v0.11.11	11 years ago
Wyatt Preul	8c05570258	docs: clarify origin in agent.maxSockets section	12 years ago
Jun Ma	d2de8ba34d	net: make Socket destroy() re-entrance safe So that we are free to call socket.destroy() in error event handler. fix #6769	11 years ago
Fedor Indutny	b4c4e0bbaa	crypto: throw on SignFinal failure fix #6963	11 years ago
Fedor Indutny	00efcb4cd7	net: reset `endEmitted` on reconnect fix #6908	11 years ago
Fedor Indutny	896e19330a	deps: backport b5135bbc from c-ares repo Original commit message: ares_parse_txt_reply: return a ares_txt_reply node for each sub-string Previously, the function would wrongly return all substrings merged into one. fix #6931	11 years ago
Fedor Indutny	0ec3770767	doc: readline document TTY utils fix #6933	11 years ago
Scott González	9975ff603b	doc: fix typo in readline	11 years ago
isaacs	485fcf9c63	npm: Upgrade to v1.3.25	11 years ago
Alexis Campailla	42cd468901	test: fix http-incoming-pipelined-socket-destroy The test was calling server.close() after write on the socket had completed. However the fact that the write had completed was not valid indication that the server had received the data. This would result in a premutaure closing of the server and an ECONNRESET event on the client.	11 years ago
Alexis Campailla	5d4f4ee310	test: fix http-many-ended-pipelines server close The test was calling server.close() without waiting for the server to have received all the requests. This would cause an ECONNRESET.	11 years ago
Timothy J Fontaine	5aebc73525	blog: Post for v0.10.25	11 years ago
Timothy J Fontaine	eb7c7be7da	Now working on 0.10.26	11 years ago
Timothy J Fontaine	24d05f21be	Merge branch 'v0.10.25-release' into v0.10	11 years ago
Timothy J Fontaine	b0e5f195df	src: lint lib/net.js	11 years ago
Timothy J Fontaine	bc2f31ae1d	2014.01.23, Version 0.10.25 (Stable) * uv: Upgrade to v0.10.23 * npm: Upgrade to v1.3.24 * v8: Fix enumeration for objects with lots of properties * child_process: fix spawn() optional arguments (Sam Roberts) * cluster: report more errors to workers (Fedor Indutny) * domains: exit() only affects active domains (Ryan Graham) * src: OnFatalError handler must abort() (Timothy J Fontaine) * stream: writes may return false but forget to emit drain (Yang Tianyang)	11 years ago
Timothy J Fontaine	8b7ec73331	uv: Upgrade to v0.10.23	11 years ago
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

1 2 3 4 5 ...

8732 Commits (1317032c9738790362b8e1bdd3638f1368b00188) All Branches Search

8732 Commits (1317032c9738790362b8e1bdd3638f1368b00188)

All Branches