Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2024-08-01 meeting #66

Open
lino-levan opened this issue Aug 1, 2024 · 1 comment
Open

2024-08-01 meeting #66

lino-levan opened this issue Aug 1, 2024 · 1 comment
Labels
meeting An issue announcing a meeting.

Comments

@lino-levan
Copy link

lino-levan commented Aug 1, 2024

Agenda

  • Review progress towards WinterTC
    • Put the proposal on a vote at ECMA. Google and Mozilla were concerned about IP.
    • The proposal is to have every contributor to the Common Minimum API sign a transfer of copyright to ECMA. This would have to include any comments in meetings that led to a change in the spec.
    • Daniel and Andreu have committed to getting signatures from contributors.
  • Discussed AsyncContext in the context of server runtime apis (e.g. node/cf workers/deno)
    • For web APIs, APIs that take callbacks will store the context at the time the API is called, and will restore it when calling the callback.
      • Events have the context when addEventListener is called, which is the one that will be restored when the listener is called. But they might have another context (the dispatch snapshot), which is the JS context that caused the event to fire (e.g. the call to an API that started an async fetch that eventually fires an event). This dispatch snapshot isn't always present, e.g. for signals, IPC or messages from workers, since the thing that causes the event isn't JS code living inside the agent / V8 isolate.
      • In the web API, this dispatch snapshot might only be exposed for a subset of events, since it's not realistic to update every event in the web. It will be exposed as a property in Event subclasses, containing an AsyncContext.Snapshot value.
      • Full web integration document available at Add web integration document tc39/proposal-async-context#100.
    • This clearly applies to WinterCG APIs, but we're hoping runtime-specific APIs would also use this.
    • Guy compared this to stack swtiching in WebAssembly (https://github.com/WebAssembly/stack-switching), suggesting that it might use similar mechanisms at the implementation level. Andreu was not previously aware of the parallels, and will look into it.
  • Briefly discussed the CLI proposal
    • Not enough core members present to come to any conclusions

Attendance

@andreubotella andreubotella added the meeting An issue announcing a meeting. label Aug 1, 2024
@jasnell
Copy link
Contributor

jasnell commented Aug 1, 2024

Doh!! I completely missed the fact that this was the first thursday of august! Glad y'all went ahead without me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meeting An issue announcing a meeting.
Projects
None yet
Development

No branches or pull requests

3 participants