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

Tree: c93c99c7c3

isaacs 14e8f806de stream: Properly handle large reads from push-streams Problem 1: If stream.push() triggers a 'readable' event, and the user calls `read(n)` with some n > the highWaterMark, then the push() will return false (indicating that they should not push any more), but no future 'readable' event is coming (because we're above the highWaterMark). Solution: return true from push() when needReadable is set. Problem 2: A read(n) for n != 0, after the stream had encountered an EOF, would not trigger the 'end' event if the EOF was pushed in synchronously by the _read() function. Solution: Check for ended in stream.read() and schedule an end event if the length now equals 0. Fix #4585		12 years ago
..
addons	test: update addons .gitignore	13 years ago
disabled	test: disable simple/test-debug-brk-file	12 years ago
fixtures	test: 2 resume() calls needed to flush streams	12 years ago
gc	test: use the debug build of node-weak when necessary	13 years ago
internet	test: pick another CNAME record to test dns queries	13 years ago
message	test: make tests work with newer v8	12 years ago
pummel	test-pummel: Add call validation in net-write-callbacks	12 years ago
simple	stream: Properly handle large reads from push-streams	12 years ago
common.js	test: child process { stdio:'inherit' }	12 years ago