►
From YouTube: 2022-06-03-Node.js Node-API Team 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).
A
B
A
To
the
node.js
note
api
team
meeting
for
june
3rd
2022,
we
will
start
by
asking
if
anybody
who
has
any
enough
they'd
like
to
share.
A
Okay,
if
not,
we
will
flip
over
to
the
standard
agenda.
I
will
share
my
screen
if
I
can
find
the
right
window
there
we
go
so
the
first
thing
is
drive
to
full
coverage.
I
don't
know
if
anybody
has
any
updates
on
that
this
week,.
A
B
A
C
A
A
August,
okay,
yeah
no
problem
just
as
a
reminder
for
us
to
not
forget
things,
and
I
think
that's
it
so.
Okay,
so
we're
doing
pretty
well
on
stale
issues,
which
is
great
tracking
issues
of
module,
boarded
nothing
too
new
there.
We
can
take
a
quick
look
at.
B
B
So
this
poster
has
an
example
that
creates
a
lot
of
async
progress.
Workers.
D
A
B
Yes,
he
creates
a
lot
of
async
progress
workers,
but
in
his
test
he
does
a
wait
for
them
to
to
finish.
So
I'm
really
not
sure.
Why,
because
I
mean
we
do
see
in
the
stack
trace,
it
has
something
to
do
with
collecting
the
garbage
collector
is
running
and
then
some
finalizers
are
happening,
but
then
eventually
it.
It
breaks
some
debug
checks
and
it's
three
different
types
of
stack,
traces
that
end
up
happening.
A
B
Let
me
see,
there's
in
the
let's,
that's
the
first
one
in
the
second
one
and
in
the
second
stack
trace,
sort
of
trying
to
construct
a
new
threat,
say
function,
and
that
seems
to
be
failing
and
that
says
debug
check
failed
with
the
used
nodes
less
than
the
k
block
size.
I
don't
know
what
that
means
and
then
in
the
third
stack
trace,
it's
also
trying
to
construct
a
new
thread,
save
function
and
it
has
a
debug
check
with
the
free
with
the
state
of
the
handle
not
being
free
or
something
like
that.
B
But
all
of
the
crashes
are
in
the
global
handles
cc
file
right
to
deal
with
handle
creation
or
finalization.
It
looks
like.
A
So
the
question
would
be:
is
there
something
in
the
node
api
code
which
is
potentially
corrupting
code
or
is
there
something
I
mean
there
even
could
be
something
in
the
the
like
the
application
code
right
like
not
even
then
a
node
code
is,
is
you
said
you
could
recreate
it?
Could
you
recreate
it
with
a
like
a
small
test
case,
or
is
it
still
like
the
fall.
B
D
Could
it
be
like
a
v8
has
some
kind
of
maybe
some
reasonable
limit
on
some
resources,
and
then
we
just
seem
like
there's
some
some
kind
of
one
million
of
some
some
units
and.
C
A
B
B
B
D
A
I
think
that
would
be
handy
like
if
we
had
a
small
test
case.
That
basically
was
mostly
you
know,
just
no
doubt
on
api
code.
That
does
something
similar,
but
didn't
do
any
other
work
and
if
it
recreates
with
that,
then
you
can
kind
of
rule.
We
can
rule
out
that
there's
some
memory,
corruption
or
something
like
that
going
on
somewhere
else.
A
The
other
thing
is
like:
did
you
look
at
the
so
you
looked
at
gc
memory?
How
about
the
the
like
the
physical
memory
with
something
like
top
or.
A
Yeah
that
would
be
worth
looking
too
like
because
you
know
to
see
if
it's,
if
you,
you
know
it's
one
of
those
things
where
like.
If
you,
whenever
you're
allocating
native
memory,
that's
tied
to
the
the
heat
memory
you
might,
the
heat
might
not
notice
that
there's
memory
being
used
and
therefore
never
do
the
finalization.
That
would
let
you
collect
the
memory
that
you
don't
need
on
the
native
side.
So
it's
just
interesting
to
see
if,
like
maybe
we're
growing
in
native
memory,
as
opposed
to
heat
memory
or
something.
B
A
A
B
A
So
it's
it's
possible
somehow
we're
not
freeing
those
or
even
there's
some
limitation
in
terms
of
what
we're
using,
but
I
think
the
smaller
test
case.
First
to
sort
of
you
know
if
we
say
like
okay,
here's
something
we
can
just
run
ourselves
and
it
doesn't
really
require
any
other
code.
Then
it's
clear
something's
going
on
there.
D
Yeah,
looking
at
this
kind
of
cold
stacks
and
type
of
errors,
it
almost
feels
like
we're
corrupting
some
kind
of
state
of
these
global
handles,
which
which
usually
might
happen
if
we
try
to
access
from
all
threads.
I
wonder
if
we
have
any
any
possibilities
that
we're
touching
these
structures
from
from
no
non
non
domain
thread,
but
maybe
some
different
thread.
B
D
B
One
thing
that
I
noticed
was
that
on
our
node
add-on
examples
repository
because
I've
had
a
couple
of
merges
recently,
there
there's
a
ci
failure
for
the
because
if
you
hit
the
red
x
there
next
to
my
commit
right,
okay,
it's
on
the
build
and
deploy
the
website.
So
that's
been
failing
for
a
couple
of
a
couple
of
runs
now
and
I'm
not.
I
guess
it's
doing
something
with
github
pages
or
on
the
the
node
api
resource.
I'm
not
exactly
sure,
but
I
just
wanted
to
bring
this
up.
B
A
B
And
then
the
link
for
the
yeah,
it's
this
one,
that's
this
one!
So.
B
A
B
But
like
I
guess
that
website
doesn't
really
have
changes
to
it
unless
you
update
the
website
folder
in
in
that
repository
right.
So
since
there
really
haven't
been
any
changes
to
the
website,
nothing
is
really
majorly
affected
by
these
failures
right.
I
just
wanted
to
point
that
out,
though,.
A
A
A
A
C
A
A
Unless
there
is
a
reason
not
to
back
port,
things
tend
to
flow
back,
like
almost
everything
gets
flowed
back
to
the
current.
So,
like
you
know,
if
it
went
into
maine
today,
which
was
19,
it
would
flow
into
18
and
then
it's
kind
of
like,
as
as
it
goes
back
further
in
the
lts's.
But
16
is
the
sort
of
the
main
lts.
Now
it
still
flows
in
once
it's
sort
of
baked
in
in
the
current.
D
Yeah,
this
one's
probably
good
good
to
have,
I
guess,
because
it's
we
we're
kind
of
fixing
module
registration
for
ms
right
yeah.
D
Breaks,
I
don't
think
they're
related
to
my
change,
because
there's
some
kind
of
some
random
tests.
A
Yeah
our
ci
is
nowhere
as
stable
as
we
would
like
I'll
say.
D
A
A
D
No,
no,
this
one
is
actually
I
need
to.
I
need
to
I'm
kind
of
working
on
integrating
changes
from
legend
cars
because
application,
which
is
the
same
same
functionality,
so.
D
D
I
just
rebased
replace
it
today
morning
and
okay,
also
kind
of
I
found
that
there
was
some
missing
an
apical
implementation.
It's
probably
not
required,
but
just
for
consistency.
D
Mostly
about
I'm
asking
like
all
these
different
new
names,
because
I'm
not
good
with
names
and
right
yeah,
we
did
several
iterations,
then
changed
one
way
or
another,
so
any
kind
of
ideas
how
what
better
names
we
should
use.
So
like
definitely
welcome.
B
B
There's
to
discuss
what
is
this,
this
rename
node
api
to
something
less
confusing
misleading.
A
Well,
you
know
I
basically
it's
the
the
complaint
that
node
api
can
be
confused
with
like.
Well,
it's
an
api
for
all
of
node
versus
the
add-on
api,
but
you
know
I
I
my
personal
take
is
okay.
You
know
we
had
a
discussion.
We
we
put
a
lot
of
work
in
to
change
it.
B
A
I
I
personally
don't
think
that
it's
such
a
big
deal
like
I
haven't
seen
people
coming
to
me
and
say
I'm
confused
or
I
haven't
seen
reports
and
so
like
I'm
not
gonna
advocate
for
us
to
change.
I
did
ask
the
originator
if
they
were
okay
with
it
being
closed,
because
since
I
didn't
think
it
was
gonna
happen,
but
they
said
no,
so
it's
still
there.
I
see.
D
Does
it
propose,
like
I
mean
like
instead
of
just
him
saying
whatever
we
have
is
bad
like?
Does
he
propose
something
better?
I
think
you.
A
Know
I
I
can.
Where
is
it,
which
one
was
that
at.
D
Bit
above
like
three
lines
above.
A
B
A
A
So
mention
this
okay
anyway,
I
could
go.
Take
a
look
at
that,
but.
B
C
A
A
No
yes
in
the
node
api
team
meeting,
node
api
team
meeting
day
and
consensus.
B
A
D
Okay,
I
guess
the
question
like
whatever
I
just
saw
in
in
the
original
point
that
something
I
meant
to
ask
internally
inside
of
node.js.
We
have
a
bunch
of
different
modules
and
as
a
kind
of
any
plans
for
us
to
change
internal
modules,
to
use
node
api
that.
A
We
talked
about
that
way
back
in
the
beginning
like
when
we
were
talking,
but
it
was
seen
as
a
you
know:
you
you
prove
it
out
first
and
then
you
might
consider
to
use
those
methods
internally,
I'm
not
sure,
there's
anything
that
would
stop
us
from
doing
that
now
other
than
it's,
not
a
100
coverage,
so
you
couldn't
do
everything
and
the
other
aspect
would
be
like
you'd
have
to
show
that
the
performance
wasn't
going
to
be
degraded,
because
you
know
the
internal
bindings
and
stuff
can
be
more
direct.
D
But
then
I
guess
should
be
like
something
which
will
push
us
to
improve
perf
and
improve
kind
of
abs
kind
of
surface.
A
Yeah,
no,
it's
it's
it's
true
it
just.
I
guess
it
would
be
it
would.
You
know,
take
somebody
who's
like
this
is,
you
know,
has
who
wants
to
champion
doing
that
to
understand
where
it
would
make
sense
where
it
wouldn't
try,
and-
and
you
know
it
is
a
good
question
though
it's
like
have
we
come
far
enough-
that
now
that
something
we
could
say
is
a
direction
we
should.
A
You
know,
drive
the
product
like
try
and
try
and
advocate,
for
you
know,
sort
of
through
the
the
next
10
stuff
is
like
like
what's
needed,
to
make
node
successful,
and
is
this
something
that
you
know
we
could
say
if
we
actually
refactor
this
way,
it's
actually
going
to
make
our
lives
better
enough
to
to
make
it
a
strategic
thing
to
do.
D
I
know
it's
just
general
yeah
feeling
about
like
it's
interesting,
because
it's
what's
something
I
sometimes
when
they're
developing
some
apis
and
some
products
and,
like
I
often
see
developers
saying
oh
in
general,
we'll
use
something
some
internal
better
apis,
but
for
users.
Forgive
us
right.
C
D
A
Yeah,
I
know
yeah,
it's
definitely
a
good
point
and
definitely
like
it.
It
was
discussed
but
like
it
was
a
non-starter
in
the
beginning,
because
it's
like,
oh,
let's
refactor,
all
of
our
internal
stuff,
to
use
something
new
that
we
haven't
tried
out.
Wasn't
you
know
very
palatable
now
that
it's
actually
been
you
know
in
place
for
years
it
might
be,
but
it's
certainly
a
big
enough
thing
that
you
know
somebody
would
need
to
say:
hey
I'm
going
to
go
and
try-
and
you
know,
do
this
and
see
how
it
goes.
D
Yeah,
because
we
we
want
people
to
start
to
use
this
api
safe
api,
but
even
internally
inside
of
our
node.js,
it's
not
being
used
that
much.
So
it's
also
kind
of
also
a
matter
of
adoption.
If
I
open
today
like
youtube
and
search
like
how
I
create
modules
for
node.js,
I
would
not
find
anything
about
node
api.
I
will
find
like
how
to
use
none.
I
would
find
how
to
use
v8
api,
but
there's
almost.
A
D
D
D
You
you
you're
searching
for
yourself
and
your
google
trains.
Sure.
A
A
D
A
B
You
could
try
doing
a
incognito
window.
A
B
A
D
D
A
D
Yeah
I
mentioned
just
youtube
like
if
you,
if
you
go,
for
example,
to
youtube
on
youtube,
then
you're
kind
of
saying
I
would
like
to
say
that
oh
no,
they
don't
occur.
I
think
it
will
not
show
you
know
the
api
to
talk
about
none.
It
will
talk
about
all
these
different
previous
add-on,
apis
right.
Okay,
that's
what
because
what
I'm
saying
I'm
seeing
even
new.
There
are
a
lot
of
new
videos
and
some
of
them
developers
still
kind
of
teaching
kind
of
others
to
use
this
old
old
one
right.
A
A
D
And
I
think
that,
because
of
this
all
this
newbie
a
lot
of
people
who
is
teaching
new
node.js
kind
of
like
developers
to
create
using
different
apis.
They
doing
some
kind
of
disservice.
In
some
sense.
D
Yeah
going
back
to
this
original
issue,
if,
with
renaming
all
the
guys,
without
what
we
can
read
about
what
I
can,
we
can
also
kind
of
learn
from
this
issue
that
it's,
maybe
not
so
much
about
name
but
actually
about
usage
and
widespread
usage
like
should
we
kind
of
promote
it
more
inside?
If
you
know
the
js,
should
we
promote
outside
the
world
a
little
bit
more
and
smoke.
D
I
think
that's
one
of
the
complaints
with
this
issue
was
that
no
dodge
api
is
like
node.
Api
is
too
generic
right
and
kind
of
confuses
people.
Well,
it's
not
exactly
what
it
is.
A
A
I
just
put
the
issue
in
the
wrong
place.
Sorry,
I'm
going
to
close
this
one.
A
We
don't
see
your
screen
sharing,
yeah,
okay,
I'm
just
I'm
just
creating
an
issue,
though
so
I
think
let
me
just
I
can
share
it.
Okay
share.
A
Yeah
that
one
we
could,
I
guess
like
for
me-
I
never.
I
never
want
youtube
to
show
me
how
to
do
something
I
want,
I
shouldn't
say,
never
very,
very
infrequently
I'd
much
rather
have
like
a
short
document
like
two,
I
always
figure.
It's
like
a
two
paragraph
description
will
show
me
exactly
what
I
want
versus
having
to
watch
a
five
minute
video,
but
I
do
know,
there's
many
people
who
are
the
exact
opposite,
so
it
makes
sense
to
to
address
all
the
audiences.
A
A
I
any,
I
think
that
was
there
weren't
any
other
issues
in
the
repo
to
look
at
anything
else.
We
should
chat
about
this
week.