-
Notifications
You must be signed in to change notification settings - Fork 78
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
Node.js Diagnostics WorkGroup Meeting 2022-05-03 #557
Comments
I am on vacation this week and the next. @mhdawson - can you pls run this? |
@gireeshpunathil unfortunately I'm tripple booked at the start of the meeting. I migth be able to join a bit later into the meeting but I don't think I can host this week. |
Maybe should post spawn it to next week ? 👍👎 |
Probably. |
I'm available anyway ^^ |
Did this happen? If not would you like me to move the meeting to next week in the calendar? |
I was there, but I leave after 10 minutes. Yeah for sure :) please |
Moved, closing as new issue will be created for meeting next week. |
Time
UTC Tue 03-May-2022 15:30 (03:30 PM):
Or in your local time:
Links
Agenda
Extracted from diag-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
nodejs/diagnostics
--trace-gc
in the tools tier-list #554mdb_V8
tool in the tier-list #549heapdump
in the tools tier-list #548llnode
in the tools tier-list #547Systemtap
tool tier-list #541DTrace
tool tier-list #540Windows xperf
tool tier-list #5390x
tool tier-list #538node-clinic
tool tier-list #537appmetrics
tool tier-list #536Invited
Observers/Guests
Notes
The agenda comes from issues labelled with
diag-agenda
across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.Joining the meeting
The text was updated successfully, but these errors were encountered: