►
From YouTube: 2020-09-09 JavaScript SIG
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
A
A
A
B
B
B
B
B
It
was
a
holiday
monday,
can
imagine
people
may
be
on
vacation.
This
is
also
the
first
week
of
school
for
most
kids
in
the.
C
B
B
All
right:
well,
it's
been
seven
minutes,
I
think
we'll
just
start
and
if
people
show
up
they
show
up.
B
A
B
D
Yeah,
but
I
believe
there
were,
there
was
some
plan
to
migrate
to
github
action,
but
I'm
not
sure
where
it's
standing
right
now
and
I
think
some
of
the
sdk
are
switching
already.
And
there
was
some
someone
opening
an
issue
saying
that
they
might
try
to
migrate
some
stuff
to
to
to
get
the
version.
But
maybe
that's
related.
B
Yeah,
I
know
that
there
was
an
intern
that
was
gonna,
try
to
migrate
us
to
github
actions,
and
he
did
some
things.
But
you
know
most
of
the
the
bulk
of
the
tests
are
still
on
circle.
Ci
I
mean
our
tests
won't
even
run
on
the
regular
on
the
free
tier,
because
the
lerna
bootstrap
is
too
too
heavy.
A
What
do
you
mean
like
nice,
like
it's
too
heavy?
I
mean
it
won't
work
on
on
this
middle
class.
B
It
won't
run
on
the
regular
resource
class
because
it
runs
out
of
memory,
while
it's
doing
the
bootstrap.
A
We
can
limit
this
one
and
there
is
a
pattern
for
that.
So
we
can
limit
the
memory.
B
Yeah,
so
we
we
did
that
in
the
past.
That's
why
we
originally
switched
to
the
large
resource
class,
because
we
tried
to
limit
the
memory,
but
then
it
was
taking
like
20
minutes
to
run
the
build.
A
D
I
don't
know
it's
a
specific
update
on
the
on
the
community
issues
that
is
linked
inside
ours.
B
I
don't
remember
exactly
where
it
is
doesn't
matter,
but
it
seems
like
we
should
switch
to
github
actions,
but
maybe
we
should
also
consider
maybe
looking
at
learn
alternatives
like
nx
or
something
like
that
or
possibly
splitting
into
a
third
repo,
so
that
we
would
have
fewer
packages
in
the
learner
mono
repo
to
build.
I'm
not
entirely
sure
how
that
would
work.
D
Well,
on
the
I
think,
open
having
a
flip
would
be
quite
problematic
because
I've,
I
think
that
already
having
a
second
one,
is
quite
hard
to
get
reviews
on
the
console
one,
because
people
are
not
just
checking
as
as
a
main
one,
so
yeah
yeah.
That
will
be
maybe
start
to
get
complicated
about
that
and.
D
Yeah
yeah,
but
about
nx
and
lana,
I'm
not
sure.
If,
if
we
could
change
the
online,
this
will
be
better
because
lana
just
uninstalled
the
bare
minimum.
I
think
if
you
scope
the
installation
so
even
with
tool
like
nx,
I
believe
it
will
be
the
same
issues
if
you
want
to
to
bootstrap
everything.
It
could
take
question
time.
If
you
don't
have
a
good
hardware,
I'm
not
sure
it
will
be
really
well.
D
Well
about
the
cia,
we
can
try
this,
but
I
think
the
issues
was
for
for
one
contributor,
that
was
that
didn't
have
a
good
enough
hardware
and
the
installation
on
his
laptop
was
like
really
slow
yeah,
and
we
can't
really
try
to
fix
it
without
changing
learn.
I
think.
D
We
could
we
could
try
to
change
tools,
but
I'm
not
sure
it
will
be
really
worth
the
pain
to
me
rate,
because
lana
is
quite
known
for
everyone.
A
A
B
A
Yeah,
but
I
mean
if
you,
if
you
want
modified
a
couple
of
packages,
you
need
to
have
them
running
anyway,
right
so
instead
of
just
npm
style
and
in
the
main
reaper.
You
just
have
to
go
to
to
your
viewpoint,
because
if
someone
has
like
not
our
laptop
powerful
enough
to
even
do
the
npm
install,
then
I
don't
know
what
can
we
do
about
this.
B
Right,
but
if,
if
you
want
to
make
a
change
in,
for
instance,
tracing
but
trade,
but
core
has
updated
with
some,
you
know
breaking
change,
then
the
current
master
of
tracing
will
depend
on
that
updated
core,
not
on
the
released
one.
So
if
you
run
npm
install
in
the
tracing
repo,
it
will
download
the
npm
version
of
core
which
is
not
compatible.
A
B
B
Okay?
Well,
this
issue
aside,
I
I
think
we
should
probably
stick
with
lerna
and
maybe
document
you
know
for
in
the
contributing
markdown
or
something
what
to
do.
If
my
machine
is
too
slow
to
run,
learn
like
some
steps,
you
can
do
like
the
bootstrapping,
with
just
a
scope
or
something
like
that.
B
D
Maybe
we
can
ping
the
the
guy
that
opened
the
issue
to
me
great,
because
I
think
he
offered
to
try
to
migrate
for
us
playing
this
guy
yeah
this
one
at
the
end
of
the
of
the
issues
he
he
offered
to
do
it.
I
think,
if
I'm
understanding
correctly
what
he
said.
B
A
B
Okay,
I'll
I'll
look
at
flags
like
that,
and
I
I
don't
think
because
that's
with
like
a
running
node,
I
think
that
the
issue
was
it's
trying
to
download
too
many
packages.
B
B
B
I
think
this
is
good
enough
for
now,
though,
we
can
try
a
couple
of
different
things
and
if
it
doesn't
work,
we
can
talk
about
it
again.
A
But
our
kodrip
still
has
the
normal
plan.
Here
still
has
what
I
mean.
We
don't
have
a
free
tire
on
like
kodu
people,
just
in
the
country.
B
Yeah,
so
that's
I
asked
in
the
maintainers
channel
here
said:
I'm
getting
these
test
failures.
I
haven't
gotten
a
response,
yet
it's
possible
that
it's
just
our
repository
is
not
like
signed
up
for
the
account
or
something
like
that.
So
I
I'm
not
entirely
sure.
Maybe
we
should
even
just
rerun
this
and
see
if
it
yeah
no.
F
B
Downgrading
circle
or
anything
like
that,
you
know,
I
know
that
they
want
people
to
move
to
actions
over
time,
but
I
didn't
think
that
there
was
that
they
were
had
any
target
time
to
actually
shut
off.
The
circle
account.
B
People,
I
think,
actually
we
did
both
since
then
right,
because
we
did
11
and
we
did
10
for
the
control.
B
Okay,
I
did
also
merge
a
pr
that
tests
node
14
on
contrib
now
and
actually
that
pr
worked
just
fine.
F
B
B
I
did
also
update
the
bug
template
to
just
add.
Please
provide
code
to
use
to
set
up
the
sdk
like
we
talked
about
last
week,
because
a
lot
of
the
bugs
we
get
are
just
from
incorrect
setup.
B
I
did
want
to
talk
about
this
issue
here,
so
this,
apparently
the
zone
contact
manager
doesn't
work
if
your
compilation
target
is
for
es
2017,
something
to
do
with
zone.js,
not
properly
supporting
a
single
weight.
Are
you
aware
of
this
issue
bart?
Have
you
looked
at
this.
D
Well,
I
mean
tracking
the
tracking
with
asynchronous.
Will
act
currently
never
work
in
the
browser,
because
the
api
that
we
use
in
njs
isn't
exposed
on
the
browser.
So
I'm
not
sure
the
linked
the
link
with
the
version
that
we
target.
When
we
build
the
package
I
mean
it
will
never
work.
I
think
the
weight
will
in
the
mozart
will
never
work
with
zone
js,
and
I
think
that
made
it
really
clear
that,
without
without
any.
B
So
what
what
should
we
do
about
this?
I
mean
this
user
said
that
essentially
they
had
to
use
explicit
context
propagation
and
for
now
that's
what
he's
doing,
but
he
suggested
that
we
drop
implicit
context
propagation,
which
I
do
not
want
to
do.
I
don't
think
we
would
even
be
allowed
to
do
that.
According
to
this
fact,.
D
I'm
sorry:
what
was
that
there's?
No
gingers
is
the
only
implementation
that
that
works
quite
nicely,
but
they
they
don't
support
us
in
kuwait.
So
I
think
I
I
think
I
got
the
link
with
the
versions
is
because,
when
you
compile
to
to
the
version
of
dimension,
you
should
be
able
to
use
that
incognitively,
so
they
are
transpiled
with
a
single
weight
and
so
the
the
contact
management
break,
because
the
js
doesn't
support
async
rates
and
taxes.
B
D
F
A
B
B
D
I
can't
find
back
because
someone
someone
is
trying
to
bring
back
this
to
the
to
the
javascript
tst,
to
have
a
specification
directly
into
javascript
for
conte
for
the
context
propagation
with
I
think
awaits,
but
I
think
it's
still
a
proposal,
I'm
trying
to
find
it
and
actually
they
are
the
support
for
the.
D
Them
yes,
this
one
is
the
issue
from
it's
linked
to
another.
Yes,
but
it's
pretty
much
the
same
as
the.
D
It
yeah
yeah
yeah
me
I
I'm
stealing,
because
there
are
issues
like
twice
a
proposal
for
for
for
the
sunrise
mechanism,
so
yeah,
I
think
if
it
will
be
ever
accepted,
it
will
be
minimum
for
two
years
or
maybe
more.
A
D
But
that
there
is
no
api
exposed
on
chrome
to
to
get
the
different
contacts
and
to
get
pretty
much
what
we
have
in
address,
which
lasting
books.
There
is
no
api
like
this,
so
that's
why
they
are
blocked
for
the
zanjs.
It's
just
that
it's
not
possible
currently
on
the
browser.
So
even
if
we,
if
we
try
for
everyone,
something
we'll
just
add
the
symbol
that
they
add
and
the
same
all.
B
Okay,
I
didn't
completely
understand
that
your
your
connection
is
breaking
up
a
little
bit
absolutely,
but
I
think
for
now
we
really
don't
have
any
action
item
on
this.
You
know
it
at
the
very
least.
F
B
To
wait
for
this,
you
know
for
a
couple
of
years
before
there's
any
support
so
for
now,
there's
really
nothing.
We
can
do.
B
So
I
think
for
now
this
is
a
documentation
issue
and
hopefully
the
situation
improves
in
the
future
and
that's
really
all
we
can
say.
F
B
A
D
B
This
browser
supports
this
zones
proposal.
D
Yeah
open
it,
that's
this
one
did
no,
no
electron,
no.
D
There
wasn't
support,
I
think,
awaits,
but
the
missing
part
is
the
mechanism
that
allow
us
to
to
get
oops
on
the
creation
of
those
contacts
to
be
able
to
get
and
set
the
context
quite
clear
when
it's
created
like
like
it's
done,
energized,
we
have
articles,
there's
no
api
to
do
it,
even
though
I
think
it
works
in
buzzer.
Of
course,.
F
B
This
issue
valentin,
I
know
you've
been
active
on
this
one
yeah
yeah.
Do
you.
D
B
What
do
you
recommend
we
do
here?
This
is,
there's
been
a
lot.
D
Everyone
agree
that
it's
not
really
helpful
to
get
traced
like
this,
but
what
I
was
saying
is
that
challenging
this
behavior
is
possible
for
experts.
We
could
make
a
fix,
but
generally.
D
B
B
G
D
B
B
D
That's
the
thing
I'm
not
sure,
because
if
we
do
that
for
express,
we
might
do
that
for
happy
or
any
framework
that
that
work
the
same
way
because
that's
that's
the
intended
behavior,
and
so
you,
you
start
a
list
of
pre
or
plug-in
that
have
a
specific
implementation,
just
just
to
have
a
simpler,
a
simpler
link
between
spans
but
yeah.
You
sh
there's
no
limit
of
adding
new
plugin
in
that
list,
and
I'm
I'm
afraid
to
just
to.
B
B
G
B
So
another
bug
opened
this
morning
that
I
saw
you
assigned
to
yourself:
do
you
have
an
idea
what
might
be
causing
this
or
anything.
D
D
B
Another,
so
this
was
an
old
issue,
but
I
saw
you
suggested.
We
enable
the
async
storage
contacts
manager
by
default.
I
know
when
we
originally
created
it.
I
said
I
didn't
want
to,
but
since
then,
we've
actually
been
using
it
internally
at
dynatrace
and
it's
been
working
well
for
us,
okay.
B
G
B
G
D
I
still
wouldn't
prefer
to
check
the
version,
because
I
believe
there
are
some
bugs
in
number
14
in
the
earlier
minors
that
we
could
avoid,
I'm
not
sure
which
one,
but
I
will
check
that
and
yeah.
I
think
I
think
actually
the
guys
that
implemented
the
I
think.
Storage
for
this
manager
was
the
guy
from
mineralics.
D
B
Yeah,
okay,
so
that
should
I
assign
this
to
you
then.
D
D
F
G
B
So
I
have
this
synchronous
sdk
pr,
it's
been
open
for
a
while
now
I
know
that
everybody
is
aware
of
it.
It's
ready
to
be
reviewed
and
merged
in
my
opinion,
but
there's
a
test.
That's
breaking
in
the
browser
bart.
I
mentioned
you
on
this,
but
you
haven't
responded.
I
know
it's
only
been
a
day,
but
have
you
have
you
looked
at
this
at
all.
B
Not
really,
okay,
so
I'll
explain
what
the
issue
is
here.
The
original
test
did
not
have
the
done
callback,
but
it
does
asynchronous
work
and
it
has
assertions
here
so
the
problem
is
these
assertions
never
run
in
the
original
one,
but
because
there's
no
done
callback,
the
test
is
just
successful.
B
B
Shut
down,
notifier
never
runs
in
the
tests.
The
these,
it
literally
never
runs
and
all
of
the
tests
pass
anyways
because
the
assertions
just
don't
run
but
they're
missing
done.
Callbacks.
B
Okay,
I'm
on
the
wrong
branch
right
now,
and
I
don't
want
you
guys
to
have
to
wait
for
my
bootstrap
holder
on
the
call
but
I'll
try
this
if
it
doesn't
work
I'll,
create
an
issue
and
assign
it
to
you.
If
that's
okay,.
A
Yeah
go
ahead,
I
mean
if
this
doesn't,
if
it
wasn't
working
previously,
then
you
know
it.
It
means
you
can
probably
ignore
it
and
just
create
an
issue
here.
B
B
A
B
So
I'll
work
on
that
and
then
I
just
wanted
to
have
a
quick
check
in
on
what
you
know.
We
went
and
assigned
ga
issues
last
time,
so
this
is
sort
of
the
status
of
those
ga
issues
that
were
assigned
to
me.
B
I
have
a
pr
open
for
the
span
attribute
spec
compliance
once
that
merges.
I
will
apply
that
to
the
resources,
also
since
they're
supposed
to
share
the
same
definition
and
then,
after
that
I'll
be
working
on
the
propagator
issues.
B
Has
anyone
else
had
time
to
work
on
the
issues
that
we
talked
about
last
week?
Or
would
anyone
like
to
to
give
us
a
quick
update
or
not.
B
Okay,
let
me
open
openness.
C
I
have
the
the
global
error
handler
and
I
have
a
global
error
handler
and
I've
kind
of
updated
the
collector
exporter
to
use
it.
I
could
probably
open
like
a
draft
pr
to
get
some
feedback
on
it.
C
Yeah,
like
I've,
been
pretty
busy,
but
I
think
the
rest
is
to
just
like
you
know
figure
out
if,
if,
if
we
like
kind
of
the
setup
and
then
just
update
the
other
components
to
use
the
the
global
error
handler,
it
basically
kind
of
replaces
all
of
the
logger.error
calls
in
most
of
the
kind
of
sdk
components.
C
B
Yeah
and
that's
sort
of,
I
think,
the
way
it's
supposed
to
work
and
then
by
default
I
think
it
just
logs
right.
Isn't
that
what
the
spec
says
yeah.
C
C
C
I
think
this
would
be
possible,
but
yeah
it
would
take.
It
would
be
like
a.
It
would
be
one
more
line
of
setup
for
somebody
to
to
set
this
up,
because
I
guess,
like
the
other
problem,
is
that
there's
not
you
know,
there's
not
really
like
a
place
to
get
at
like
a
global
logger.
It's
kind
of
like
each
sub-component
has
a
logger
reference
and
it's
up
to
somebody
to
somehow
kind
of
assign
it
the
sdk
package
kind
of
helps.
You
get
the
same.
You
know
logger
everywhere,
but
yeah.
That's
that's
one
complication.
C
C
I
guess
maybe
it's
not
completely
crappy,
but
it's
not
amazing
version
of
like
node
inspect
if
you're
familiar
with
that
yeah
because,
like
I
wanted
something
that
would
work
both
in
browser
and
node
and
I
didn't
know
like
a
browser
equivalent
to
log
which.
C
Yeah
to
log
an
error
object
like
one
yeah,
like
one
thing
that
I
basically
the
way
I'm
doing
that
right
now
is
like
error
objects.
They
seem
to
have
non-innumerable
properties.
Like
name
name
seems
to
be
not
enumerable.
I
figured
if
message
is
always
so
you
kind
of
have
to
like
walk
up
the
prototype
chain
and
flatten
flatten
the
object
and
then
log
it.
B
One
thing
we
could
do
is
expose
a
function
in
like
core
or
something
like
that
that
stringifies
errors
and
then
have
the
global
error
handler.
Always
we
have
it
either.
You
know
simplify
the
type,
have
it
only
accept
a
string
or
only
accept
error
objects,
and
then
we
know
what
the
shape
of
the
object
is
like,
and
we
don't
have
to
enumerate
everything
so
yeah.
C
Like
I,
actually
I
had
this
thing
in
core
called
stringify
exception
and
I
spent
a
lot
of
time
just
kind
of
messing
around
with
it,
and
I've
done
a
few
different
implementations.
So
one
of
them
I
did
do
was
we
have
those
exception
enums.
So
I
just
like
enumerated
those
properties
like
the
full
set
of
properties
that
could
be
in
our
enums,
and
that
worked
all
right.
I
noticed
that
some
exceptions.
C
Well,
the
exception.
Genomes
came
after
some
of
the
exceptions
or
some
of
the
errors.
I
guess
in
the
rest
of
the
and
the
rest
of
the
components
and
some
of
them
have
more
information
on
them,
so
that
what
do
you
mean
by
exception?
Enum,
I'm
not
sure
what
you're
talking
about
so
in
api.
Now
there
are
maybe
like
four
three
or
four
different
exceptions:
there's
one
that's
called
like
exception
with
message
exception,
with
code
exception
with
name:
oh
yeah.
C
No,
I
know
what
you're
talking
about
so
that
is
technically
the
type
that
stringify
exception,
expects.
C
Okay
and
but
like
yeah,
so
that's
the
other
kind
of
weird
thing
is
that
we
kind
of
have
these
errors
in
the
rest
of
the
application
that
do
like
kind
of
by
typing
implement
the
right
thing.
Some
of
them
had
to
be
massaged
a
little
bit,
but
I
guess
that's.
The
other
complication
with
this
global
error
handler
is
what
is
the
actual
type
of
thing
that
it
should
accept.
B
C
Okay,
that's
a
little
different
than
what
I
currently
have,
but.
C
C
Right
now,
and
I
guess
that's
kind
of
one
of
the
issues
is
that
a
lot
of
the
components
aren't
actually
using
errors
as
their
as
their
errors.
B
Yeah,
I
think
a
draft
pr
is
probably
helpful.
You
know
it.
It
sounds
like
there's
been
sort
of
un
inconsistent
error
handling
throughout
the
project,
which
makes
your
job
a
little
bit
more
difficult,
but
in
a
lot
of
ways
that's
what
this
is
attempting
to
resolve
so
not
unexpected.
I
guess.
C
Yeah
yeah,
I
think,
there's
a
few
rough
edges
I
think
generally.
The
approach
is
probably
on
the
right
track,
but
I
think
it
would
be
good
to
get
some
feedback
because
it's
kind
of
time
consuming
like
updating
all
these
components
to
use
this.
I
just
want
if
I
know
that
what
I'm
doing
there
is
what
we
want
to
do,
that
will
be
helpful
because
it's
kind
of
you
know
introduce
the
whole
error
handler
and
then
spend
an
hour
fixing
tests
and
and
things
of
that
nature
for
for
where
you
introduced
it.
B
Right,
okay,
yeah,
so
I
guess,
whenever
you
get
a
time
a
draft
pr
would
be
helpful,
but
you
know
no
no
rush.
If
it's
not
ready,
then
there's
no
reason
to
whenever
whenever
you
feel
like
you're
ready,
but.
C
Yeah
no,
like
I
feel
like
I
have
enough
to
put
up
I'll,
probably
make
one
or
two
changes
so
I'll.
Try
to
do
that
tonight.
Sometime.
B
Okay,
I
guess
the
only
other
one
for
people
that
are
here
is
this
propagating
with
only
the
api
valentine.
Have
you
had
any
time
to
look
at
this
or
not.
D
No,
it's
not
not
this
weekend,
maybe
the
next.
I
should
have
the
techniques.
B
Okay,
well,
I
guess
that's
it
for
the
day,
then
anyone
have
anything
that
they
want
to
bring
up
before
we
go.
B
All
right:
well,
everybody
have
a
good
week
and
I'll
talk
to
you
next.