►
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
Hi
everyone
and
welcome
to
the
node.js
technical
studio
committee
meeting
of
this
first
of
june
2022.
As
usual,
we
have
a
a
few
people
from
the
tse
joining
joining
from
all
over
the
globe
today.
So
and
let's,
let's
jump
in
on
the
agenda
as
usual,
are
there
any
announcements
to
make.
A
A
Cool
okay,
so,
let's
jump
immediately
in
on
the
on
the
values
issues
and
the
first
one
is
issue
43054
on
node.js
and
one.
I
think
this
was
yours.
What
the
status
of
it.
B
So
that's
the
reverse
right
yeah,
so
I'm
getting
into
some
blockers
and
yeah.
I
guess
folks
can
read
the
last
comments
on
the
thread
to
have
an
idea
what
the
status
is
but
yeah.
Currently
we
we
have
to
to
make
a
choice
to
move
forward
and
I
guess,
if
folks
want
to
to
chime
in
on
the
pr
thread.
That
would
be
helpful.
B
C
I
have
a
question
about
this
one.
So
wasn't
the
pr
supposed
to
be
a
clean
revert
of
what
was
added
previously.
B
D
B
Clean
result
of
well,
the
clean
river
doesn't
work
because
we've
landed
all
the
changes
and
yeah
the
the
cia
doesn't
doesn't
want
to
turn
green.
If
I
tried
a
clean
resort.
C
Okay
and
what
if
we
revert,
the
next
changes
that
were
added
after
the
breaking
change.
B
C
I
added
that
one
to
the
tic
agenda,
so
I'll
start
off
with
it,
so
the
pr
adds
a
file
and
based
on
the
commits
mentioned
in
that
file,
the
github
blame
ui
would
ignore
those
commits,
so
the
blame
ui
would
be
much
neater.
According
to
the
review
comments,
I
found
in
few
other
prs
that
added
changes
like
adding
more
commas
at
the
end
of
things
that
make
sense.
C
A
How
does
this
will
this
impact
our
multi,
what
the
maintenance
of
this
maintenance
of
this,
like
somebody
will
need
to
make
a
pull
request
to
add
it.
E
C
A
Okay,
I
is
there
anybody
that
has
any
concerns
or
I'll.
We
can
kick
it
back
to
github.
I
don't
know.
What's
the.
B
Maybe
we
could
ask
the
github
support
if
they
plan
of
adding
an
option
to
opt
out
of
this
file,
because
I
think
the
the
current
objection
would
be
erased
if
there
was
a
way
from
the
github
ui
to
just
see
those
ignored
commits.
A
F
Okay,
so
you
were
here:
okay,.
F
A
I
added
all
of
you
to
the
meeting
notes.
Okay,
great,
so
next
issue
is.
A
Four
three:
zero
one:
four
and
we
have
it's
a
duplicate
of
the
revert
of
the
integer
of
the
network
thing:
okay,
the
next
one
is
the
pr42981.
D
D
So,
of
course
the
I
understand
the
overall
backlog
reduction
would
be
a
reasonable
motivation,
but
on
the
other
hand,
we
will
be
losing
vital
data
in
many
cases
where
half
baked
or
almost.
D
A
good
amount
of
collaboration,
good
amount
of
design
discussions,
things
like
that
that
have
already
gone
in,
would
be
buried
forever
if
you're
closing
old
pr's.
Instead,
I
would
look
at
the
reason
why
those
are
stale.
What
is
the
fundamental
problems,
though?
That's
affecting
those
pr's?
Is
it
lack
of
visibility,
lack
of
skills
or
lack
of
people's
bandwidth,
and
I
would
classify
based
on
that
and
take
a
decision
on
certain
class
of
prs
can
be
closed
because
the
pro
underlying.
A
A
Yeah,
no,
it's
totally
good
point.
Okay,
can
you
write
down
your
point
in
the
in
the
issue?
I
think
it's.
We
probably
need
to
come
to
a
conclusion.
I
don't
think
we
are
in
agreement,
so
I'm
just.
A
So
basically
you
are
you
objecting
at
all
or
not
because
in
the
last
message
it's
michael
said
discussing
the
last
yes
meeting
with
no
objection
to
proceed.
So
if
you
want
to
object,
I.
D
H
A
Okay,
so
next
one
is,
this
is
another
fun,
it's
another
fun
one
of
my
I'm
fond
of
these
issues.
Okay,
so
the
global
fetch
break,
break
source
map
issue,
42638.
A
C
F
A
A
A
I
am
going
to
remove
it
from
the
tsc
agenda.
Okay,
so.
A
I
Yes,
we
are,
I
don't
know
if
there's
much
else
to
say
once
we
do
the
rename.
If
you've
got
local
get
clones,
you
will
you'll
need
to
update
your
anything
or
anything
pointing
to
the
master
branch.
You'll
need
to
update
to
point
to
the
to
the
new
reference,
which
will
be
main
once
the
rename
is
done.
So
we
will
build,
will
take
care
of
the
ci
side.
You
know,
hopefully
we'll
catch
all
the
instances,
but
yeah
anyone
with
local
clones
will
need
to
go
through
the
usual
steps.
A
A
Okay,
are
you
also
updating
the
security
and
not
private
clothes.
I
I
I
A
Yeah
well
anyway,
if
you
can
take
a
look,
if,
like
my
main
concern,
is
something
is
needed
from
a
cicd
perspective,
so
that
something
will
need
to
be
brought
on
by.
I
don't
know
like
no.
I
I
I
think
the
ci
should
be
okay,
but
yeah
it'll
be
workflows
like
people
making
patches
whether
they're
patching
based
on
the
right
yeah
base
base
code
underneath
them.
A
Okay,
perfect
last
but
not
least,
a
very
old
issue:
ish
pull
request,
number
three
31
000
very
long
number
and
it's
it
has
been
open
since
the
17th
of
december
2019,
which
is
a
old
one.
A
D
A
I
Think
the
summary
is
that
pr
is
adding
an
option
to
disable
to
turn
off
all
experimental
warnings
and
there's
objections
in
that
pr.
I
mean
this
is
quite
an
odd
pr,
as
mentioned
to
blanket
turning
off
all
experimental
warnings,
but
quite
a
few
collaborators
have
expressed
a
sort
of
tolerance
or
they'd,
be
okay,
with
being
able
to
turn
off
select.
You
know
if
you
were
specific
in
that
you
wanted
a
specific
formula
turned
off,
then
that
would
be
something
they
could
get
behind,
but
that's
not
what
this
pr
currently
implements.
I
A
Yeah,
let's
say
that
I'm
going
to
close
this
pr,
okay
and
saying
closing
in
favor
of
the
issue.
Number
40940
suppress
specific
deprecation
work.
A
Okay,
great
and
with
that
we
have
some
issues
on
the
node.jsc
repo,
so
the
first
one
is
on
board.
Johanna
can't
pronounce
him
pronounce
this
sorry.
A
One
week
tag
for
the
agenda
one
more
day,
so
it's
been
no
objection
so
far.
A
Okay,
so
I
leave
it
on
the
issue.
Okay,
perfect,.
A
C
I
Yeah,
I
I
am
drafting,
I
hope,
to
have
it
open
today
the
announcement
to
go
up
on
the
website
so.
I
Well,
yeah,
we
and
you
know
unless
someone
else
comes
up
with
an
another
viable
way
forward.
We
don't
really
have
much
of
a
choice.
I
think
the
options
we
have
are
where,
where
you
know
a
replacement,
whether
that's
we
try
and
swap
in
openssl
3
during
the
release
or
we,
what
I've
been
looking
at
was
whether
we
could
swapping
the
version
of
openness
so
one
one
from
central
stream
eight,
but
that
also
has
a
lot
of
differences
from
upstream
openness
to
one
one
one.
I
So
both
of
those
options
where
we
replace
openness
itself
during
the
release
with
a
different
version,
they
are
visible
to
applications,
so
our
potential
breaking
changes
yeah.
So
you
know
I
at
the
moment
the
safest
option
seems
to
be
shorten
the
end
of
life,
expand
for
note
16.
So
my
plan
is
to
I'll
I'll
open
the
pr
later
today
and
then
you
know
leave
some
time
for
people
to
review
it,
but
the
idea
will
be
to
announce
that
you
know
this
is
where
we're
the
current
status.
I
I
A
I
A
A
A
That's
the
question
like
again:
I
have
no,
I
I
will
just
submit
the
question.
Let's
just
cut
it,
okay,
to
be
clear.
Let's
just
I
don't
like,
I
would
not
know
who
can
do
that
work
to
begin
with?
Okay,
so
it's
who
can
somebody
throw
money
at
to
be
honest
to
to
to
fix
that
problem?
So
no,
let's
do
okay,
so
richard
will
prepare
he's
preparing
that.
A
Yeah,
I
explain
exactly
what's
going
on
great
cool
okay,
so
we
are
moving
up
to
strategic
initiatives.
G
I
think
there
was
another
item
on
the
agenda,
but
it
didn't
make
it
into
the
issue
because,
oh
okay,
so
which
one
is
it
sorry
in
chat?
It's
the
onboarding
review
to
the
security
group.
A
Okay,
so
joey
you
were,
you
did.
I
think
there
are
a
few
snap
startup
performance
issues.
You
want
to
say
something
on
those
or.
H
Not
I
guess
I.
E
Can
quickly
update
about
the
stuff
I
mentioned
in
the
issue,
I
landed
the
band-aid
for
the
memory
corruption
issue
found
in
the
customs
newsline
snapshot
prototype,
but
it
was
literally
later
reverted
because
of
regressions.
E
I
also
opened
another
issue
in
the
va
issue:
checker
for
discussing
about
possible
solutions
to
the
memory,
corruption
issue
in
general
and
also
the
code
cache
generator
mdk
cache
is
now
gone
because
it's
safer
to
make
the
code
cache
part
of
the
snapshot,
which
is
what
currently
is
in
the
repo.
Now,
that's
all
for
startup
performance.
E
I
think
the
entire
cash
thing
is
going
to
land
in
18,
not
sure
about
the
va
stuff.
I
don't
think
they
can
make
it
amazing.
A
Okay
and
perfect,
oh,
I
can't
wait
to
read
one
more
of
your
articles,
they're
all
very
insightful
on
all
of
what
those
things
that
happen
in
the
behind
the
scene.
So
thank
you
and
with
that
I
think.
That's
all!
If
you
have
liked
this
meeting
and
you
would
like
to
hear
more
about
us
on
how
we
develop
node.js,
you
can
subscribe
to
the
notejs
project
calendar
at
nodejs.org
calendar
and
you
will
be
notified
whenever
there
are
node.js
meetings
and
for
today.
That's
all
so!
A
Thank
you,
everybody
and
see
you
next,
oh
see
you
next
week,
but
one
more
thing:
it's
not
next
week
we
are
not
doing
the
meeting.
We
are
cancelling
it,
so
we
are
going
to
do
see
each
other
in
two
weeks.
Okay,
because
I
think
most
of
us
will
be
in
in
austin
texas
for
openss
word,
so
bye,
bye,
right.