Files
scriptc/tests
Chris Tate ccb4cfa1ae The emittedReadable flag follows Node's emitReadable_/read() lifecycle
- emitReadable_ clears emittedReadable AFTER the 'readable' emit and only when it really fired — a listener observes true during the pass, exactly Node's readable.js.
- read() clears the flag for absent sizes too (Node's `if (n !== 0)` sees NaN there); only read(0) leaves it standing.
- Corpus 2558 pins the lifecycle byte-identically on both backends. The suite's needReadable/resumeScheduled probes remain blocked by the documented stream-tick station divergence (stream ticks drain at the next checkpoint instead of interleaving the user nextTick queue), not by flag semantics.
2026-07-23 22:34:03 -05:00
..
2026-07-22 18:08:04 -05:00