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

Author	SHA1	Message	Date
Chris Dickinson	a96d6603b3	stream2: flush extant data on read of ended stream A ReadableStream with a base64 StringDecoder backed by only one or two bytes would fail to output its partial data before ending. This fix adds a check to see if the `read` was triggered by an internal `flow`, and if so, empties any remaining data. fixes #7914. Signed-off-by: Fedor Indutny <fedor@indutny.com>	11 years ago
Fedor Indutny	4128d4d2ba	Revert "stream: start old-mode read in a next tick" This reverts commit `2efe4ab761`.	11 years ago
Fedor Indutny	2efe4ab761	stream: start old-mode read in a next tick Calling `.read()` in the same tick with `.on('data', ...)` may cause users missing `error` events, because no `error` listeners were set yet. fix #7618	11 years ago
isaacs	0f8de5e1f9	stream: Simplify flowing, passive data listening Closes #5860 In streams2, there is an "old mode" for compatibility. Once switched into this mode, there is no going back. With this change, there is a "flowing mode" and a "paused mode". If you add a data listener, then this will start the flow of data. However, hitting the `pause()` method will switch back into a non-flowing mode, where the `read()` method will pull data out. Every time `read()` returns a data chunk, it also emits a `data` event. In this way, a passive data listener can be added, and the stream passed off to some other reader, for use with progress bars and the like. There is no API change beyond this added flexibility.	12 years ago
isaacs	88644eaa2d	stream: There is no _read cb, there is only push This makes it so that `stream.push(chunk)` is the only way to signal the end of reading, removing the confusing disparity between the callback-style _read method, and the fact that most real-world streams do not have a 1:1 corollation between the "please give me data" event, and the actual arrival of a chunk of data. It is still possible, of course, to implement a `CallbackReadable` on top of this. Simply provide a method like this as the callback: function readCallback(er, chunk) { if (er) stream.emit('error', er); else stream.push(chunk); } However, only fs streams actually would behave in this way, so it makes not a lot of sense to make TCP, TLS, HTTP, and all the rest have to bend into this uncomfortable paradigm.	12 years ago
Fedor Indutny	45941811dc	streams: set listener first, emit 'data' later When switching into compatibility mode by setting `data` event listener, `_read()` method will be called immediately. If method implementation invokes callback in the same tick - all emitted `data` events will be discarded, because `data` listener wasn't set yet.	12 years ago
isaacs	6c80ef01c1	node: emit 'exit' when exiting with error Fix #3555	12 years ago
isaacs	1c2910d94c	test-message: Add setTimeout and nextTick message tests	12 years ago
Ryan Dahl	850609ea2d	Remove separation of libuv tests	13 years ago
Ryan Dahl	4e1d6fca8e	Mark tests which are broken in libuv	14 years ago
Ryan Dahl	55048cdf79	Update copyright headers	14 years ago
Ryan Dahl	92789b16e5	Fix global leaks	14 years ago
Oleg Efimov	c0d69a4883	GJSLint part of tests	14 years ago
Ryan Dahl	9fd5e3c89c	Update tests to work with module contexts	15 years ago
Ryan Dahl	ba792ea202	:%s/sys.puts/console.log/g and there was much rejoicing	15 years ago
Ryan Dahl	7d0252eae2	Fix message tests	15 years ago
Ryan Dahl	125b868e06	Add message tests	15 years ago