08:27
<Noam Rosenthal>
I don't think specs are expected to optimize for this non-observable behavior
08:28
<Noam Rosenthal>
(regarding the double-promise thing)
08:30
<Noam Rosenthal>
Sounds like you've violated this line: Public API must not be used: while reading or writing, or performing any of the operations below, the JavaScript-modifiable reader, writer, and stream APIs (i.e. methods on the appropriate prototypes) must not be used. Instead, the streams must be manipulated directly.
08:30
<Noam Rosenthal>
... which would explain this whole thread :)
08:31
<akaster>
It seems so! It took quite a bit of digging to find the "massive fixme but it's probably fine" comment
19:22
<akaster>
Sounds like you've violated this line: Public API must not be used: while reading or writing, or performing any of the operations below, the JavaScript-modifiable reader, writer, and stream APIs (i.e. methods on the appropriate prototypes) must not be used. Instead, the streams must be manipulated directly.
The real issue seems to be we didn't have a facility to set the internal response's body when appropriate on Response. So in the cases that we had a subclass of Response, we were setting a body that nobody used 😅. Some class refactoring is in order