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

2013-01-16 10:45:11 -08:00

..

addons

test: update addons .gitignore

2012-05-24 14:07:09 +02:00

disabled

test: disable simple/test-debug-brk-file

2013-01-07 03:40:12 +01:00

fixtures

test: 2 resume() calls needed to flush streams

2012-12-19 10:55:23 -08:00

gc

test: use the debug build of node-weak when necessary

2012-06-13 17:58:28 -07:00

internet

test: pick another CNAME record to test dns queries

2012-09-26 01:57:24 +02:00

message

test: make tests work with newer v8

2013-01-02 12:13:47 +04:00

pummel

test-pummel: Add call validation in net-write-callbacks

2012-12-19 10:55:23 -08:00

simple

stream: Properly handle large reads from push-streams

2013-01-16 10:45:11 -08:00

common.js

test: child process { stdio:'inherit' }

2013-01-11 09:14:09 -08:00