Node.js Foundation Diagnostics WorkGroup Meeting 2018-11-14

[mhdawson]

Time

UTC Wed 14-Nov-2018 18:00 (06:00 PM):

Timezone	Date/Time
US / Pacific	Wed 14-Nov-2018 10:00 (10:00 AM)
US / Mountain	Wed 14-Nov-2018 11:00 (11:00 AM)
US / Central	Wed 14-Nov-2018 12:00 (12:00 PM)
US / Eastern	Wed 14-Nov-2018 13:00 (01:00 PM)
London	Wed 14-Nov-2018 18:00 (06:00 PM)
Amsterdam	Wed 14-Nov-2018 19:00 (07:00 PM)
Moscow	Wed 14-Nov-2018 21:00 (09:00 PM)
Chennai	Wed 14-Nov-2018 23:30 (11:30 PM)
Hangzhou	Thu 15-Nov-2018 02:00 (02:00 AM)
Tokyo	Thu 15-Nov-2018 03:00 (03:00 AM)
Sydney	Thu 15-Nov-2018 05:00 (05:00 AM)

Or in your local time:

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

Links

• Minutes Google Doc: https://docs.google.com/document/d/12w-fz24fZw0lwwN24o4jEzwWIsf5ZeQLQWTyY8TtqRI/edit

Agenda

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

nodejs/diagnostics

• Meeting timeslot #235
• Diagnostics "Best Practices" Guide? #211
• Diag WG Deep Dives - topics #168
• Expectation about tier of support from diagnostic tools and VMs #157
• [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/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

hangouts: https://hangouts.google.com/hangouts/_/ytl/UiHzX7LaCGayqQLdCupCiud1SklP2bzw4BffFt-8YkY=?eid=100598160817214911030&hl=en_US
youtube: http://youtu.be/JpQYLcacz6Y

[mcollina]

I'm traveling and I won't be able to partecipate.

[mmarchini]

I'm attending Linux Plumbers so won't be able to join. Quick update on async_hooks' current async resource (#248):

I'm working to reopen the .currentAsyncResource() pull request (nodejs/node#21313). I believe most comments were addressed, and now we use a stack of async resources instead of keeping only the last one. The only thing missing before moving forward with this is making HTTPParser async resource be unique for each async operation (today we reuse HTTPParser quite often). There's a PR open to stop reusing HTTPParser in our code base (nodejs/node#24330), but it might need some optimizations before landing.

[mike-kaufman]

hangouts: https://hangouts.google.com/hangouts/_/ytl/UiHzX7LaCGayqQLdCupCiud1SklP2bzw4BffFt-8YkY=?eid=100598160817214911030&hl=en_US
youtube: http://youtu.be/JpQYLcacz6Y

[NatalieWolfe]

Not sure if something weird with Hangouts or if the call just didn't happen, but no one was on for 10 minutes. I unfortunately don't have much of an update. Head down on job things and haven't had much opportunity to focus on the continuation work.