►
From YouTube: Node.js Diagnostics WG - 2018-11-28
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
A
The
on
the
agenda
issue
number
211,
the
Diagnostics
best
practices
guide,
you're,
just
saying
that
trying
to
get
a
time
schedule
where
people
can
talk
about
that
Gary's
try
to
do
that
last
week
and
I
didn't
get
a
lot
of
response.
So
last
week
was
a
holiday
week
in
the
US.
So
we
should
probably
try
that
again.
We
should
do
that.
I,
don't
think,
there's
any
update
on
the
deep
dive
stuff
that
we
had
standing
on
the
agenda.
A
B
The
tiers
yeah,
no
I,
there's
nothing
on
that
update.
Sorry,
async
hooks.
A
C
C
C
Class
is
tied
so
instead
of
the
HTTP
parser,
and
that
will
fix
all
of
things,
so
it
seems
we
have
a
way
forward
in
that
regard,
and
if
there
are
any
questions
should
probably
ask
mathias.
We
is
mainly
the
person
driving
this
at
this
point
in
time,
I
was
just
keeping
tabs
on
on
the
issues.
That's
it.
Okay,.
A
A
So
async
context,
formalization
diagnostic
support,
I
there's
been
a
call
that
we
had
scheduled
with
the
v18
to
talk
about
sort
of
where
this
stuff
fits
conceptually
and
start
talking
about
you
know:
does
this
kind
of
make
sense?
Do
you
see
any
things
that
would
block
this
at
a
spec
level
on
and
start
trying
to
get
to
some
more
detailed
text
and
I
was
asked
to
either
write
an
explainer
or
on
write.
A
Start
writing
spec
text
I,
don't
want
to
I
want
to
avoid
writing
the
spec
text
as
much
as
possible
and
I
need
to
start
writing
some,
some
of
this
explainers
stuff
and
I'm,
trying
to
find
the
time
to
do
that
that
I
will
share
that
would
probably
get
PRD
to
the
Diagnostics.
We
go.
I
have
another
PR
to
read
me
from
earlier
this
year.
Some
of
the
concepts
who
think
we've
been
able
to
simplify
some
thing,
so
I
need
to
go
back
and
see
if
that
da
yeah
there's
a
purpose
so.
A
A
I
think
that
that
is
an
open
question,
I
think
there's
some
specific
areas,
I
think
in
the
spec,
where
I'm
probably
able
to
point
at
it
and
be
like
this
stuff
needs.
We
need
updates
here.
We
need
update
here,
and
you
know
it's
to
actually
what
that
text
is
that
I
want
to
get
to
that
level
of
detail
just.
D
A
D
That's
exactly
what
I
had
in
mind
essentially
like.
Whenever
you
talk
about
asking
context,
you
would
have
certain
points
in
this
bag
saying:
okay,
here's
what
certain
operations
in
the
context
of
s
in
context
organization
would
occur
and
whether,
like
whatever
hooks
into
that,
is
written
down
in
this
bag
or
outside,
would
not
matter
all
that
much
yeah,
it
would
be
great
to
you
know,
have
the
relation
between
the
spec
and
the
proposal.
Okay,.
A
On
yeah,
let
me
work
on
that.
I
like
I,
want
to
try
and
keep
the
dock
I
think
as
succinct
and
minimal
as
I
can,
but
not
have
it
be
too
vague
that
it
interferes
with
causes,
confusion
right
and
I,
don't
I,
don't
know
when
I'm
hoping
like
I
was
hoping
last
week
to
do
it,
but
I
was
on
vacation
and
I
ended
up
doing
things
like
vacuuming
out
the
vents
at
my
bathroom,
which
they
were
her
desk.
The
way
some.
D
C
A
D
A
A
A
Yeah,
it's
good
to
hear
that
there's,
like
general
sort
of
consensus
that
the
spec
needs
update
it
and
we
can
go
from
there.
So
the
trace
event
stuffs
issue,
number
84,
I,
don't
know!
If
there's
any
update
there,
I
don't
know.
If
anybody
has
any
update,
a
leave
is
usually
the
ones
providing
updates
on
that
joined
us.
I,
I.
B
D
A
D
Question
was
whether
we
could
move
it
a
week
later,
because
the
Monday
after
is
in
Munich
there's
this
Jay
s
Congress,
which
is
a
middle-sized
medium-sized
conference
on
JavaScript
I,
try
to
do
that
and
ask
around
whether
it
was
possible,
but
the
venue
I
booked
is
already
reserved
for
those
dates.
Okay,.
A
A
C
A
C
C
A
Changes
to
the
debug
protocol
to
support
some
of
this
stuff
and
node
and
I
was
gonna
tag,
his
issue
for
he
with
the
diag
addenda.
Just
so
we
can
start
pulsing
on
it
and
but
I
don't
have
permissions
actually
in
the
node
repository
to
tag
the
thing
on,
so
somebody
could
do
that.
For
me,
it's
this
should
be
twenty
four
six,
eight
seven.
A
E
A
A
Yeah,
if
you
tag
it
with
the
agenda,
I
think
that'd
be
great,
we'll
just
keep
an
eye
on
and
I
promised
Rob.
You
open
the
issue
that
I'd
sort
of
try
and
make
the
right
connections
between
him
and
people
inside
of
node
and
potentially
in
v8,
to
sort
of
help
him
out,
and
you
understand
the
right
thing
to
happen.
C
Issue
of
adding
network
traction
support
to
that,
like
the
dev
tools
inspector
in
the
inspecting
Chrome,
and
we
might
considering
that
we
don't
have
much
time
we
might
be
looking
for
asking
for
volunteers
in
a
more
public
way
to
do
that
work.
It's
a
significant
chunk
of
work
and
requires
different
of
skill
set.
So.
C
C
A
A
That's
I
think
everything
on
the
agenda.
I,
don't
know
if
anyone
has
anything
else,
I
don't
know.
If
we
want
to
wait
for
a
few
minutes.
People
are
gonna
start
trickling
Indiana,
because
it's
10:00
and
I
anticipate
because
I
was
totally
like
if
I
hadn't
been
looking
at
my
email
precisely
when
I
got
the
notification
from
from
yang
that
hey.
Why
isn't
this
happening
now?
I
would
have
completely
missed
this.
So
I.