You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similarly to #44, the following test currently fails:
tape('push after push(null) should cause an error',function(t){t.plan(5)consts=newReadable()s.on('data',function(data){t.equals(data,'a')})s.on('error',function(){t.pass('stream.push() after EOF')})s.on('close',function(){t.end()})t.equals(s.push('a'),true)t.equals(s.push(null),false)t.equals(s.push('b'),false)})
Both pushed data statements are passed through and no error like stream.push() after EOF as this is an incompatibility to the current Node.js streams and am wondering: is that intentional? should that be documented?
The text was updated successfully, but these errors were encountered:
Similarly to #44, the following test currently fails:
Both pushed data statements are passed through and no error like
stream.push() after EOF
as this is an incompatibility to the current Node.js streams and am wondering: is that intentional? should that be documented?The text was updated successfully, but these errors were encountered: