►
From YouTube: Node.js Diagnostics WG meeting April 21 2021
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
A
C
C
So
the
pr
has
been
updated.
It's
following
some
kind
of
obscure
tests
that
I'm
not
entirely
sure
what
the
tests
are
actually
testing.
C
So
I'm
trying
to
find
some
time
to
look
at
that
and
figure
out
if
it's
actually
like
an
issue
or
if
the
tests
are
not
correct
anymore
or
what,
because,
with
the
new
promisebook
api,
it
goes
from
being
isolate
scoped
to
context
scoped,
and
this
test
is
like
about
worker
thread
behavior,
which,
as
far
as
I
know
like,
they
should
have
their
own
unique
contexts.
B
C
I
I
I'm
not
sure
exactly
so
something
in
the
pierre
is
making
that
okay,
I'm
not
sure
what
yet
I
haven't
really
had
any
time
to
look
into
it.
Yet
just
saw
it
blow
up
on
the
ci
last
night.
C
B
B
Just
as
a
side
note,
we
did
a
survey,
which
is,
I
think,
what
you're
planning
we're
planning
for
this,
like
the
blog
post
and
then
like
possibly
a
survey,
and
we
did
manage
to
get
like
2500
responses
on
that
last
survey.
So
this
might
be
a
bit
more
specific,
but
it
does
does
show
that
we
can
get.
You
know
a
good
good,
some
good
input
in
some
cases.
B
Oh
sorry,
I
mean
it
was
an
unrelated
survey.
It
was
a
survey
on
the
next
10
effort-
oh
okay,
right
so,
but
I
I
just
was
saying
that,
like
we're
in
this
issue,
we're
talking
about
doing
a
survey
getting
more
input
so
just
relating
that
we
were
successful
in
another
case
of
doing
that.
A
C
I
I
just
haven't
had
the
time
to
get
to
it
and
really
think
about
it.
Much
okay,
yeah.
The
general
plan
was
write,
some
sort
of
blog
post
that
basically
points
to
the
issue
and
says
like
we're,
trying
to
figure
out
like
what
people
use.
C
Asynch
hopes
for
that
can't
be
done
by
async
local
storage
to
hopefully
try
to
eliminate
the
need
for
using
ac
hooks
directly
as
much
as
possible,
since
it
seems
to
be
kind
of
stuck
in
experimental
limbo
forever,
just
due
to
exposing
internals
and
yeah
all
that,
if
we
can
provide
some
higher
level
apis,
hopefully
maybe
someday
we'll
have
enough
that
we
don't
actually
need
to
expose
asynchronous
at
all,
just
make
it
a
private
api.
A
One
of
the
known
advantage
with
the
survey
is
the
fact
that
your
your
questions
can
be
customized
in
such
an
another.
The
user
can
actually
select
one
of
many
options,
so
they
don't
need
to
really
break
their
head
too
much
about
thinking
about
use
case
or
creating
opinions,
etc.
So
in
instead,
when
you
are
asking
a
question,
do
you
think
a
single
local
storage
can
be
used
in
this
particular
context
versus
this
one
option?
Abcd
user
has
a
better,
better
tendency
to
answer,
as
opposed
to
you
know,
providing
a
fresh
answer.
A
C
I
I
I
think
in
that,
like
in
that
case,
like,
if
you're,
if
you're,
making
a
survey
like
you're,
usually
going
into
it's
like
providing
a
handful
of
like
possible
use
cases
you've
already
thought
of,
whereas
I
think
we're
kind
of
trying
to
ask
the
community
to
give
us
stuff.
We
haven't
already
thought
of.