►
From YouTube: Node.js Diagnostics WG Meeting - 2018-08-22
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
You
know
I,
think
quick,
summary
of
what
we
talked
about
and
the
agenda
there's
the
for
whoever's
watching
on
the
stream,
because
we
started
late,
the
the
deep
dives
are
still
open
and
we
need
one
scheduled
for
a
sink
context.
There's
you
know
the
tiers
of
support
for
diagnostic
tools
and
Michael
Dawson
as
a
PR,
which
sort
of
writes
that
stuff
up
and
his
markdown
broke.
Ci.
A
There's
a
sink
hook,
stuff
and
I.
Think
the
key
point
there
is
that
you
know
if
support
is
needed
from
the
8
that
they're
you
know
it.
We
need
to
make
sure
that
there's
enough
lead
time
or
no
12.
So
some
decision
needs
to
be
made
in
the
next
three
months,
Perley
on
a
saint
context,
formalization
so
I
think,
there's
again
there's
some.
A
You
know
we
need
to
do
a
deep
dive
on
it
and
and
we'll
try
and
get
that
scheduled
soon,
and
then
that
brings
the
last
issue
on
the
agenda
here,
which
is
issued
number
84,
which
is
the
trace
of
end
stuff
and
I.
Don't
know,
what's
happened
here,
I,
don't
know
if
anybody
does.
If
anybody
could
speak
to
it,
there's
been
any
progress
on
any
of
this
I.
A
B
A
B
A
C
C
D
Particular
question
is
more
relevant
to
users
of
HT
PQ
rather
than
Diagnostics
per
se.
I
think
diagnostic
should
provide
the
the
means
and
the
mechanism
to
provide
diagnostic
data
or
what
precise
data
you
want
from
HTTP
to
I
mean
a
user
of
hd-dvd
would
be
much
more
attuned
to
what
are
the
needs
there
then,
for
example,
I
don't
have
practical
experience.
Iit
can
speak
too
much
to
it.
I.
C
D
B
I'm
sort
of
the
same
thought
that,
like
I,
think
like
if
we
had
unlimited
cycles,
it
would
be
great
if
we
could
dive
in
and
figure
out.
You
know
what
diagnostic
trace
points
and
all
that
would
be
useful.
Probably
if
you
know
if
I
was
doing
that,
I
would
go
out
and
ask
like
Ally
suggesting
the
end
users.
B
A
A
Think
as
to
whether
or
not
it's
you
know
under
the
auspices
of
this
working
group,
I
I
would
I
would
have
anticipated
it
like
somebody
coming
at
it
from
like
in
the
M
point
of
view,
might
be
like
hey.
We
need
this
specific
data
because
we're
trying
to
show
this
stuff,
which
case
it
would
fit,
but
yeah
I,
agree
like
unless
I
were
to
actually
like
dive
in
and
really
start
thinking
about
it.
I
really
wouldn't
know
what
to
say
here.
C
B
A
B
You
know
I
kind
of
see
as
part
of
our
overall
like
there's
the
push
on
trace
events
that
we
want
to
make
sure
we
have
good
coverage
across
the
board,
so
I
see
it
fitting
into
that
sort
of
larger
sort
of
initiative
as
a
how
do
we
make
node
a
good
provider
of
trace
events
but
yeah
unless
somebody's
got
a
particular
interest?
I,
don't
know
what
we
do
to
push
that
forward
outside
of
that
kind
of
thing.
Right
now,.
B
C
B
A
C
B
C
E
Sorry
for
jumping
back
to
the
South
40s,
but
now
I,
double-checked
and
I'm
also
going
to
comment
it
to
the
issue.
But
there's
this
new
code
even
listener
API
by
v8,
which
madhouse
was
working
with
v8
team
together,
can
be
added,
to
least
to
the
unsupported
into
the
section
which
needs
to
reconsideration
the
not
yet
classified.
E
E
Sure,
and
one
more
context
is
that,
maybe,
as
you
know
that
we
we
work
with
matter
us
as
Netflix,
so
he
be
supporting
him
that
he
can
see
beautiful
full
time
in
LA,
yes,
actually
yep
and
just
I
would
like
to
give
a
heads
up
that
our
next
focus
would
be
to
improve
the
postmortem
debugging
with
promises.
So
if
anyone
has
any
idea
about
that-
and
that
would
be
helpful
right
now-
we
are
in
a
research
phase
that
Mattel's
is
thinking
about
what
are
the
possible
options?
I
just
wanted
to
give
a
heads
up
that.
B
E
B
E
A
And
then
on
comments,
I
think,
Mike,
Medel,
Co
I
had
a
question
about
I
open
an
issue
around.
How
do
we
get
like
the
best
practices
guides?
It
sounds
like
there's
some
existing
content
from
people
that
we
can
start
using
and
then
we
start
compiling
these
things
into
a
guide.
I
think
I
open
that
issue
under
some
delusion
that
I
had
more
time
and
but
we'll
see
what
kind
of
progress
gets
made
on
it.
B
A
A
D
A
I'm
not
sure
I'm
pronouncing
it
correctly
was
interested
in
doing
that.
I
know
that
I
think
it
was
Collin,
replied
or
maybe
it
was
what
is
it?
Jules,
Julian
yeah
Julian
had
said
hey
we
had
some
content
on
and
maybe
it
was
Mateus
had
some
content
that
he
had
written
people
to
commented
in
there
being
like
hey,
we
have
a
bunch
of
stuff
and
so
I
think
it's
just
a
question
of
like
going
through.
D
A
And
being
like
you
know,
is
it
current
and
then
is
it
structured
in
the
right
way,
and
you
know
like
where
does
it
land
which
I'm
doing
from
the
the
website
group
is
like
hey?
You
know
you
should
go
up
at
the
website
thing
and
see
what
can
be
done
there
like
in
terms
of
like
where
to
plug
in
I,
don't
know
where
it
necessarily
fits
in
terms
of
like
the
all
up
documentation,
I
think
what
I
was
thinking
is
that,
like,
if
I
was
like
hey
I
need
to
stand
up
a
heaven
service?
A
What
do
I
do
about
like
blogging
or
tracing,
or
you
know
like
monitoring
or
things
like
that?
It's
like,
where
do
I
go
to
kind
of
find
some
definitive.
You
know,
god.
These
are
the
things
right,
so,
but
anything
more
than
that
I
think
is.
Like
you
know,
anything
Moore's
is
TBD
so
like
in
terms
of
the
structure
or
things
like
that.
So
yeah
go
for
it
like
feel
and
power
to
you
know
whatever
it
is
that
you've
got
the
time
and
and
energy
to
do
so.
A
F
You
guys
can
give
me
finally
I'm
sorry
for
that
Oh,
oh
yeah!
Thank
you
so
much
that
was
really
helpful.
Michael
Dawson,
who
I
was
introduced
to
do
by
a
source,
pointed
me
towards
that
issue.
So
I
thought,
given
that
everyone
has
such
prolific
work
in
terms
of
putting
some
content
together
already,
maybe
I
changed,
give
it
a
first
pass
and
I'm
not
entirely
sure,
would
I
be
able
to
replicate
the
table
of
content
that
Mike
you
like,
but
I
can
try
to
cover
it
as
much
as
possible.
Yeah.