Skip to content

Commit

Permalink
adding minutes from 12/13 meeting (#135)
Browse files Browse the repository at this point in the history
  • Loading branch information
mike-kaufman authored Jan 3, 2018
1 parent 62931cf commit 4120aed
Showing 1 changed file with 95 additions and 0 deletions.
95 changes: 95 additions & 0 deletions wg-meetings/2017-12-13.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,95 @@
# Node.js Foundation Diagnostics Working Group Meeting 2017-12-13 Minutes


## Attendees

- @mike-kaufman
- @mhdawson (Michael Dawson)
- @ofrobots
- @kjin
- @dominickramer
- @watson
- @mrkmarron
- @qard (Stephen Belanger)
- Daan Leijen


## Links

* **This Meeting**:
* Minutes: https://github.com/nodejs/diagnostics/blob/master/wg-meetings/2017-12-13.md
* Notes: https://docs.google.com/document/d/1ZkTGBUk5lgodtwtlY_0eoInpctVGpf6ofB5TyUF0hqs/edit?usp=sharing
* You Tube: https://www.youtube.com/watch?v=nLsJm0_bP3U
* **Previous Meeting**:
* Minutes: https://github.com/nodejs/diagnostics/blob/master/wg-meetings/2017-11-29.md
* Notes: https://docs.google.com/document/d/1QCV-w86zINGyAZQ5l1fZ8VCjRkFHuyBYD9Unij458kk/edit#

## Notes

### Call Capacity
- # of Ppl on call may reach 10-person capacity on hangouts
- Sum options to address were discussed
- we should watch it going forward & see if we need to change anything up

### Integrate C++ AsyncHooks Embedder API with native abstraction [#13254](https://github.com/nodejs/node/issues/13254)
- need Champion from those working AsyncHooks.
- Defer discussion to next meeting when Andreas is in the meeting

### \[async-hooks\] request for feedback [#129](https://github.com/nodejs/diagnostics/issues/129)
- Not enough feedback yet
- **Actions**:
- [ ] All to promote/tweet more
- [ ] Michael to ask Foundation to re-tweet request for input from Node.js account

### \[async_hooks\] stable API - tracking issue [#124](https://github.com/nodejs/diagnostics/issues/124)
- defer to next week

### Diagnostics WG Summit - Feb 12-13, 2018 - Ottawa, ON Canada [#121](https://github.com/nodejs/diagnostics/issues/121)
- overflow/too many attendees?
- don't think it will be a problem
- should accomodate up to 30
- structure
- proposal of
- 1/2-day overview
- 2 * 1/2-day breakout sessions
- 1/2-day report-out/wrap-up
- **Actions**:
- [ ] @mhdawson to set candidate agenda and move from comments to top of issue 121
- [ ] @mhdawson to list any info needed from attendees plans to do that early in Jan.

### Async-context formalization and diagnostics support [#107](https://github.com/nodejs/diagnostics/issues/107)
- really rough draft posted to GH: https://github.com/mike-kaufman/async-context-definition
- feel free to comment
- **Actions**:
- [x] - @mike-kaufman to post link on issue #107

### Node.js Collaboration Summit diagnostics discussion minutes [#95](https://github.com/nodejs/diagnostics/issues/95)
- we should close #95 & open a seperate issue to track 2nd point
- Thomas is async hooks not trying to fix this ?
- Mike K, 2 issues async hooks handles one. Second one is around wanting to know
that events (ex mongo read) has occurred.
- Diagnostic Channel
- https://github.com/Microsoft/node-diagnostic-channel
- one proposal to address this in community acceptable-way
- Thomas to add doc to capture modules that don’t play well yet with Async Hooks.
- **Actions**:
- [x] @mike-kaufman - we should close this & open a seperate issue to track getting out of monkey-patching
- [ ] @watson to add doc to capture modules that don’t play well yet with Async Hooks.


### \[trace_event\] tracking issue [#84](https://github.com/nodejs/diagnostics/issues/84)
- @kjin working on making set of macros in node up-to-date
- going forward:
- There's a set of macros people requrested but don't yet exist
- Figure out a longer-term path forward

### Perf/Node.js [#168](https://github.com/nodejs/benchmarking/issues/168)
- v8 bug has been opened

### Meta data for llnode - Node.js version 8 [#50](https://github.com/nodejs/post-mortem/issues/50)
- need to close loop on this
- is it really a problem?
- Some claim it is fixed
- Person who reported has not responded to questions
- give them another week or two & then close if no response

0 comments on commit 4120aed

Please sign in to comment.