►
From YouTube: Node.js Diagnostics WG Call - 2018-11-14
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
So
yeah
so
quick
recap:
I!
Guess
we
already,
so
the
timing
of
the
meeting
is
moved
to
9:30
the
issue
to
11,
which
is
the
best
practices
guide.
We're
going
to
wait
for
another
week,
try
to
get
a
meeting
scheduled,
try
and
sort
of
get
some
clarity
on
the
table
of
contents
and
next
steps
forward
and
prioritization.
A
A
Formalization
is
where
we're
at
now,
Calvin
I
saw
your
thing:
I've
been
kind
of
buried
with
some
other
stuff
I'm
kind
of
reading,
through
what
you
wrote
and
I
will
try
and
respond
to
that,
and
on
that,
where
you
added
that
issue
on
and
I
think,
there's
got
a
call
scheduled
with
some
of
the
v8
folks
on
this
stuff
elite
out.
I
could
write
and
explain
her
and
I
need
to
sort
of
look
at
some
of
the
previous
Doc's
see
how
much
time
it's
been.
A
A
B
You
had
no
other
updates
there.
What,
if
there's
anything
I
can
do
to
I
guess
you
know
she
really
asked
questions
about
my
row
for
everyone
else.
The
discussions
going
on
in
Natalie,
Wolf's
repo,
like
hurricane,
you
know
by
invitation.
So
that's
where
this
got
just
taking
place
in
case.
Anyone
else
is
wondering
yeah.
A
A
Reaction
is
in
cute
right,
I
mean
there's
various
precise
places
in
the
spec,
where
that
happens
on
and
that's
kind
of
what
I
like
about
it
like
you,
don't
need
to
think
too
hard
about
you're,
just
like
okay,
great
and
sort
of
have
this
clear
definition,
and
indeed
you're
right
or
wrong
right.
What.
B
A
A
Oddly
but
I,
think
people
are
looking
at
this
ready
context
and
they're
kind
of
conflating
two
different
things
on
it
and
one
is
sort
of
like
what
is
the
context
where
a
promise
reaction
is
in
q3
and
the
promise
has
already
resolved,
and
it's
just
the
current
context,
and
if
the
promise
is
not
resolved
and
it's
when
that's
that
promise
that
you're
chaining
on
to
gets
resolved
and
that's
distinct
from
like
hey
I,
want
to
know.
A
A
And
there
I
think
there's
different
reasons
why
people
want
one
versus
the
other,
and
you
know
I,
think
you
know,
having
just
just
being
able
to
be
explicitly
clarify
that
distinction,
I
think
is,
is
useful
and
the
you
know
I
think.
In
both
cases
you
can
have
very
precise
language
at
the
spec
level.
That
gives
you
this
ready
context
versus
this.
Where
was
a
promise
resolved
context,
and-
and
you
can
do
that
and
in
a
very
kind
of
clear
and
targeted
way
in
the
language
of
the
spec,
but
they
do
end
up
being
distinct.
A
Sometimes
they
are
the
same,
sometimes
they're
not
depending
on
what
you
want
to
do.
You
may
want
one
versus
the
other.
I
do
have
some
concerns.
I
think
that
when
you
start
getting
into
like
this
notion
of
what's
the
context
where
the
promise
was
resolved,
you
start
getting
into
like
a
lot
of
other
questions
related
to
promises.
It's
like
well
yeah
great,
but
maybe
what
I
want
to
know
the
value
where
promise
was
resolved,
maybe
I
want
to
know
like
my
promise
was
resolved
and
it
wasn't
in
a
pending
state.
A
You
know
Laurie
always
rejected
that
you
know
like
after
it
was
resolved.
Then
there's
all
these
other
questions
and
what
I
don't
really
have
a
clear
sense
of
is:
are
we
just
kind
of
slipping
down
this
path
of
being
able
to
sort
of
answer?
These
very
in-depth
questions
about
the
you
know
the
promise
graph
effectively
right,
and
is
this
just
kind
of
like
a
little
baby
step
along
that?
A
B
A
No
problem,
sorry
I've
been
a
delay.
It's
okay,
so
number
84
trace
events,
I,
don't
know.
If
there's
any
update
here.