►
From YouTube: 2021-09-08 meeting
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
A
B
A
B
I'm
not
from
canada,
I
mean
I'm
in
europe
and
no
one
here
does
most.
A
Of
the
world
as
a
labor
day
and
in
may
right.
C
B
D
A
I'm
not
sure
how
many
people
who
are
joining
today.
I
know
a
lot
of
people
are
on
vacation
this
week.
I
see
a
couple
of
new
people
on
the
call,
though,
ran
and
diana
welcome.
E
Oh
yes,
of
course,
I'm
diana
I'm
a
new
member
of
the
node.js
agent
team,
and
so
I
may
maintain
the
node.js
software
agent,
my
first
timer,
oh,
oh,
it's
new
relic!
Oh
I'm,
sorry,
yeah,
no
problem.
A
I
guess
we
should
get
started.
I
don't
know
if
valentine's
gonna
join
or
not,
but.
A
So
first
thing
I
know
it
has
been
a
slow
week
over
the
last
week
or
so
because
of
labor
day.
So
I
just
wanted
to
give
my
apologies
for
slow
reviews
and
merges,
and
things
like
that
I've
been
working
on
trying
to
catch
up,
but
you
know
it
just
takes
time.
A
The
first
thing
that
I
wanted
to
talk
about
here.
The
only
thing
that
I
have
on
the
agenda
is
to
talk
about
the
multiple
learner.json
issue
that
we
talked
about
last
week,
where
we
were
grouping
stable
and
experimental
packages
together
for
those
that
don't
know,
there's
a
draft
pr
available
for
this.
A
So
you
can
take
a
look
at
what
I've
already
done,
but
I've
sort
of
listed
a
couple
of
the
the
challenges
that
I've
run
into
here
and
some
potential
solutions,
and
I
wanted
to
talk
with
people
about
what
they
would
prefer
for
these.
So
in
no
particular
order
we'll
just
there
is
no
way
to
select
to
learn
a
json
file
when
you
run
learner
commands.
A
F
A
A
So
I
think
it's
probably
safest
to
delete
the
node
modules
folder
when
you
switch
groups
which
is
sort
of
frustrating,
I
actually
just
cloned
the
repository
twice
locally
so
that
I
could
have
one
for
experiment.
You
know
one
one
clone
for
experimental
and
one
clone
for
stable,
so
I
wouldn't
have
to
deal
with
switching,
but
if
anybody
can
think
of
a
better
solution
than
that,
I'm
all
ears,
because
this
isn't
great,
it's
not
bad,
but
it's
not
great
either.
A
One
important
one
that
I'm
particularly
going
to
be
looking
for
barton
valentine's
and
put
on
is
that
the
update
ts
references
step
fails
on
note
8..
So
if
you
look
at
the
pr,
the
tests
for
node
8
fail
every
time
on
both
groups.
What
is
it
changing
from
what
no
what's
the
problem?
A
So
we
have
this
update,
ts,
references
step
in
the
in
the
workflow
and
that
updates
the
ts
config
json
file.
It
updates
this
references
array
and
the
references
array
needs
to
be
regenerated
because
it's
different
for
each
group.
A
A
One
thing
we
could
do
is
have
a
separate
ts,
config
json,
for
each
group,
but
then
you
know
we're
getting
to
the
point
where
we're
copying
so
many
files
to
have
two
different
versions
where
you
know.
I
don't
want
it
to
be
too
confusing
for
new
users
to
get
up
and
running
like
having
to
select
a
specific
ts
config
and
having
to
select
a
specific
learner,
json
and
all
that
stuff.
D
G
D
Because
we
decided
to
have
11
like
two
to
two
fires:
yeah
a
little
experimental.
I
really
am
not
stable,
and
I'm
just
surprised
that
you
have
to
make
this
strange
work
around
like
you
copy
to
be
a
learner
json,
and
you
cannot
specify
the
learner
config.
Whenever
you
run
some
command,
there
is
no
option
to
pass
no.
B
B
A
A
Is
it
similar
to
learner,
then,
did
you
know
solve
similar
problems?
I
guess.
D
Well,
I
can
check
basically
I
can
play
around
to
see
what
it
would
take
to
replace
the
11
hour.
Flash.
A
Yeah,
it's
just
kind
of
annoying.
You
don't
actually
have
to
delete
the
node
modules
like
I,
I
didn't
run
into
any
problems
when
I
didn't.
I
just
think
that,
since
we're
hoisting
on
both,
it's
probably
a
good
idea
to
deal
with
the
node
modules.
D
And
after
you
know,
if
the
rush
supports
like
having
experimental
and
unstable
and
without
problems
like
package
groups,
yeah.
F
In
fact,
you
just
have
a
single
one
on
repo
and
we
deploy
them
all
at
the
same
time.
So
I'm
not
certain
if
you
could
say.
F
Yeah,
I
don't
know
it,
may
it
may
not.
I
I
don't
know
I'm
also
after
today,
I'm
well
after
after
monday,
I'm
out
for
two
weeks,
so
I
don't
have
any
cycles
to
look
at
this,
for
you
guys
either.
A
D
A
We
can
do
it
with
this
solution
like
it's
fine
it
just
there's
just
some
ergonomic
difficulties.
Okay,
what
about
the
note
8
issue?
Do
you
have
any
preference
on
that?
I
mean
we
could
we
could
obviously
just
not
test
on
node
eight
or
we
could
generate
different
ts,
config
files,
one
for
experimental
and
one
for
stable
and
switch
between
those
also,
I
probably
would
prefer
to
just
stop
testing
on
note.
8.
D
A
Nothing
we've
done
has
has
broken
note
8.
It
was
working,
fine.
A
B
Is
the
problem
in
the
package
that
provides
update,
ps
references?
Maybe
we
can
just
fix
it,
so
it
would
actually
support
node,
eight.
A
Yes,
the
problem
is
actually
in
the
update,
yes,
references
package.
So
if
you
look
at
the
failure.
F
A
A
A
No,
this
is
because
we
need
to
run
the
update
ts
references
in
order
to
generate
the
references
array
in
the
in
the
ts,
config
json
file,
so
the
ts
config
json,
has
this
references
array
that
lists
all
the
packages
that
are
going
to
be
built
and
because
we
have
two
separate
groups
now
it
needs
the
the
array
is
different
for
stable
and
for
experimental.
So
it
needs
to
be
regenerated
before
you
run,
compile
how.
D
D
A
Yeah,
that's
fine!
I
guess
I'll
do
that
after
the
call
and
I'll
create
a
quick
pr
for
this
too,
since
it's
pretty
small,
I
don't
think
it
will
be
particularly.
You
know
a
problem
or
anything
like
that.
It
should
be
relatively
easy
to
update.
D
D
A
A
Do
you
think
that's
a
reasonable
solution?
Everybody,
okay
with
that
yep
moving
on
the
integration
test
is
not
yet
working.
I
haven't
really
looked
into
it
too
much,
but.
A
On
the
pr
here,
the
w3c
integration
tests
don't
run.
I
was
thinking
about
just
moving
this
into
the
trace
base
package
anyways,
since
it's
only
testing
the
w3c
propagator.
There's,
there's
no
reason
to
have
it
in
the
root
of
the
project,
and
if
we
just
move
it
into
the
trace-based
package,
then
we
avoid
any
learner,
weirdness
or
anything
like
that.
C
D
I
mean
in
the
error
that
you
show
it
was
written
that
the
learner
json
file
is
missing.
That's
why
it's
failing.
A
Yes,
so
that's
why
it's
failing
now
there
there
it
was
failing
for
different
reasons
earlier.
If
you
look
at
the.
A
A
A
That's
just
the
current
failure,
though
we
look
at
older
ones
from
last
week.
It
was
failing
for
a
different
reason:
I'm
not
going
to
bother
finding
it
okay,
but
it
was
failing
for
a
different
reason
before.
A
And
then
this
last
one
here
when
you
bootstrap
with
one
group
like
experimental
it,
hoists
a
bunch
of
dependencies
into
the
node
modules
folder
and
then,
if
you
switch
groups
and
bootstrap
again,
it
runs
again
with
hoisting
and
there's
potentially
some
you
know
clashing
there
or
some
some
collisions.
A
A
A
Yeah,
I
could
add
it
to
the
like
the
use,
stable,
npm
script.
We
could
have
it
automatically
delete
the
node
modules
and
bootstrap
again.
Would
that
be
okay.
A
It
would
make
it
run
like
a
lot
slower
right
now,
if
you
run
like
use
stable,
it's
pretty
quick,
but
I
don't
know
how
often
we'll
be
switching
between
stable
and
experimental
groups.
I
think
most
prs
will
only
be
affecting
one
or
the
other
right,
because
you,
if
you
want
to
change
something
in
the
stable
group
and
then
use
it
in
the
experimental
group,
you
need
to
release
the
stable
group
first
anyways.
So
I
don't
think
the
rs
that
that
modify
both
of
them
at
the
same
time
are
going
to
be
particularly
common.
F
Just
circling
back
to
the
rush
question
from
earlier
and
the
reason
that
we're
going
down
the
experimental
and
stable
path
in
rush
you
can't
specify
that
packages
or
based
on
the
package
name
don't
use
the
local
instances.
So
we
could
actually
have
a
single
build
project
that
says
all
the
experimental
ones
download
the
the
published
versions
rather
than
the
local
versions,
and
that
gets
around
the
issues
that
we're
talking
about
here,
because
it's
still
one
build.
F
F
We
have
a
script
to
do
that.
That
was
the
script
I
pasted
last
week.
A
I've
never
used
rush
js,
so
I
I
don't
know.
Can
you
give
me
a
quick
like
just
stick?
You
know
thumb
in
the
air
estimate
of
how
much
effort
it
would
take
to
switch
to
use
rush
js
instead
of
learning.
F
I
I
haven't
used
lorna
sorry.
I
don't
know
that
that
side
of
it
but
you're,
probably
looking
like
I'd,
say
no
more
than
a
day.
If
you
know
rush,
if
you
don't
know
it,
maybe
a
couple
of
days
because
really
all
it
is,
you
have
a
rush
jason
in
the
route
that
use
best
for
all
the
projects.
F
We
also
use
grunt
to
control
the
build.
So
I
think
learner
is
probably
a
combination
of
both,
but
you
can
still
use
just
npm
scripts
to
go
to
build
it
and
you
just
say:
yeah
video
rush,
build
rush,
update,
effectively,
goes
and
runs
npm
build
on
all
of
them.
So
it's
it's
just
an
orchestrator.
It's
not
that
difficult.
D
A
A
It
looks
like
somebody
added
a
pr
to
the
to
the
list
of
pr's
to
review
again
I
apologize.
I
haven't
reviewed
that
many
pr's
because
of
the
holiday,
but
I'm
trying
to
catch
up
now
so
I'll
be
going
through,
especially
contrib,
there's
a
bunch
of
pr's
that
I
haven't
reviewed
yet
so
anyone
that
thinks
one
should
be
looked
at
feel
free
to
add
it
to
this
list,
I'll
look
at
it
later
in
the
day.
G
Yep
go
ahead.
Sorry,
so
just
regarding
the
original
thing,
with
the
learn,
multiple
learner,
json
files.
Last
week
we
chose
that
one
as
the
solution
because
of
the
release.
Please
the
release,
please
complications
and
we
wanted
to
have
all
the
sdk
versions
be
the
same,
and
then
I
think
we
also
had
a
few
other
possible
solutions
like
creating
sub
directories
and
a
few
other
things.
Should
we
revisit
those
or
do
you
do
you
want
to
like
do
rush
or
because
I
remember
we
discussed
it
a
lot.
A
Yeah
so
having
a
subdirectory
with
all
the
experimental
packages
would
probably
still
work.
It
solves
some
of
these
issues,
but
then
it
means
we
would
have
to
duplicate
a
lot
of
things
like
the
all
of
the
ts,
config
and
all
that
yes,
config
and
stuff
like
that,
would
probably
need
to
be
duplicated
into
that
subdirectory
it.
You
know
it
simplifies
some
things,
but
it
makes
some
other
things
a
little
bit
more
complex,
but
it
might.
A
A
D
But
I
mean
if
you,
if
you
were
to
develop
something
in
the
experimental
and
you
would
have
to
change
something
the
stable.
You
would
not
be
able
to
to
make
this
automatically
like
the
combined
and
so
on
right,
because
the
experimental
will
be
using
the
version
from
npm
not
from
the
locals.
A
A
Yeah-
and
we
talked
about
this
last
week-
that's
actually
that's
the
behavior.
We
want.
A
Just
create
a
sub
directory
yeah
we'll
try
that
it
might
simplify
some
of
these
things,
I'll,
try
it
and
I'll.
If
it
doesn't
work
I'll
comment
on
the
pr
and
if
it
does
then
I'll
update
appear.