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
Readable confusion/inconsistency between mutating flowing and using pause/resume, e.g. pipe uses pause but pipeOnDrain uses flowing=true.
ReadablemaybeReadMore does not take explicit pausing into consideration and can read data despite being paused, e.g. if pause() is called before _construct(callback) has completed, it will start reading despite being paused. stream: don't read when paused #34106
The text was updated successfully, but these errors were encountered:
ronag
added
meta
Issues and PRs related to the general management of the project.
stream
Issues and PRs related to the stream subsystem.
labels
Jun 28, 2020
This is a meta issue of somewhat complex issues to look into:
writable.end(chunk, callback)
does not properly propagatewrite(chunk, callback)
errors. stream: end(callback) does not propagate write after end to callback #33684writable.end(chunk)
API is ambiguous in relation to optional parameters (i.e. chunk).writable.end(chunk, callback)
register error handler, but will still result in unhandled exception (stream: fix writable.end callback behavior #34101)setEncoding
should apply transform when reading fromReadable
not when pushing into it. stream: socket.setEncoding(null) to receive binary Buffers rather than strings has no effect #6038Readable
confusion/inconsistency between mutatingflowing
and usingpause
/resume
, e.g.pipe
usespause
butpipeOnDrain
usesflowing=true
.Readable
maybeReadMore
does not take explicit pausing into consideration and can read data despite being paused, e.g. ifpause()
is called before_construct(callback)
has completed, it will start reading despite being paused. stream: don't read when paused #34106Readable.wrap
is not streams compliant. (stream: cleanup and fix Readable.wrap #34204)Readable.wrap
does not auto destroy wrapped stream.emit('error', undefined)
?finished(stream)
is called on an errored stream?pipeline(stream)
is called on an errored stream?finished
registers excessive amount of listeners.'data'
,'drain'
,pause()
,resume()
API in order to avoid possible complexity/bugs frompipe
?DuplexSocket
needed? Is it broken?js_socket_stream
is not streams compliant.'error'
instead of usingdestroy(err)
TLSSocket
is not streams compliant.'error'
instead of usingdestroy(err)
'end'
semantics fornet.Socket
. Probably also related tojs_socket_stream
. 'end' event not called on connected socket wrapped with tls #10871The text was updated successfully, but these errors were encountered: