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 Diagnostics WorkGroup Meeting 2020-02-26 #359

Closed
mhdawson opened this issue Feb 24, 2020 · 2 comments
Closed

Node.js Diagnostics WorkGroup Meeting 2020-02-26 #359

mhdawson opened this issue Feb 24, 2020 · 2 comments
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Wed 26-Feb-2020 17:30 (05:30 PM):

Timezone Date/Time
US / Pacific Wed 26-Feb-2020 09:30 (09:30 AM)
US / Mountain Wed 26-Feb-2020 10:30 (10:30 AM)
US / Central Wed 26-Feb-2020 11:30 (11:30 AM)
US / Eastern Wed 26-Feb-2020 12:30 (12:30 PM)
London Wed 26-Feb-2020 17:30 (05:30 PM)
Amsterdam Wed 26-Feb-2020 18:30 (06:30 PM)
Moscow Wed 26-Feb-2020 20:30 (08:30 PM)
Chennai Wed 26-Feb-2020 23:00 (11:00 PM)
Hangzhou Thu 27-Feb-2020 01:30 (01:30 AM)
Tokyo Thu 27-Feb-2020 02:30 (02:30 AM)
Sydney Thu 27-Feb-2020 04:30 (04: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/diagnostics

  • Future of llnode #355
  • reportVersion semantics are not defined #349
  • 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 Feb 24, 2020
@hekike
Copy link
Contributor

hekike commented Feb 25, 2020

We made a great progress on the last deep dive about memory leaks:
https://docs.google.com/document/d/16PeoMhREmJxSbrpyom9Uypl2lJuMsqAfB96oocDTPwQ/edit

Should we spend the majority of the meeting time again to continue it?

@mhdawson
Copy link
Member Author

PR for minutes: #361

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

2 participants