Skip to content

Node.js Diagnostics WorkGroup Meeting 2022-01-25 #523

New issue

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

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

Already on GitHub? # to your account

Closed
mhdawson opened this issue Jan 24, 2022 · 1 comment
Closed

Node.js Diagnostics WorkGroup Meeting 2022-01-25 #523

mhdawson opened this issue Jan 24, 2022 · 1 comment
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Tue 25-Jan-2022 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Tue 25-Jan-2022 08:00 (08:00 AM)
US / Mountain Tue 25-Jan-2022 09:00 (09:00 AM)
US / Central Tue 25-Jan-2022 10:00 (10:00 AM)
US / Eastern Tue 25-Jan-2022 11:00 (11:00 AM)
EU / Western Tue 25-Jan-2022 16:00 (04:00 PM)
EU / Central Tue 25-Jan-2022 17:00 (05:00 PM)
EU / Eastern Tue 25-Jan-2022 18:00 (06:00 PM)
Moscow Tue 25-Jan-2022 19:00 (07:00 PM)
Chennai Tue 25-Jan-2022 21:30 (09:30 PM)
Hangzhou Wed 26-Jan-2022 00:00 (12:00 AM)
Tokyo Wed 26-Jan-2022 01:00 (01:00 AM)
Sydney Wed 26-Jan-2022 03:00 (03:00 AM)

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

  • Add using clinic/heap-profiler step #521
  • Document async_hooks types purposes #511
  • meeting time, again #507
  • User Journey tracking documentation #502
  • Identify async_hooks use cases beyond AsyncLocalStorage #437

Invited

  • Diagnostics team: @nodejs/diagnostics

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

@mhdawson mhdawson self-assigned this Jan 24, 2022
@RafaelGSS
Copy link
Member

I'll join 10 min late (currently in a meeting). Sorry about that.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants