00:57
<Justin Ridgewell>
Chengzhong Wu: Are we skipping Slide 8 (async functions and promise rejections)?
00:58
<Chengzhong Wu>
I think that we can come back to this slide when the time allows
01:16
<littledan>
yeah I agree with skipping slide 8
01:30
<littledan>
Sorry about this; we should get our story straight among ourselves before the next presentation
01:32
<Andreu Botella>
The slide mentioned specifically that web APIs need run in the context of task attribution
01:32
<Andreu Botella>
maybe I should've made it clearer that it was Variable.p.run
01:32
<Andreu Botella>
I guess out of context that's not clear
01:32
<littledan>
fundamentally, Justin probably should've been aware of what was being presented, and I should've given feedback about not emphasizing the concerns raised on the last couple slides (since they were just not relevant or representative)
01:33
<littledan>
it'd be OK if the audience is confused but we shouldn't get confused among ourselves
01:33
<Justin Ridgewell>
That slide was added after our last meeting, so I wasn't aware until now. Sorry
01:33
<littledan>
I mean, obviously the audience shouldn't be confused either
01:33
<littledan>
yes, the last couple slides were added since I last saw it, sorry
01:34
<Andreu Botella>
I added them sometime last week, maybe Thursday, although I was modifying them earlier today / yesterday
01:35
<littledan>
yeah if you could just ping the channel to ask for reviews, then it'd be helpful
01:36
<littledan>
the slides weren't incorrect, we just have to think about how to explain things best
01:46
<Andreu Botella>
can we make sure AsyncContext becomes stage 3 before V8 decides to get rid of CPED
01:57
<James M Snell>
Umm... Gets rid of CPED...? Is that at risk?
01:58
<Andreu Botella>
V8 doesn't seem happy with it
01:58
<James M Snell>
Workers is absolutely relying on that API right now. That would break us
01:58
<shu>
James M Snell: i don't think removal of the expressivity is at risk, but the current implementation leaves something to be desired so the implementation might change
01:59
<James M Snell>
Impl changing is fine. We can adjust to impl changing. But we absolutely depend on that API
02:00
<James M Snell>
We can fallback to promise hooks if we absolutely need to buy obviously would rather not
02:00
<shu>
noted
02:00
<littledan>
Shu seems to be expressing that a conclusion hasn't been reached yet, rather than being uniformly unhappy. I think the best thing we could do is move forward with our design doc for review by the V8 team.
02:00
<James M Snell>
Let me know if I can help
02:01
<James M Snell>
We use CPED in our ALS impl but also under the covers for propagating trace spans across async boundaries.
02:01
<James M Snell>
We have a c++ level API wrapped around it that we use for both purposes
02:02
<Andreu Botella>
See also this review on an CL for CPED to support thenables: https://chromium-review.googlesource.com/c/v8/v8/+/4674242/comments/8fa12f12_eef7ac70
02:03
<Andreu Botella>
though IMO Blink is not gonna be happy with CPED being removed without an alternative
02:05
<James M Snell>
Fwiw, even once AsyncContext is done, we'll need a c++level API for accessing it as we have areas where we have to manually propagate context over other async boundaries (like our timers impl). We don't care what the actual API is as long as it's available and we have time to move over to it. E. G. Please don't drop CPED without having the replacement in place first
02:05
<littledan>
yes, this is part of the draft design doc. We just need to finish that doc.
02:05
<littledan>
and the draft implementation has this already
02:06
<Andreu Botella>
when prototyping the Blink integration I noticed the C++ API we initially drafted isn't great, but that's something that we can iterate on
02:07
<Chengzhong Wu>
Certainly, C++ native APIs of async context would definitely be a requirement for hosts
02:07
<littledan>
btw Luca from Sentry expressed interest in joining this effort. I'll just invite him to this room?
02:07
<Chengzhong Wu>
btw Luca from Sentry expressed interest in joining this effort. I'll just invite him to this room?
Definitely, please
02:07
<James M Snell>
Happy to review the API we implemented over the top. It has warts but it works well for us
02:07
<littledan>
"once the top"?
02:08
<James M Snell>
Typo
02:08
<littledan>
thanks for correcting
02:21
<littledan>
Let's write a good summary/conclusion for the TC39 topic