Node.js Diagnostics WorkGroup Meeting 2022-02-08

[mhdawson]

Time

UTC Tue 08-Feb-2022 16:00 (04:00 PM):

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

Or in your local time:

• https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Diagnostics%20WorkGroup+Meeting+2022-02-08&iso=20220208T1600
• or https://www.wolframalpha.com/input/?i=04PM+UTC%2C+Feb+08%2C+2022+in+local+time

Links

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

Agenda

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

nodejs/diagnostics

• meeting time, again #507
• 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

• 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

[gireeshpunathil]

I have a time conflict with this instance that I cannot resolve. @mhdawson - are you in a position to chair this one?

[mhdawson]

I can chair this one.

[RafaelGSS]

The meeting has started? It looks like nobody started it yet.

[Qard]

Yeah, still just waiting here.

[RafaelGSS]

I'll try to re-enter

[tony-go]

I'm here too ^^

[bmeck]

I'll pop on as host

[tony-go]

Hi 👋🏼

If I have technical questions regarding topics we tackle today. Should I post them here ?

[bmeck]

Sure, then we can triage if they need their own issue

…

On Tue, Feb 8, 2022, 11:10 AM Tony Gorez ***@***.***> wrote: Hi 👋🏼 If I have technical questions regarding topics we tackle today. Should I post them here ? — Reply to this email directly, view it on GitHub <#526 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABZJI36HN2JAXTMOATKGGTU2FFAFANCNFSM5NXMSXTA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are on a team that was mentioned.Message ID: ***@***.***>

[mhdawson]

Sorry I missed this, I have a family emergency and will be out for a few days.

[tony-go]

Sure, then we can triage if they need their own issue

Thanks @bmeck 🙌 ^^ It's more to be sure to understand the big issue there:

• My first question was related to diagnostics_channels. Yesterday you mention that it should be brought "to the core". Does that mean that it should be moved from lib to src? (And more generally, is "core" mean src/cpp ?)
• Regarding the high cost of using AsyncLocalStorage you mention, the solution should be the same as diagnostics_channels?
• What is the cause of the memory issues you mentioned regarding the usage of async_hooks?

If anyone starts something, I'll happy to look at the PR :)

Sorry I missed this, I have a family emergency and will be out for a few days.

@mhdawson 💪

[github-actions]

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.