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

[mhdawson]

Time

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

Timezone	Date/Time
US / Pacific	Wed 13-Jun-2018 11:00 (11:00 AM)
US / Mountain	Wed 13-Jun-2018 12:00 (12:00 PM)
US / Central	Wed 13-Jun-2018 13:00 (01:00 PM)
US / Eastern	Wed 13-Jun-2018 14:00 (02:00 PM)
London	Wed 13-Jun-2018 19:00 (07:00 PM)
Amsterdam	Wed 13-Jun-2018 20:00 (08:00 PM)
Moscow	Wed 13-Jun-2018 21:00 (09:00 PM)
Chennai	Wed 13-Jun-2018 23:30 (11:30 PM)
Hangzhou	Thu 14-Jun-2018 02:00 (02:00 AM)
Tokyo	Thu 14-Jun-2018 03:00 (03:00 AM)
Sydney	Thu 14-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-13&iso=20180613T18
• or http://www.wolframalpha.com/input/?i=06PM+UTC%2C+Jun+13%2C+2018+in+local+time

Links

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

Agenda

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

nodejs/diagnostics

• Next Diagnostic Summit Informal Diagnostic Meetup Around Node Summit #201
• Strategic Initiatives/Champions like we have on TSC #185
• Diagnostics Channel - Next steps #180
• Diag WG Deep Dives - topics #168
• Node CPU Profiling Roadmap #148
• [async_hooks] stable API - tracking issue #124
• Async-context formalization and diagnostics support #107
• [trace_event] tracking issue #84
• Expectation about tier of support from diagnostic tools and VMs #157
• async_hooks: add currentResource node#21313

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/wee2UHON80xZRs0TZqOEZctuvxIZSlJd7r4YocbspiU=?eid=100598160817214911030&hl=en_US
youtube: http://youtu.be/WUzmqf0Uvu4

• link for participants: https://hangouts.google.com/hangouts/_/ytl/wee2UHON80xZRs0TZqOEZctuvxIZSlJd7r4YocbspiU=?eid=100598160817214911030&hl=en_US
• For those who just want to watch: http://youtu.be/WUzmqf0Uvu4
• youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled

[mcollina]

I would like to include nodejs/node#21313.

[mmarchini]

I won't be able to attend this time.

Updates on the CPU Profiling initiative

• Node.js v10.4.0 got released with V8 6.7, which fixes interpreted frames for Linux perf through a flag (--interpreted-frames-native-stack)
• The CodeEventListener API landed on V8 6.9
  • There's a backport PR to add it to Node.js ( deps: cherry-pick aa6ce3e from upstream V8 node#21126)
• I created a npm package which will use the API to provide runtime togglable --perf-basic-prof functionality to Node.js (mmarchini/node-linux-perf)
  • Found some bugs on the API while working on this package. A fix is already submitted upstream, waiting for it to land on V8 before landing deps: cherry-pick aa6ce3e from upstream V8 node#21126
• Tests for Linux perf were added to Node.js core (test: add test for Linux perf node#20783)
  • Still need to make sure they'll run on every V8 update + daily builds of v8-canary

Updates on the Post-mortem WG merge initiative

• Since there has been no objections on merging the working groups, I'll start to migrate open issues from nodejs/post-mortem to here later this week.

[mmarchini]

Might be worth discussing #201 today as well. Some people are relying on this to finish their travel plans for NodeSummit.

[mike-kaufman]

nodejs/node#21313 and #201 added to agenda

[yunong]

Would it be possible to move #201 up in the agenda? As it turns out I can only attend the first half of the meeting.

[mike-kaufman]

Hangouts:
https://hangouts.google.com/hangouts/_/ytl/wee2UHON80xZRs0TZqOEZctuvxIZSlJd7r4YocbspiU=?eid=100598160817214911030&hl=en_US
youtube: http://youtu.be/WUzmqf0Uvu4

[mcollina]

Are you in the hangout? I do not see anyone.

[mcollina]

Turns out the hangout is full, zoom?