Repository navigation
Node.js Foundation Diagnostics WorkGroup Meeting 2018-04-18 #182
Description
Time
UTC Wed 18-Apr-2018 18:00 (06:00 PM):
| Timezone | Date/Time |
|---|---|
| US / Pacific | Wed 18-Apr-2018 11:00 (11:00 AM) |
| US / Mountain | Wed 18-Apr-2018 12:00 (12:00 PM) |
| US / Central | Wed 18-Apr-2018 13:00 (01:00 PM) |
| US / Eastern | Wed 18-Apr-2018 14:00 (02:00 PM) |
| London | Wed 18-Apr-2018 19:00 (07:00 PM) |
| Amsterdam | Wed 18-Apr-2018 20:00 (08:00 PM) |
| Moscow | Wed 18-Apr-2018 21:00 (09:00 PM) |
| Chennai | Thu 19-Apr-2018 23:30 (11:30 PM) |
| Hangzhou | Thu 19-Apr-2018 02:00 (02:00 AM) |
| Tokyo | Thu 19-Apr-2018 03:00 (03:00 AM) |
| Sydney | Thu 19-Apr-2018 04:00 (04:00 AM) |
Or in your local time:
- http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Diagnostics%20WorkGroup+Meeting+2018-04-18&iso=20180418T18
- or http://www.wolframalpha.com/input/?i=06PM+UTC%2C+Apr+18%2C+2018+in+local+time
Links
- Minutes Google Doc: https://docs.google.com/document/d/14dRC5OT6gD0jP8YG6a7Iunahw86CaGKj2DmQsggq0Jg/edit
Agenda
Extracted from diag-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/diagnostics
- Diagnostics Channel - Next steps #180
- Visualizing Async Context #179
- Diag WG Deep Dives - topics #168
- Node CPU Profiling Roadmap #148
- [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
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: Will be added a few minutes before meeting starts
- For those who just want to watch:
- youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled
Metadata
Metadata
Assignees
Labels
No labels
Activity
mhdawson commentedon Apr 16, 2018
Any chance we can move this 1 hour earlier?
mcollina commentedon Apr 16, 2018
It would be way better for me.
Qard commentedon Apr 16, 2018
I’m happy with earlier. 👌
hashseed commentedon Apr 16, 2018
Not sure I can join this time. I'll be in Sunnyvale for BlinkOn.
mhdawson commentedon Apr 17, 2018
@mike-kaufman you ok with earlier, and if so can we re-schedule?
mike-kaufman commentedon Apr 17, 2018
Yes, good for me.
mmarchini commentedon Apr 18, 2018
I'm attending to The Developers Conference this week and the connection here is not good enough for me to join, so I'll leave an update here again (hopefully I'll be able to attend to the next meeting):
Node CPU Profiling Roadmap #148
v8::CpuProfilerand shared my insights on Node CPU Profiling Roadmap #148 (comment). If anyone have suggestions regarding this it would be really appreciated (especially on how to handle native symbols).llnode
I know this is not on the agenda, but I'd like to mention a few things:
hekike commentedon Apr 18, 2018
What's the final time? Will we do this one hour earlier? (it works for me)
@mmarchini thanks!
mike-kaufman commentedon Apr 18, 2018
OK, updating this to be one hour earlier. Sorry for delayed responses here.
mcollina commentedon Apr 18, 2018
I moved the meeting in the calendar.
mike-kaufman commentedon Apr 18, 2018
Hangouts: https://hangouts.google.com/hangouts/_/ytl/VOUJjux-1XfO_vSR90ACWpmQEkj_58Yx1wNaezT6TiI=?eid=100598160817214911030&hl=en_US
Youtube: http://youtu.be/hePMyxKiCf0
mike-kaufman commentedon Apr 18, 2018
ping @nodejs/diagnostics - this is happening now if you can join. Or should we push back to original time.
mike-kaufman commentedon Apr 18, 2018
OK, we don't have quorum, so we're going to re-convene at noon. Sorry for the confusion :(
mhdawson commentedon Apr 18, 2018
Sorry I missed it, if we move for next time I can get into my calendar.