Skip to content

Commit 191ad6e

Browse files
mhdawsongireeshpunathil
authored andcommitted
doc: add minutes for Apr 178
PR-URL: #293 Reviewed-By: Gireesh Punathil <[email protected]>
1 parent ddf7d13 commit 191ad6e

File tree

1 file changed

+87
-0
lines changed

1 file changed

+87
-0
lines changed

wg-meetings/2019-04-17.md

+87
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
# Node.js Foundation Diagnostics WorkGroup Meeting 2019-04-17
2+
3+
## Links
4+
5+
* **Recording**: https://www.youtube.com/watch?v=FxsT8qZua-E
6+
* **GitHub Issue**: https://github.com/nodejs/diagnostics/issues/292
7+
8+
## Present
9+
10+
* Michael Dawson (@mhdawson)
11+
* Peter Marton (@hekike)
12+
* Ruben Bridgewater (@BridgeAR)
13+
* Kelvin Jin (@kjin)
14+
* Diagnostics team: @nodejs/diagnostics
15+
16+
## Agenda
17+
18+
## Announcements
19+
20+
*Extracted from **diag-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
21+
22+
* Kevin, perfetto repo is now created, https://github.com/nodejs/perfetto-nodejs-wip
23+
* Have build perfetto with gyp, ironing out a few issues.
24+
* Peter still working on use cases, hope to share today, but hope to share tomorrow and we
25+
can discuss in 2 weeks.
26+
27+
### nodejs/node
28+
29+
* Support pausing the debugger on script load [#24687](https://github.com/nodejs/node/issues/24687)
30+
* Kevin was going to follow up since person who opened left Google.
31+
will report back next time.
32+
33+
### nodejs/diagnostics
34+
35+
* Post-mortem debugging support inside V8/Node.js [#227](https://github.com/nodejs/diagnostics/issues/227)
36+
* We can take agenda tag off, we agree on way forward at summit
37+
now we just need to wait for progress.
38+
39+
* Diagnostics "Best Practices" Guide? [#211](https://github.com/nodejs/diagnostics/issues/211)
40+
* Work that Peter is doing is moving this forward as mentioned before.
41+
42+
* Diag WG Deep Dives - topics [#168](https://github.com/nodejs/diagnostics/issues/168)
43+
* No update this week.
44+
* Peter Marton, after he shares use cases would be good to do deep dive on each use case.
45+
46+
* Expectation about tier of support from diagnostic tools and VMs [#157](https://github.com/nodejs/diagnostics/issues/157)
47+
* No update this week, focus is on defining best practices
48+
* Peter Marton working on a doc with an updated set of user stories.
49+
* Removing agenda tag until we make progress on the best practices.
50+
51+
* \[async_hooks\] stable API - tracking issue [#124](https://github.com/nodejs/diagnostics/issues/124)
52+
* Related is issue around async context propagation. Vladimir is trying to resolve one
53+
test case where state is lost.
54+
55+
* Async-context formalization and diagnostics support [#107](https://github.com/nodejs/diagnostics/issues/107)
56+
* We don’t have Mike K this week so no update.
57+
58+
* \[trace_event\] tracking issue [#84](https://github.com/nodejs/diagnostics/issues/84)
59+
* Working on perfetto but nothing else to report this week.
60+
61+
* Flag for unhandled rejects in core
62+
* Should we talk about new default?
63+
* you can opt in, strict or warn (almost default but no deprecation warning)
64+
* Would like to have a survey to get more opinions on what they would prefer
65+
* blog post, followed by survey on what they would like as the default
66+
* would also want to figure based on type of user.
67+
* Ruben, will open an issue and work on the questions the first step.
68+
69+
* Diagnostic WG mission, was surprised current content.
70+
* Peter will submit PR to suggest a few modifications.
71+
72+
* Who’s coming to summit
73+
* Michael, Ruben and Peter from those in attendance.
74+
75+
76+
## Q&A, Other
77+
78+
* Question (@wentout) about Async Storage and it’s connection to #107
79+
https://github.com/nodejs/node/pull/26540
80+
81+
* No other questions this week
82+
83+
## Upcoming Meetings
84+
85+
* **Node.js Foundation Calendar**: https://nodejs.org/calendar
86+
87+
Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.

0 commit comments

Comments
 (0)