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

Diag WG Meeting - 2017-02 #85

Closed
joshgav opened this issue Feb 6, 2017 · 15 comments
Closed

Diag WG Meeting - 2017-02 #85

joshgav opened this issue Feb 6, 2017 · 15 comments

Comments

@joshgav
Copy link
Contributor

joshgav commented Feb 6, 2017

Date/Time

Thursday Feb 23 2100 UTC (1pm US Pacific)

It's helpful if you give this post a 👍 or 👎 so we know you'd like to attend.

Join/Watch

If you are only observing please use the YouTube channel; Hangouts limits the number of connections.

If the Hangouts link isn't working for you try removing the query string (the ? and all which follows).

Minutes

Agenda

Issues tagged diag-agenda across the nodejs GitHub organization.

nodejs/node

  • proposal: programmatically expose the V8 inspector URL #11496
  • inspector: make debug an alias for inspect #11441
  • Switch the CLI debugger to V8 inspector #11421
  • [WIP] inspector: hint text update #11207
  • What will Domain be replaced with? #10843
  • src: separate trace_event_common from trace_event #10628
  • async_hooks initial implementation #8531

nodejs/diagnostics

  • wg: nominating jkrems #87
  • Request to join Diagnostics WG #86
  • [trace] tracking issue; out of experimental #84
  • AsyncWrap issues - overview #29

nodejs/nodejs.org

  • guides: debugging getting started guide #1131
  • blog: diag wg update and --debug deprecation nodejs.org#1156

/cc @nodejs/diagnostics @nodejs/post-mortem

@misterdjules
Copy link

The agenda isn't specific enough to determine what will be discussed. For instance, what specific topics related to post-mortem will be discussed?

@naugtur
Copy link
Contributor

naugtur commented Feb 6, 2017

I watched a recording of the previous meeting and it seems this post-mortem point is a continuation as there wasn't enough time left for covering what the WG is up to.

Also, there's more details in the minutes googledoc linked.

@joshgav
Copy link
Contributor Author

joshgav commented Feb 6, 2017

@misterdjules @naugtur the agenda in the OP at the moment is just a list of domains we cover here, specific agenda items still need to be added.

We've also added the diag-agenda label in this repo to tag specific issues or PRs for discussion.

@misterdjules
Copy link

misterdjules commented Feb 6, 2017

@joshgav

the agenda in the OP at the moment is just a list of domains we cover here, specific agenda items still need to be added.

Ok, then that's a bit misleading, as in its current form the agenda seems to be complete. I think it would help to mention that's not the case.

@AndreasMadsen
Copy link
Member

AndreasMadsen commented Feb 10, 2017

Agenda:

@watson
Copy link
Member

watson commented Feb 12, 2017

@joshgav did we settle on a date?

@joshgav
Copy link
Contributor Author

joshgav commented Feb 13, 2017

Final time: Thursday Feb 23 2100 UTC (1pm US Pacific) (next Thursday)

@joshgav
Copy link
Contributor Author

joshgav commented Feb 13, 2017

We've also added the diag-agenda label in this repo and some others. Could you all please tag issues you'd like to discuss in the meeting? Thanks!

@watson
Copy link
Member

watson commented Feb 13, 2017

Changing my RSVP to tentative. Something unfortunately came up that I have to go to on that day. It might finish in time for me to attend though, but not sure

@joshgav
Copy link
Contributor Author

joshgav commented Feb 23, 2017

I've added the diag-agenda label over the past couple weeks wherever I had permissions across the nodejs org and tagged some issues to get us started. Following is generated by Rod's node-meeting-agenda script; I'll add it to the OP and notes too.

nodejs/node

  • proposal: programmatically expose the V8 inspector URL #11496
  • inspector: make debug an alias for inspect #11441
  • Switch the CLI debugger to V8 inspector #11421
  • [WIP] inspector: hint text update #11207
  • What will Domain be replaced with? #10843
  • src: separate trace_event_common from trace_event #10628
  • async_hooks initial implementation #8531

nodejs/diagnostics

  • wg: nominating jkrems #87
  • [trace] tracking issue; out of experimental #84
  • AsyncWrap issues - overview #29

nodejs/nodejs.org

  • guides: debugging getting started guide #1131

@joshgav
Copy link
Contributor Author

joshgav commented Feb 23, 2017

One more just added:

@joshgav
Copy link
Contributor Author

joshgav commented Feb 23, 2017

Notes in #88.

Hangouts worked fine, but strangely there wasn't an option to broadcast, so no recording this month. Might have been because the scheduled time in YouTube was incorrect, I'll double-check that next time.

Thank you!

@joshgav joshgav closed this as completed Feb 23, 2017
@naugtur
Copy link
Contributor

naugtur commented Feb 23, 2017

Another thing I noticed about the hangout - it seems I could only join using a paid Google account, not my private one.

@mhdawson
Copy link
Member

Sorry I missed it, meant to be there. As for the recording I've had lots of problems. Sometimes option is there sometimes not.

@mhdawson
Copy link
Member

From reading the notes, I agree with Ali that node-report should be in core. Looking forward to the discussion in the Issue Richard's going to open.

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

6 participants