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

Tree: 993bb93e0a

isaacs 993bb93e0a streams: Don't emit 'end' until read() past EOF This prevents the following sort of thing from being confusing: ```javascript stream.on('data', function() { console.error('got data'); }); stream.pause(); // stop reading // turns out no data is available stream.push(null); // Hand the stream to someone else, who does stuff... setTimeout(function() { // too late! 'end' is already emitted! stream.on('end', function() { console.error('got end'); }); }); ``` With this change, the `end` event is not emitted until you call `read()` past the EOF null. So, a paused stream will not swallow the `end` event and emit it before you `resume()` the stream.		12 years ago
..
addons	test: modify async native test.js to test for #4820	12 years ago
disabled	Merge remote-tracking branch 'ry/v0.8' into master	12 years ago
fixtures	src: break on uncaught exception	12 years ago
gc	test: fix up weakref.cc after v8 api change	12 years ago
internet	DNS: Support NAPTR queries	12 years ago
message	process: remove maxTickDepth from _tickCallback	12 years ago
pummel	Merge branch 'v0.10'	12 years ago
simple	streams: Don't emit 'end' until read() past EOF	12 years ago
common.js	test: optionally set common.PORT via env variable	12 years ago