|
| 1 | +January 26th 2015 |
| 2 | +================================================================================ |
| 3 | + |
| 4 | +* [YouTube recording](http://www.youtube.com/watch?v=DvQ7QSyEe64) |
| 5 | +* [Hangouts Event](https://plus.google.com/events/c5n1int7rfegr3lqs3ujr2707e4) |
| 6 | +* [issue for this meeting](https://github.com/nodejs/tracing-wg/issues/38) |
| 7 | +* [previous meeting](https://github.com/nodejs/tracing-wg/blob/master/wg-meetings/2015-11-19.md) - 2015-11-19 |
| 8 | + |
| 9 | + |
| 10 | +Attendees |
| 11 | +================================================================================ |
| 12 | + |
| 13 | +* @trevnorris - Trevor Norris |
| 14 | +* @thlorenz - Thorsten Lorenz |
| 15 | +* @watson - Thomas Watson Steen |
| 16 | +* @pmuellr - Patrick Mueller |
| 17 | +* @bripkens - Ben Ripkens |
| 18 | +* @AndreasMadsen - Andreas Madsen |
| 19 | + |
| 20 | +Agenda |
| 21 | +================================================================================ |
| 22 | + |
| 23 | +* trace-event is now in V8 4.9; [#30 - next steps](https://github.com/nodejs/tracing-wg/issues/30) |
| 24 | + |
| 25 | +* need more meat / structure in the [#31 - use cases issue](https://github.com/nodejs/tracing-wg/issues/31) |
| 26 | + |
| 27 | +* AsyncWrap |
| 28 | + * [node #3504 - async_wrap](https://github.com/nodejs/node/pull/3504): make native |
| 29 | + API public is unlikely to land. What are the alternatives for integrating |
| 30 | + native addons with AsyncWrap? |
| 31 | + * Follow up on http fix and making MakeCallback reentrant: |
| 32 | + * [node #4509 - Fix async wrap http](https://github.com/nodejs/node/pull/4509) |
| 33 | + * [node #4507 - src: fix MakeCallback error handling](https://github.com/nodejs/node/pull/4507) |
| 34 | + |
| 35 | + |
| 36 | +Minutes |
| 37 | +================================================================================ |
| 38 | + |
| 39 | +## [1:30](https://youtu.be/DvQ7QSyEe64?t=90) - agenda, previous minutes |
| 40 | + |
| 41 | +## [5:36](https://youtu.be/DvQ7QSyEe64?t=336) - trace events |
| 42 | + |
| 43 | +* node branch now available to play with - [issue comment](https://github.com/nodejs/tracing-wg/issues/38#issuecomment-174623789) |
| 44 | + |
| 45 | +* What work can we do in parallel to work Google is doing? |
| 46 | + * what will Google folks be providing? |
| 47 | + |
| 48 | +* What does a trace event look like in the code, including passing data? |
| 49 | + |
| 50 | +* How do we expose the trace buffer to whoever wants to read the trace events? |
| 51 | + * only via special build? |
| 52 | + * provided in existing node build, via native add-on? |
| 53 | + |
| 54 | +* What trace events do we actually provide? |
| 55 | + * very low overhead, and configurable, so we probably want to add a bunch |
| 56 | + * grouped via categories - a grouping mechanism provided by the tracing |
| 57 | + infrastructure |
| 58 | + |
| 59 | +* Probably don't want to have events themselves surface back through JavaScript, |
| 60 | + kills the overhead. |
| 61 | + |
| 62 | +* But probably want to think about configuring the tracing via some kind of API; |
| 63 | + start/stop tracing, configuring what trace categories are enabled, where does |
| 64 | + tracing output go. This API might be only exposed via native add-ons first, |
| 65 | + and then later higher in JS if we find a nice set. |
| 66 | + |
| 67 | +* What are the constraints on the data we can add to a trace event. Eg, presumably |
| 68 | + won't be pointers to things that can move / be freed, since trace events are |
| 69 | + "read" long after events occur. |
| 70 | + |
| 71 | +* Can we allow users to emit events from JavaScript? |
| 72 | + |
| 73 | +* Pat wants to create a couple of issues to focus on some of the particular |
| 74 | + questions. |
| 75 | + |
| 76 | + * how do expose trace events to the user |
| 77 | + * apis to start/stop/configure tracing |
| 78 | + * what are we going to put trace events around |
| 79 | + |
| 80 | + |
| 81 | +## [31:07](https://youtu.be/DvQ7QSyEe64?t=1867) - async wrap status |
| 82 | + |
| 83 | +* native addons integrated with AsyncWrap |
| 84 | + |
| 85 | + * [node #3504- async_wrap: make native API public](https://github.com/nodejs/node/pull/3504) |
| 86 | + * Can we do this? Currently seems impossible | hard; because this exposes |
| 87 | + some internal stuff that we wouldn't want to. Trevor will look into some |
| 88 | + techniques to do this. |
| 89 | + |
| 90 | +* http fix / MakeCallback being re-entrant |
| 91 | + |
| 92 | + * [node #4509 - Fix async wrap http](https://github.com/nodejs/node/pull/4509) |
| 93 | + * [node #4507 - src: fix MakeCallback error handling](https://github.com/nodejs/node/pull/4507) |
| 94 | + * note that this PR has been merged |
0 commit comments