Skip to content

Node.js Foundation Diagnostics WorkGroup Meeting 2019-03-06 #278

New issue

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

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

Already on GitHub? # to your account

Closed
mhdawson opened this issue Mar 4, 2019 · 2 comments
Closed

Node.js Foundation Diagnostics WorkGroup Meeting 2019-03-06 #278

mhdawson opened this issue Mar 4, 2019 · 2 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Mar 4, 2019

Time

UTC Wed 06-Mar-2019 17:30 (05:30 PM):

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

  • Support pausing the debugger on script load #24687

nodejs/diagnostics

  • Diagnostics WG Summit Agenda - 2019-03-07, 2019-03-08 #267
  • Post-mortem debugging support inside V8/Node.js #227
  • Diagnostics "Best Practices" Guide? #211
  • Diag WG Deep Dives - topics #168
  • Expectation about tier of support from diagnostic tools and VMs #157
  • [async_hooks] stable API - tracking issue #124
  • Async-context formalization and diagnostics support #107
  • [trace_event] tracking issue #84

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 Mar 4, 2019
@mike-kaufman
Copy link
Contributor

I think this will be cancelled because most people will be in transit for summit, correct?

@mhdawson
Copy link
Member Author

mhdawson commented Mar 5, 2019

I think we agreed to cancel in the last meeting.

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

No branches or pull requests

2 participants