Tracing WG Meeting 2016-01-26

[pmuellr]

Date/Time: Tuesday, January 26, 2016 at 2:00pm Eastern - world time

Availablity in doodle: http://doodle.com/poll/n7m2z8dym6z7u9fz

Agenda and minutes can be collected in here and copied into this repo later:
https://docs.google.com/document/d/1OnfT8jFjOsEu-RjFbsgB80EQzola3ZvRe2N027nOv5E/edit?usp=sharing

Previous minutes: https://github.com/nodejs/tracing-wg/blob/master/wg-meetings/2015-11-19.md

Hangout on air for active participants: https://plus.google.com/hangouts/_/hoaevent/AP36tYcxxA_nKveUTsictv1k-qcJHu2ti1uI5c6sqb7eYb4RyFQOBA?hl=en

YouTube movie for observers and saved recording: http://www.youtube.com/watch?v=DvQ7QSyEe64 (delayed for a minute or so)

Hangout on air event for more details: https://plus.google.com/events/c5n1int7rfegr3lqs3ujr2707e4 (moderator must start here to start recording meeting)

Agenda discussion can happen in this thread.

(format loosely copied from nodejs/Release#38)

(instructions for creating Hangouts On Air on the nodejs/node wiki)

[AndreasMadsen]

Agenda discussion:

Almost nothing have happened on the async_wrap front (documentation was updated). But I think we can move a lot with the trace_event.h story, we have a very specific usecase (GC metrics - see nodejs/node#4496) and trace event has finally landed in v8 4.9 (see #30 (comment)).

[pmuellr]

@nodejs/tracing Happy 2016, Tracing Work Group members!

I believe I've got everything set up for the next meeting.

Add your availability to the doodle linked above. The doodle covers week days 1/18 - 1/29, 11am to 8pm eastern.

Once we've settled on a date, I'll update the relevant bits.

I think you can subscribe/join the Hangout on Air event (link in first comment), and add to your calendar; the date for the event is currently set for 11/29 8pm, but I'll change it to the actual date when settled.

[bripkens]

@pmuellr: Can I join this hangout as well? I am not a working group member, but I am very interested in the trace-event story.

btw.: How does one become a working group member? Is there any document on how this works?

[pmuellr]

Great question @bripkens !!

The only real constraint on joining the hangout is leaving room for folks we expect to be joining. The way I set the Hangout on Air up, 15 people should be able to be on at the same time. The recent meetings certainly had room for a few more people. Worse case is asking folks who just want to listen, to watch the slightly delayed (1 min, I think) YouTube movie.

re: joining the WG. The only real artifacts behind the WG are the nodejs "Tracing" team and this repo. I believe you can request to join yourself (hopefully on that page). I don't know what the rules are re: joining.

The team is currently just used as a reference in comments like the one I made above, to notify folks about things. You could also "Watch" this repo to the same effect.

[bripkens]

Worse case is asking folks who just want to listen, to watch the slightly delayed (1 min, I think) YouTube movie.

Perfect, I'll try to be there.

re: joining the WG. The only real artifacts behind the WG are the nodejs "Tracing" team and this repo. I believe you can request to join yourself (hopefully on that page). I don't know what the rules are re: joining.

I am not a member of the nodejs organization so I cannot do that.

Thanks for explaining @pmuellr :)

[pmuellr]

For future reference, there appear to be some "official" rules re: becoming a Node.js collaborator here:

• https://nodejs.org/en/get-involved/development/#collaborators

There are no "rules" for this WG regarding watching the meetings, access to the repo, etc though, for folks who are not collaborators, at this point.

[AndreasMadsen]

Added to agenda:

• Status update on: #3504 – async_wrap: make native API public

edit: I've updated the agenda to reflect the recent discussion in nodejs/node#3504

[pmuellr]

According to Doodle, we had all 12 folks line up for one time:

• Tuesday January 26 2016 at 2:00pm Eastern

See the top comment for a link to the world time converter for this meeting. The Hangout on Air event has been updated, so I think you can "subscribe" or "attend" or something to get it auto-added to your Google Calendar (if you have one).

Talk to you then!

[ofrobots]

Unfortunately I will no longer be able attend the meeting on the 26th.

[pmuellr]

Ah, too bad. I was hoping to get an update on V8 trace_event. Will Matthew be able to make it, cover that, or is there anything you could add about it here?

[matthewloring]

I will have to miss the meeting for the same reason as Ali actually, sorry for the later notice!

[Qard]

I expect a bunch of us may not be there. (The error summit?)

[pmuellr]

So, shall we cancel this, do another doodle, maybe from Feb 1 - Feb 12 (M-F for two weeks)?

[watson]

@Qard The error summit??
@pmuellr Is the meeting is still on for tomorrow or did we cancel?

[pmuellr]

I actually didn't get anyone confirming a cancellation, so I'm planning on
holding the hangout tomorrow. May try to schedule another one sooner so we
can get an update on the tracing bits that have been updated, from
Ali/Matthew.

On Mon, Jan 25, 2016 at 8:56 AM, Thomas Watson Steen <
[email protected]> wrote:

@Qard https://github.com/Qard The error summit??
@pmuellr https://github.com/pmuellr Is the meeting is still on for
tomorrow or did we cancel?

—
Reply to this email directly or view it on GitHub
#38 (comment).

Patrick Mueller
http://muellerware.org

[Qard]

I'm pretty sure at least the Google folks and myself will not be available. You can run it without us though, there just probably won't be anyone to say much about trace_event.h stuff.

[Qard]

@watson Some folks are meeting in SF to discuss async errors and how to handle them better.

[ofrobots]

Let me give a quick update on trace-event here.

1. The basic change to get trace-event headers into V8 has landed in V8. This means any embedder can override a few methods on v8::Platform and to provide their own implementation. The DefaultPlatform provides dummy implementation of these methods.
2. The next step for any embedder would be to provide implementation of a Tracing Controller (TraceBuffer, TraceConfig, TraceLog, ..) as implemented by blink.
3. @fmeawad and myself are working on an implementation of Tracing Controller that can be used by d8. We are planning to implement this in a way to allow other embedders (specially Node) to re-use as much code as possible. I'll update this WG once we have a CL ready for review.
4. Node.js will need some extra features over and above what d8 needs. For example, we may want a separate thread to drain the TraceBuffer asynchronously.

I think the work would become very concrete & parallelizable once we have a Tracing Controller implemented in d8.

[pmuellr]

@nodejs/tracing -

Reminder of the call scheduled tomorrow - time / links in the top comment.

Expect an abbreviated call due to folks who can't make it.

[bnoordhuis]

I might miss the start. I have another meeting first that's starting late.

[pmuellr]

Sorry for delay in getting the minutes together for this meeting.

I've got a PR for the minutes here - #41

Please comment on changes required, or LGTM.

Thanks!

[pmuellr]

meant to cc @nodejs/tracing on that last comment, for folks who follow that way

[pmuellr]

merged the minutes