15:05
<wanderview>
anyone else having problems with the bikeshed server? I'm getting "<html><body><p><strong>WARNING: </strong>mysqli_connect(): (HY000/2002): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)</p></body></html>"
15:10
<annevk>
Domenic: implementations have non-JS streams
15:11
<annevk>
(re Fetch architecture)
15:12
<annevk>
wanderview: you can ping plinns on GitHub for help perhaps
15:15
<wanderview>
what repo is the bikeshed server associated with?
15:19
<annevk>
I don't know, if you don't have a PR or something I guess I'd file an issue against tabatkins/bikeshed
15:20
<Sam Sneddon [:gsnedders]>
wanderview: none, plinss hosts it (see also drafts.csswg.org being down)
15:21
<wanderview>
I guess if the outage is wider scope then maybe its already known about
15:27
<Domenic>
Domenic: implementations have non-JS streams
Sure but when do they create ReadableStream objects and enqueue from them, is the question. I think you could get away without a first-class non-JS stream primitive in the spec since you can just pretend the data hasn't reached you yet if it's queued up.
15:29
<annevk>
Domenic: I suspect it gets created the moment someone "touches" it
15:29
<Domenic>
Hmm I don't think that's true in Chrome
15:29
<annevk>
As in, once someone does res.body
15:30
<Domenic>
No, that returns an existing BodyStreamBuffer->Stream() it seems
15:31
<Domenic>
Trying to find out when those are created
15:31
<Domenic>
(the implementation actually seems to use the same JS-stream infrastructure for blob() and arrayBuffer() as the spec does, interestingly!)
15:32
<annevk>
The JS object is eagerly allocated? Interesting. I thought those were pretty much always lazily created, but maybe that's only in Gecko.
15:32
<Domenic>
The ReadableStream is created the same time the Response object is created
15:32
<Domenic>
Well the JS object is created lazily but the "IDL" (C++) object is created eagerly
15:32
<wanderview>
bikeshed seems to be fixed now
15:33
<annevk>
I see, but in theory the IDL object could be cross-thread...
15:33
<Domenic>
O_o I guess in theory, but not in implementations
15:34
<annevk>
Might be a bit confusing though