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

WG Meeting Week of February 19th on trace_event #4

Closed
mikeal opened this issue Feb 13, 2015 · 20 comments
Closed

WG Meeting Week of February 19th on trace_event #4

mikeal opened this issue Feb 13, 2015 · 20 comments

Comments

@mikeal
Copy link
Contributor

mikeal commented Feb 13, 2015

We should have a working group meeting this week, there's a lot to discuss but because we have so many people I think that we're going to have to limit the meeting in scope and ask that people unfamiliar with the topic watch the feed rather than get on the hangout since space on hangouts-on-air is limited.

I think we should discuss v8/chrome's trace_event and how this can be leveraged by iojs. In particular, I've heard people wondering if we might actually be able to replace AsyncWrap with trace events which would make it easier to write more unified tooling. If changes to the debugging plan this big are being considered we should shake them out now :)

Off the top of my head I think we need @natduca @ofrobots @trevnorris and @thlorenz and probably others.

@arunoda
Copy link

arunoda commented Feb 13, 2015

I'm happy to watch the feed :)

@rmg
Copy link

rmg commented Feb 13, 2015

I don't think I have anything to offer on this one, and I can always feed my input through @sam-github or @piscisaureus if I hear something on the youtube stream.

@GlenTiki
Copy link

I'll watch the feed. :)

@bnoordhuis
Copy link
Member

I'll try to join but I'm moving next week and I may not have a working internet connection on the 19th yet.

@natduca
Copy link

natduca commented Feb 13, 2015

Happy to join.

@thlorenz
Copy link

We should get Ali from Google (don't remember his last name or github handle) into the discussion as well as he has expressed interest in helping us adopt the v8 tracing format.
Some of you (i.e. @mikeal) may have talked to him at NodeSummit and remember his handle to summon him in here.

I myself would be available any day of the week and early Friday for a meeting.

@thlorenz
Copy link

Also linking in @natduca's very detailed notes regarding tracing in chromium since I believe that some points in there should become part of the discussion.

@ofrobots
Copy link
Contributor

I'll be happy to join. (Hi Thorsten!)

On Fri, Feb 13, 2015 at 9:09 AM, Thorsten Lorenz [email protected]
wrote:

Also linking in @natduca https://github.com/natduca's very detailed
notes nodejs/node#671 (comment)
regarding tracing in chromium since I believe that some points in there
should become part of the discussion.


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

Ali

@thlorenz
Copy link

Awesome @ofrobots, glad to have you :)

@piscisaureus
Copy link

In particular, I've heard people wondering if we might actually be able to replace AsyncWrap with trace events

That sounds a bit strange to me since AsyncWrap and tracing aren't really related. Potentially you're thinking about replacing @trevnorris' tracing support?

@mikeal
Copy link
Contributor Author

mikeal commented Feb 13, 2015

@piscisaureus I think @piscisaureus and @ofrobots can probably explain it better.

@sam-github
Copy link

I'd like to be involved, I'm working on these areas for StrongLoop ATM.

@sam-github
Copy link

Also, is there a target day? Later in the week would work better for me, morning would probably help cross time zones from North American pacific coast through Europe.

@kraman
Copy link

kraman commented Feb 13, 2015

Hi, I would like to join this WG as well. I am working with Sam on the same areas within StrongLoop. Thanks

@mikeal
Copy link
Contributor Author

mikeal commented Feb 13, 2015

Doodle for finding the best time on Thursday. http://doodle.com/yds5u6ns86t85tuu

@trevnorris
Copy link

I've heard people wondering if we might actually be able to replace AsyncWrap with trace events which would make it easier to write more unified tooling

You can't just replace AsyncWrap. It's part of how the asynchronous class structure is created. All that you could do is remove the user exposed hooks. Though the advantage to AsyncWrap is that it is VM independent.

@mikeal
Copy link
Contributor Author

mikeal commented Feb 13, 2015

replace was probably the wrong way to put it, it was more like "feed asyncwrap events in to trace_event"

@Qard
Copy link
Member

Qard commented Feb 16, 2015

I put myself up for any time, though I might just lurk in IRC if it gets too full.

I'm not sure how much I have to contribute to the conversation anyway. I've only just recently started digging into tracing the native side.

@mikeal
Copy link
Contributor Author

mikeal commented Feb 17, 2015

Doodle is closed, Thu 2/19/15 2:00 PM – 3:00 PM PST.

@mikeal
Copy link
Contributor Author

mikeal commented Feb 19, 2015

@Qard Qard closed this as completed Sep 8, 2015
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