| 00:05 | <smaug> | shu: any ideas how long you'd expect microwait need to wait to be useful? |
| 00:07 | <smaug> | Also, this feels a bit like something where if used in benchmarks, UA might want to keep the cpu as busy as possible while waiting, leading effectively to the current loop. I wonder how to avoid that |
| 01:18 | <Domenic> | Ugh, the definition panels are indeed quite a mess. The fact that they vary per Bikeshed deploy is frustrating too. |
| 01:19 | <Domenic> | I guess if we wanted to get control of them back we'd need to take back the maintenance burden though. Since Bikeshed kept updating its markup for the definition panels, and our scripts/styles weren't keeping up, we lost the ability to control how they look and behave. |
| 07:26 | <annevk> | We can manually deploy now. We might be able to call that via some API so we're at least consistently bad. 🙃 |
| 15:46 | <TabAtkins> | The API server breaking its release hooks is frustrating, it needs fixing. |
| 15:47 | <TabAtkins> | Domenic: Check the latest Bikeshed version, see if anything still feels wrong. If so, happy to discuss fixes. |
| 16:15 | <annevk> | Is anyone investigating PR Preview breaking all over? Or is that limited to WHATWG repositories? |
| 16:16 | <annevk> | Maybe some of the metadata changes caused it to no longer work? |
| 16:30 | <Dominic Farolino> | I'm not seeing breakages on non-WHATWG repos for what it's worth. Occasionally maybe, but not too frequently. |
| 16:44 | <annevk> | Domenic: I vaguely suspect this is related to the "die on" change |
| 17:37 | <shu> | shu: any ideas how long you'd expect microwait need to wait to be useful? |
| 17:38 | <shu> | emscripten folks were interested in instrumenting Photoshop to see what distribution of main thread busyloop wait times they could come up with but as these things go, instrumentation isn't turning out to be so easy |
| 17:52 | <annevk> | What is microwait? |
| 17:53 | <nicolo-ribaudo> | https://github.com/syg/proposal-atomics-microwait |
| 21:43 | <Dominic Farolino> | This might be a dumb question but where do we ever set a node's parent to null, once we https://dom.spec.whatwg.org/#concept-node-remove it? Does this happen implicitly somewhere? |
| 22:04 | <Dominic Farolino> | The only thing I can think of is that "An object A whose parent is object B is a child of B" tries to imply this, but I really don't think it does. Otherwise, I don't see how/when parent becomes null. |