-
Notifications
You must be signed in to change notification settings - Fork 78
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
Node.js Diagnostics WorkGroup Meeting 2020-06-03 #393
Comments
proposed one session at collab summit here: openjs-foundation/summit#293 |
TC39 meeting time collides with the Diag meeting this week, so I won't be able to chair. |
Async context for JavaScript proposal is on the agenda of the TC39 meeting. So I'll not be able to make the WG meeting this time as well. |
Should we cancel? Seems like many of the topics would require people that will not be attending due to the overlapping TC39 meeting. |
@mmarchini @legendecas and @mhdawson are not going to make it, so that is good share of participants in recent times. let us cancel this instance! |
this meeting stands cancelled, but keeping it open, just in case if anyone wants to offline-update any of the agenda items. |
Not too much to update in regards to async_hooks other than that I fixed thenables support in the V8 PromiseHook API. Just waiting on it to land now. https://crrev.com/c/2215624 |
I don't have access to create Zoom meetings yet. Can someone create it today for the deep dive meeting? |
just started today, but realized it was only 2 of us (@legendecas and me), so we cancelled it after 10 mins of wait! |
Time
UTC Wed 03-Jun-2020 16:30 (04:30 PM):
Or in your local time:
Links
Agenda
Extracted from diag-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/diagnostics
Invited
Observers/Guests
Notes
The agenda comes from issues labelled with
diag-agenda
across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.Joining the meeting
The text was updated successfully, but these errors were encountered: