Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node.js Foundation Diagnostics WorkGroup Meeting 2019-09-25 #328

Closed
mhdawson opened this issue Sep 23, 2019 · 3 comments
Closed

Node.js Foundation Diagnostics WorkGroup Meeting 2019-09-25 #328

mhdawson opened this issue Sep 23, 2019 · 3 comments
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Wed 25-Sep-2019 17:30 (05:30 PM):

Timezone Date/Time
US / Pacific Wed 25-Sep-2019 10:30 (10:30 AM)
US / Mountain Wed 25-Sep-2019 11:30 (11:30 AM)
US / Central Wed 25-Sep-2019 12:30 (12:30 PM)
US / Eastern Wed 25-Sep-2019 13:30 (01:30 PM)
London Wed 25-Sep-2019 18:30 (06:30 PM)
Amsterdam Wed 25-Sep-2019 19:30 (07:30 PM)
Moscow Wed 25-Sep-2019 20:30 (08:30 PM)
Chennai Wed 25-Sep-2019 23:00 (11:00 PM)
Hangzhou Thu 26-Sep-2019 01:30 (01:30 AM)
Tokyo Thu 26-Sep-2019 02:30 (02:30 AM)
Sydney Thu 26-Sep-2019 03:30 (03:30 AM)

Or in your local time:

Links

Agenda

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

nodejs/node

  • Async Hooks do not recognize execution contexts created when processing thenables #22360

nodejs/diagnostics

  • Proposal to drive Diagnostics WG initiatives through user journeys #295
  • Diagnostics "Best Practices" Guide? #211
  • [async_hooks] stable API - tracking issue #124

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

@mhdawson mhdawson self-assigned this Sep 23, 2019
@mmarchini
Copy link
Contributor

Reminder: this meeting we won't go through the agenda, but instead we'll deep dive on #327 (process crash analysis), as discussed last meeting.

(I won't be able to join this meeting though)

@gireeshpunathil
Copy link
Member

was there a minute captured for this sitting? if so can we close this?

@gireeshpunathil
Copy link
Member

meeting happened, closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants