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 2018-04-18 #182

Closed
mhdawson opened this issue Apr 16, 2018 · 14 comments
Closed

Node.js Foundation Diagnostics WorkGroup Meeting 2018-04-18 #182

mhdawson opened this issue Apr 16, 2018 · 14 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Apr 16, 2018

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:

Links

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

@mhdawson mhdawson self-assigned this Apr 16, 2018
@mhdawson
Copy link
Member Author

Any chance we can move this 1 hour earlier?

@mcollina
Copy link
Member

It would be way better for me.

@Qard
Copy link
Member

Qard commented Apr 16, 2018

I’m happy with earlier. 👌

@hashseed
Copy link
Member

Not sure I can join this time. I'll be in Sunnyvale for BlinkOn.

@mhdawson
Copy link
Member Author

@mike-kaufman you ok with earlier, and if so can we re-schedule?

@mike-kaufman
Copy link
Contributor

Yes, good for me.

@mmarchini
Copy link
Contributor

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:959081 landed and made its way into V8 6.7, which is expected to land on Node.js by May 29th. With this, we'll be able to use Node.js with Linux perf and other external profilers again.
  • I looked into introducing native frames to v8::CpuProfiler and 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).
  • I started to work with @Drieger to create a CodeEventListener API for V8, which later can be used to replace --perf-basic-prof. It's not finished yet, but we believe we'll be able to open a CL next week. If anyone is interested: nodejs/node-v8@b797b63...mmarchini:58ebebbccf595dab76108c50d1b41b79b36399fb

llnode

I know this is not on the agenda, but I'd like to mention a few things:

@hekike
Copy link
Contributor

hekike commented Apr 18, 2018

What's the final time? Will we do this one hour earlier? (it works for me)
@mmarchini thanks!

@mike-kaufman
Copy link
Contributor

OK, updating this to be one hour earlier. Sorry for delayed responses here.

@mcollina
Copy link
Member

I moved the meeting in the calendar.

@mike-kaufman
Copy link
Contributor

ping @nodejs/diagnostics - this is happening now if you can join. Or should we push back to original time.

@mike-kaufman
Copy link
Contributor

OK, we don't have quorum, so we're going to re-convene at noon. Sorry for the confusion :(

@mhdawson
Copy link
Member Author

Sorry I missed it, if we move for next time I can get into my calendar.

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

7 participants