This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 7.3k
Not documented: stream.readable() is fired once when read is impossible #14597
Comments
socketpair
changed the title
Not documented: stream.readable() is fired when read is impossible
Not documented: stream.readable() is fired once when read is impossible
Apr 10, 2015
It's a bit confusing but it's not a bug. |
Please reopen. I understand that this is not a bug, but as I think, this non-trivial thing should be documented. For example, is it guaranteed that |
OK. Care to help out with a PR? :) |
jasnell
added a commit
to jasnell/node-joyent
that referenced
this issue
Jul 6, 2015
per nodejs#14597 Indicate that `'readable'` indicates only that data can be read from the stream, not that there is actually data to be consumed. `readable.read([size])` can still return null. Includes an example that illustrates the point.
I've got a PR open to clarify this. Will land shortly once reviewed. |
jasnell
added a commit
to jasnell/node-joyent
that referenced
this issue
Jul 6, 2015
per nodejs#14597 Indicate that `'readable'` indicates only that data can be read from the stream, not that there is actually data to be consumed. `readable.read([size])` can still return null. Includes an example that illustrates the point.
jasnell
added a commit
that referenced
this issue
Jul 10, 2015
per #14597 Indicate that `'readable'` indicates only that data can be read from the stream, not that there is actually data to be consumed. `readable.read([size])` can still return null. Includes an example that illustrates the point. Reviewed-By: James M Snell <[email protected]> PR-URL: #25635
jasnell
added a commit
to jasnell/node-joyent
that referenced
this issue
Jul 10, 2015
per nodejs#14597 Indicate that `'readable'` indicates only that data can be read from the stream, not that there is actually data to be consumed. `readable.read([size])` can still return null. Includes an example that illustrates the point. Reviewed-By: James M Snell <[email protected]> PR-URL: nodejs#25635
jasnell
added a commit
that referenced
this issue
Aug 4, 2015
per #14597 Indicate that `'readable'` indicates only that data can be read from the stream, not that there is actually data to be consumed. `readable.read([size])` can still return null. Includes an example that illustrates the point. Reviewed-By: James M Snell <[email protected]> PR-URL: #25591
jasnell
added a commit
to jasnell/node
that referenced
this issue
Aug 4, 2015
per nodejs/node-v0.x-archive#14597 Indicate that `'readable'` indicates only that data can be read from the stream, not that there is actually data to be consumed. `readable.read([size])` can still return null. Includes an example that illustrates the point. Reviewed-By: James M Snell <[email protected]> PR-URL: nodejs/node-v0.x-archive#25591
jBarz
pushed a commit
to ibmruntimes/node
that referenced
this issue
Nov 4, 2016
per nodejs#14597 Indicate that `'readable'` indicates only that data can be read from the stream, not that there is actually data to be consumed. `readable.read([size])` can still return null. Includes an example that illustrates the point. Reviewed-By: James M Snell <[email protected]> PR-URL: nodejs#25591
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Not documented: stream.readable() is fired once when read is impossible. I think, that just before 'end' event.
Current documentation says:
When a chunk of data can be read from the stream
. But in that case, chunk CAN_NOT be read (stream.read()
will returnnull
).The text was updated successfully, but these errors were encountered: