►
From YouTube: Node.js Diagnostics WG Meeting - 2019-02-06
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
C
A
C
Had
a
relatively
let's
open
up,
the
like
I
think
we
had
a
bunch
of
topics,
so
we
basically
said
okay,
so
key
themes,
so
we
started
in
with,
like
you
know,
and
you
start
with
general
post-mortem
proposed
since
key
themes-
part
twos,
so
we
talked
about
like
monitoring,
debugging
platform,
neutral
platform,
neutrality,
testing
and
documentation
so
sort
of.
Basically,
we
had
some
of
the
key
themes
that
we
want
to
have
some
coverage
on,
and
then
we
did
breakouts
for
the
rest
of
the
sessions.
A
C
D
C
C
B
B
C
C
E
C
C
A
C
B
Don't
know,
do
we
want
to
put
post-mortem
debugging
as
part
of
debugging
or
is
it
like
a
separate
thing.
C
So
under
post-mortem
debugging
I
could
see
we
still.
One
thing
we
still
need
to
figure
out.
Is
our
heap
dump
strategy
like?
What
do
we
recommend?
How
do
we
do?
I
mean
we
I
think
you
know
that
we've
had
issues
about
like
perhaps
pulling
in
the
heaped-up
module
into
core
or
some
capability
to
generate
heap
dumps.
There's
been
discussion,
though,
that
maybe
you
can
already
do
that
effectively
enough
through
the
the
inspector
API,
but
I,
don't
think
we
have
a
solid
like
consensus
on
hey.
This
is
the
way
you
should
do
it
and
we're.
C
E
C
B
F
B
A
A
But
it's
probably
you
know
an
interesting
discussion
and
a
high
level
for
people
to
have
so.
A
So
I
mean
like
profiling
and
monitoring
I
think
are
two
separate
things
right.
It's
like
you've
got
an
app
and
you
want
to
know
when
you
know
certain
things
happen
in
the
app
and
profiling
is
like:
hey,
you've
got
a
perf
problem
and
you're
sitting
down,
and
you
know
re
running
these
cases
and
looking
into
you
know,
Flynn
graphs
or
whatever
so
I
think
monitoring
is
distinct
from
profiling.
So
how.
B
D
C
C
Yeah
we
could
just
leave
that
on
the
like
on
the
agenda.
That's
okay!
Now,
let's
you
know
switch
over
to
live
debugging.
We
know
that
we
can
debug
with
the
chrome.
You
know
the
chrome
tools
or
the
command-line
tools.
Is
there
anything
else
like
gaps
or
things
that
we
are
hearing
that
people
are
complaining
about
it
in
right?.
B
B
All
of
them,
yeah,
I,
think
I
think
so.
Instead
of
like
the
agenda
review,
what
I
have
here
from
10:15,
we
could
just
allocate
like
two
hours
to
go
through
everything
and
take
inventory
of
what
we
have
and
what
we
think
is
important
to
discuss
and
then
set
the
time
aside
for
for
actual,
like
in-depth
discussions,
because
I
could
imagine
that
there
are
people
who
are
very
passionate
about
certain
things
and
others
don't
really
care
yeah.
C
A
Yeah
I
think
that
per
your
earlier
comment.
Michael
does
this?
Have
an
owner
I
think
that's
like
in
my
mind,
it's
like
somebody
probably
needs
to
take
this
kind
of
sketch
it
out
a
little
bit
more
like
I.
Would
guess
that
when
we
meet
next
time
in
two
weeks
we
can
sort
of
be
clear
about.
You
know
what
what
people
need
to
kind
of
show
up
with.
So
we
have
a
productive
conversation
and.
B
F
B
C
B
B
G
G
C
C
B
A
A
Think
there's
different
ideas
about
how
I
should
use
my
time
and
so
I
realized
that
there's
some
impact
there
I
talked
with
mark
market
and
you
know
family
events
that
are
scheduled
for
that
period
of
time,
and
so
he's
not
traveling.
A
H
C
Okay,
because
the
thing
I
wanted
to
bring
up
under
monitoring
was
I
think
we've
kind
of
stalled
on
the
trace
point
Edition
like
adding
new
trace
points,
I,
don't
know,
I,
don't
know
what
people's
perspective
is
on
that
like
we've,
there's
talk
about
perfetto
with
to
you
know,
have
a
new
engine
to
capture
those
trace
points,
but
I,
don't
know
that
we
have
the
trace
points.
We
would
want
note
and
and
so
forth,
right.
B
C
I
think
it
would
be
good
to
let
yeah
I
just
wrote
it
in
let's
tag
him
with
a
where
we
out
with
that
mmm-hmm
cuz.
You
know
in
my
perfect
world,
if
we're
ready
to
start
adding
a
bunch
of
trace
points,
we
should
be
doing
something
at
least
to
encourage
people
or
make
that
on
their
radar
as
something
they
could
contribute
with
right.
A
It
would
be
interesting
to
know
now
how
they're
being
used
I
think
today,
like
the
trace
points
that
we
have
mm-hmm-
and
you
know
cuz
part
of
me
wonders-
is
the
fact
that
you
know
we
haven't
necessarily
seen
a
lot
of
trace
points.
Being
added.
Is
that,
due
to
some
of
the
instability
in
the
trace
collector,
that
should
be
mitigated
with
the
perfetto
thing
yep,
where
that
there
was
just
some
instability
and
people
are
like?
Oh
yeah,
you
know
it's
not
there.
A
So
I'm,
not
gonna
start,
you
know
chasing
after
it
or
is
there
some
other
thing
going
on
there,
but
that
would
I
think
be
an
interesting
thing.
I.
C
Think
that's
certainly
the
you
know
what
I
I
think
we
were
waiting
to
be
able
to
do
him
effectively.
A
JavaScript
was
a
blocker,
but
you're,
probably
right
that
that
instability
would
have
also
been
another
if
you
started
to
try
and
work
with
it
and
it
didn't
work
so
well,
but
having
yeah
so
talking
about
that
whole
general
thing
getting
a
bit
of
an
update
and
then
you
know
we
can
probably
have
one
of
the
breakouts
to
dive
into
like
okay.
How
do
we?
What
are
the
concrete
next
steps
to
make
progress
on
that
front?
C
A
C
C
B
C
E
B
C
B
B
C
Yeah,
some
of
them
some
of
them.
It
like
it'd,
be
nice
to
have
seen
well,
actually
no
I
mean
like
say
if
I
think
the
invited
one
should
be
that
if
we
get
it
get,
somebody
would
be
the
should
have
the
first
day
right,
right,
yeah
and
I'd
even
vote
for
the
intro
to
open
census
to
be
on
the
first
day.
Okay,.
A
It's
fine
for
a
straw,
man
and
sure
yeah
things
will
evolve,
I
think
yep,
but
yeah
I
do
think
it's
nice
to
sort
of
have
you
know
some
of
the
talks
or
some
of
the
things
sort
of
interspersed
with
some
of
the
the
breakouts
right
and
just
to
kind
of
break
things
up.
That
said,
it's
sometimes
nice
to
have
some
of
the
talks
that
are
informative
and
will
you
know,
have
impact
on
some
of
the
breakouts
ahead
of
those
breakouts
I.
Don't
necessarily
know
how
to
balance
that.
A
B
D
A
B
A
C
B
B
A
A
B
Like
that
yeah
and
the
lunch
at
1:00,
lunch
is
the
one
that
we
can't
I
mean
I
can't
move
it
earlier,
because
it's
like
we
have
a
table
reserved
so
that
we
don't
clash
with
the
rest
of
Engineers
right
and
then
for
the
afternoon
when
it's
breakouts,
essentially
yeah
so
I
guess
I
mean
we
can.
We
can
then
make
that
two
like
two
breakout
sessions
in
succession,
how.
B
B
C
C
B
B
C
C
B
B
A
I
think
it's
probably
good.
It's
it's
a
good
point
to
get
feedback
from
other
people
who
aren't
on
the
call
that
is
like
hey.
You
know
this
is
the
current
proposed
agenda.
Let
us
know
if
there's
anything
missing
or
people
have
you
know,
and
you
want
to
volunteer
for
something
yeah
and
I.
Think
there's
enough
flexibility
in
some
of
these
things
that
we
can
wiggle
some
things
around
right,
yeah.
B
C
B
C
F
C
F
D
C
A
I
feel
pretty
pretty
good
about
it.
Now,
there's
a
number:
we've
only
got
about
seven
minutes
left
and
there's
a
number
of
other
things
here
on
the
agenda.
So
I
thought
maybe
we
can
do
sort
of
a
lightning.
You
know
burn
through
on
this
thing,
I
think
the
next
one
is
2
to
7,
which
is
post
mortem,
debugging
support
and
ciebie
8.
You
know,
Jas
I,
don't
know,
except
this
still
a
call
or
you'd
drop
the
chase
you're
on
yeah.
B
G
A
C
I
Probably
Mike
was
not
present
on
16th
when
we
met
so
the
bottom
line
is
we
we
met
and
briefly
discussed
about
what
are
the
the
structure?
What
should
be
the
content
on
the
best
practice
and
what
are
the
tools
we
want
to
prioritize
and
who
wants
to
pick
up
items
and
things
like
that?
I
A
A
A
B
B
A
Matteo
we
should
ask
Matteo
about
you
know
where,
where
he
thinks
you
know,
this
fits
in
his
world
I
think
he
was
the
one
that
asked
about
resurrecting
it
on
the
agenda
like
few
weeks
ago.
So
maybe
it's
some
that
we
can
figure
out
like
hey.
Does
this
thing
have
legs
and
does
somebody
want
to
drive
on
it?
Can
we
make
progress
if
not
we
just
sort
of
should
pull
it
off
of
here,
I
think
so.
Yep.