Node.js Foundation Diagnostics WorkGroup Meeting 2018-06-27

[mhdawson]

Time

UTC Wed 27-Jun-2018 18:00 (06:00 PM):

Timezone	Date/Time
US / Pacific	Wed 27-Jun-2018 11:00 (11:00 AM)
US / Mountain	Wed 27-Jun-2018 12:00 (12:00 PM)
US / Central	Wed 27-Jun-2018 13:00 (01:00 PM)
US / Eastern	Wed 27-Jun-2018 14:00 (02:00 PM)
London	Wed 27-Jun-2018 19:00 (07:00 PM)
Amsterdam	Wed 27-Jun-2018 20:00 (08:00 PM)
Moscow	Wed 27-Jun-2018 21:00 (09:00 PM)
Chennai	Wed 27-Jun-2018 23:30 (11:30 PM)
Hangzhou	Thu 28-Jun-2018 02:00 (02:00 AM)
Tokyo	Thu 28-Jun-2018 03:00 (03:00 AM)
Sydney	Thu 28-Jun-2018 04:00 (04:00 AM)

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Diagnostics%20WorkGroup+Meeting+2018-06-27&iso=20180627T18
• or http://www.wolframalpha.com/input/?i=06PM+UTC%2C+Jun+27%2C+2018+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1ZCeraqdV4ywxe3ajNuXD0CnGOfLBleSOVqjsKNPyK50/edit

Agenda

Extracted from diag-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/diagnostics

• Informal Diagnostic Meetup Around Node Summit #201
• Diagnostics Channel - Next steps #180
• Diag WG Deep Dives - topics #168
• Expectation about tier of support from diagnostic tools and VMs #157
• Node CPU Profiling Roadmap #148
• [async_hooks] stable API - tracking issue #124
• Async-context formalization and diagnostics support #107
• [trace_event] tracking issue #84

Invited

• Diagnostics team: @nodejs/diagnostics

Observers

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

hangouts: https://hangouts.google.com/hangouts/_/ytl/Kd4uBjWD31kD4sp-H1Wi5wNO8TIM0Ta9R6KFEFEHFZ4=?eid=100598160817214911030&hl=en_US
youtube: http://youtu.be/N-cTM71q24o

[mcollina]

I will not be able to join because I will be at WorkerCon (https://www.worker.sh/).

[mmarchini]

I don't think we need to keep #148 on the agenda unless we want to discuss further actions regarding CPU Profiling. The action items we had so far were completed (see #148 (comment)):

[mike-kaufman]

great work @mmarchini! :)

[mike-kaufman]

hangouts: https://hangouts.google.com/hangouts/_/ytl/Kd4uBjWD31kD4sp-H1Wi5wNO8TIM0Ta9R6KFEFEHFZ4=?eid=100598160817214911030&hl=en_US
youtube: http://youtu.be/N-cTM71q24o