whatwg/streams Issues

Last updated May 18, 2024, 6:00:22 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

17 out-of-SLO untriaged issues

Untriaged

Try to triage issues within 7 days. [ More Info ]

Issue	Title	Within SLO	On maintainers' plates for	Time past SLO
#384	TransformStream should allow transform algorithm to function as pull source	❌	8.8 years	8.8 years
#659	Tests for optimised implementations of piping	❌	7.3 years	7.3 years
#742	Make sure ReadableByteStream's respond() works for all with/without (BYOB)Reader	❌	7.1 years	7 years
#825	Use [[UpperCamelCase]] in internal slots	❌	6.6 years	6.6 years
#905	pipeTo says "in parallel", but that isn't really right	❌	6.2 years	6.2 years
#942	Participation agreement requirement non-obvious	❌	5.8 years	5.8 years
#1001	DetachArrayBuffer can throw	❌	5 years	5 years
#1016	Provide a way to communicate the current optimal write size	❌	4.7 years	4.7 years
#1031	WebSocket example bug & questions	❌	4.2 years	4.1 years
#1086	Using streams from other specs: explain some best practices for byte streams	❌	3.5 years	3.5 years
#1156	Allow web authors to tee() with cloned chunks	❌	2.8 years	2.8 years
#1222	How to create a transformed WritableStream that waits for close?	❌	2.2 years	2.2 years
#1233	Clarify: tee is unsafe for independent consumption since it backpressures to the faster consumer	❌	2 years	1.9 years
#1254	Add maxByteLength option to "read all bytes" algo	❌	1.3 years	1.3 years
#1260	Why resolve backpressurePromise by an error message in SetUpCrossRealmTransformWritable?	❌	1.2 years	1.2 years
#1290	Consider making writer.abort() automatically generate an "AbortError" DOMException?	❌	10.2 months	9.9 months
#1299	read all bytes: Why only Uint8Array instead of general BufferSource?	❌	6.1 months	5.9 months