Node.js Diagnostics WorkGroup Meeting 2020-11-11

[mhdawson]

Time

UTC Wed 11-Nov-2020 17:30 (05:30 PM):

Timezone	Date/Time
US / Pacific	Wed 11-Nov-2020 09:30 (09:30 AM)
US / Mountain	Wed 11-Nov-2020 10:30 (10:30 AM)
US / Central	Wed 11-Nov-2020 11:30 (11:30 AM)
US / Eastern	Wed 11-Nov-2020 12:30 (12:30 PM)
EU / Western	Wed 11-Nov-2020 17:30 (05:30 PM)
EU / Central	Wed 11-Nov-2020 18:30 (06:30 PM)
EU / Eastern	Wed 11-Nov-2020 19:30 (07:30 PM)
Moscow	Wed 11-Nov-2020 20:30 (08:30 PM)
Chennai	Wed 11-Nov-2020 23:00 (11:00 PM)
Hangzhou	Thu 12-Nov-2020 01:30 (01:30 AM)
Tokyo	Thu 12-Nov-2020 02:30 (02:30 AM)
Sydney	Thu 12-Nov-2020 04:30 (04:30 AM)

Or in your local time:

• https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Diagnostics%20WorkGroup+Meeting+2020-11-11&iso=20201111T1730
• or https://www.wolframalpha.com/input/?i=05PM+UTC%2C+Nov+11%2C+2020+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1Y-yEVS_W8q3cX-JXBmMQO46Op0ugT8gR4GTUr8s8kr0/edit

Agenda

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

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

• link for participants: https://zoom.us/j/466707925
• For those who just want to watch:
• youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled

[RafaelGSS]

Are missing the issues?

[gireeshpunathil]

looks like the (meeting-generating) script error. /cc @mhdawson

let us use agenda generated for the previous meeting? may be some additions & deletions that we can figure out in the meeting

[RafaelGSS]

Indeed.

[gireeshpunathil]

It was only 3 of us in the meeting, so we declared the meeting as cancelled. Will re-convene in 2 weeks time.

[Qard]

The schedule says it doesn’t start for another twenty minutes. 🤔

[mmarchini]

FYI the US went off daylight saving time last week, and the meeting is (apparently) scheduled based on US time. It shows 9:30am PST in the schedule above and calendar, it's 9:11am PST now here.

[mmarchini]

Speaking of which, the meeting time should not change when a country goes in our out daylight saving time.

[gireeshpunathil]

o! my bad. Did not notice the change in the calendar.

[RafaelGSS]

Probably I used to join the normal meeting time from my timezone. I see now that the meeting should start at 2h30PM (GMT-3). So, I'm able to join again 👍

[gireeshpunathil]

@mmarchini - are you available to run the meeting? If yes, I would like to opt out (due to the misunderstanding, I had kept some other plans)

[mmarchini]

@gireeshpunathil yes, I can run the meeting today :)

Does the current time (as it shows on the calendar) works for everyone moving forward? Otherwise I can start a Doodle to figure out a better time.

[legendecas]

I'm afraid I'll not be available for the changed meeting time due to daylight saving. It's too late in UTC+8 area.

[mmarchini]

Created #442 to discuss meeting time changes if those are necessary.

[Qard]

There was only three this time too so we decided to cut it short. I would like to get some more attention on these PRs though:

• lib: add span API to diagnostics_channel #35534
• lib: make diagnostics_channel async iterable #35532

There was also a suggestion about a blog post for diagnostics_channel that we can point new module authors to as encouragement to try the API in their modules. :)

[mmarchini]

We canceled the meeting since there were only the three of us and there wasn't much to discuss on actionable topics. Only things I'd like to highlight:

1. We briefly discussed creating an issue to track diagnostic_channels documentation as well as adoption in the ecosystem (could be two issues)
2. We briefly discussed CPU PRofiling roadmap. Current issue should be closed and remaining topics (being able to capture profile without stopping) should go on a separate issue
3. Please review lib: add span API to diagnostics_channel node#35534 and lib: make diagnostics_channel async iterable  node#35532

(edit @Qard beat me to it 😅)

[mhdawson]

Thanks, had a meeting that ran late so only tried to join 30 mins late. Thanks for the updates on the issue :)