►
From YouTube: Diagnostics WG meeting 06-17-2020
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).
B
B
C
C
D
D
C
B
C
C
D
Yes,
I've
been
working
on
a
couple
things
really
basic
hoax.
There
was
an
easily
found
animals
are
handled
by
promise,
newbie
aids,
which
is
fixed
now
and
landed
in
the
AIDS,
and
we
have
the
cherry
picker
back,
commits
in
a
PR
right
now,
which
seems
double
approvals.
I
think
I
think
we
can
land
it
now,
so
that
that
should
fix
the
animals.
Actually,
it's
good
that.
D
D
Yeah
and
then
there's
another
PR
which
have
been
working
on
which
basically,
with
a
some
folks
currently
like
most
most
things,
are
triggered
through
the
internal
callback
scope,
which
creates
like
three
separate
entries
and
new
JavaScript
before
trigger
is
one
entry
in
the
narrative,
loop,
callback,
scope
and
then
it
calls
the
callback
itself
then
returns
to
call
my
stove,
and
then
it
calls
the
after.
So
you
have
like
repeated
back
and
forth
the
native
JavaScript
plan,
so
I
made
a
PR.
D
D
D
D
D
D
D
C
D
C
D
Yeah
so
most
locations
of
like
get
your
labs
asynchrony,
it's
all
small
enough.
You
can
just
grab
whatever
you're
doing
in
a
source.
The
problem
with
edibles
was
like:
did
some
language
III
syntax
right,
not
really
anywhere?
We
do
so.
We
have
to
fix
it
yeah,
but
it's
essentially
the
same
problem
just
the
place.
We
have.
C
Right
any
any
relation
to
like
I
mean
I
know
that
I've
seen
I
think
Anna
was
working
on
a
thread
pool.
Maybe
that's
not
related,
though,
but
like
there's
a
thread
pool
module.
Is
it
that
there's
a
couple
modules
that
if
we
got
the
right
changes
in
there,
it
would
cover
like
it'd,
be
a
good
way
to
say
hey
if
you
use
this
to
get
your
asynchronous
pools
or
whatever
you're
going
to
get
the
right
behavior.
B
B
A
C
E
E
A
So
probably
let
me
explain
the
diag
best
practice
agenda
is
originally
devised
for
agenda
items
that
come
in
the
diagnostic
best
practice
meetings
which
we
set
up,
but
last
week
I
transform
the
best
practice
agenda,
template
to
the
deep
dive
template
and
if
everything
goes,
smooth
I
guess
next
Monday
we
will
start
seeing
that
invite.
So,
ideally,
this
label
also
should
be
transformed
to
Diagnostics
deep
dive
agenda.
C
Cuz
they
they
have
to
be
matched
right,
like
I.
Think
like
I,
guess
it
depends
what
you
used.
I
didn't
look
to
see
if
you
change
that
in
the
templates,
but
if
the
templates
still
say
diagnosed
practices
agenda,
then
we
just
need
to
synchronize
changing
that
if
you
actually
changed
it
to
diag,
deep-dive
or
something
then
yeah.
This
tide
won't
work.
Okay,.
B
A
B
C
I
think
in
the
end
like
this
was
open
to
say:
should
we
use
EBP,
F
more
or
less
or
like
cuz,
there's
been
talks
of
removing
things
but
I
think
I
think
you
know
if
we,
if
they
actually
make
sense
as
part
of
the
the
best
practices,
then
that
would
motivate
that.
So
that's
a
good
way
to
to
drive
outside.
B
C
F
939,
the
previous
weeks,
so
we
have
a
meeting
we
have
and
many
concerns
will
be
about
the
dynamic
scope
of
the
async
hooks,
so
your
decoder
can
be
excluding
arbitrarily
between
host
and
New
Zealander
code.
So
there
are
security
concerns
that
the
to
animation,
so
I'm
kind
of
working
and
under
a
time
to
adjust
the
various
paths
the
takes,
and
maybe
we
can
need
I
can't.
B
C
F
I
can't
sure
nice
cool.
Can
you
see
me?
Can
you
see
my
screen?
Oh
yeah?
Yes,
my
first
started
well
that
we
can
reduce
the
singles
DiCaprio,
who
came
to
the
lab
stack
old
resources.
So
it's
good
if
we
are
I
mean
trying
to
restrict
listening
of
the
events
so
kind
and
I'm
only
scope
to
changes
which
is
so
kind
in
the
new
proposal.
Maybe
we
can
and.
F
That'll
be
the
name.
Global
storage
might
be
confusing
things
that,
since
there
are
similar
to
lock
story
so
the
store,
maybe
I,
have
renamed
the
similar
story
to
a
local
to
reflect
that
have
no
relating
to
a
local
storage
so
and
the
changes
I
made
during
the
last
few
works.
I'll
remove
the
single
Oaks
resting
hooks
from
the
completely
the.
F
Economy,
the
dynamic
scope
of
the
sim
coast
in
the
language
of
packs,
so
you
know
guys
we
can
still
have
I
think
pasted
hopes
for
the
no
drip,
no
jazz
at
times,
which
is
okay
and
we
can
have
a
since
restricting
version
of
local
in
the
language,
language
implementation.
So
in
the
language,
jazz
spirit
and
drinks,
they
can.
F
F
C
Okay,
so
so
it's
it
kind
of
makes
sense
like
we
introduced
async
local
storage
as
an
idea
of
reducing
the
surface
area,
to
make
it
potentially
easier
to
to
be
comfortable.
We
weren't
exposing
too
much.
It
sounds
like
the
discussion
at
tc39
was
aligned
with
that,
like
they,
they
were
okay
with
the
async
local
part,
but
the
hooks
themselves
where
the
was
concerned.
C
F
I
think
the
idea
on
the
meeting
similar
to
that
is
that
I
think
locally,
interesting
and
very
critical
to
the
language
be
a
part
of
the
language
and
by
the
stuff.
We
should
suffice.
So
it's
in
quotes
concern
and
there
might
be
it
better,
be
left
out
from
the
language
and
we
can
have
it
any
host
platforms
like
not
just.
C
F
F
G
F
B
B
A
C
G
H
C
E
B
A
The
only
thing
is
report
is
now
stable
and
we
did
not
have
any
issues
reported
from
the
users
that
is
externally.
This
version
kind
of
concern
is
from
within
from
the
collaborators,
so
I
don't
know
what
that
actually
means,
but
it
should
be
an
internal
concern
and
it
could
be
scoped
from
that
point
of
view
right.
C
B
B
A
D
A
B
C
B
B
B
B
A
One
thing
which
I
remember
right
now
is:
there
was
a
end
user
feedback.
Sorry,
there
was
a
contributor
feedback
that
James
has
collected
from
the
projects
project,
which
has
reference
to
the
user
experience
with
diagnostic
capabilities.
I
didn't
read
too
much
details
about
that,
but
if
I
recollect
correctly,
it
was
not
very
good.
So
probably
it's
worthwhile
as
a
working
group
to
sit
together
and
having
a
look
at
that
and
discuss.