►
From YouTube: 2021-11-26-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
A
B
A
And
do
you
know
if
there's
any
sort
of
blocking
issues
or
anything
or
just
chugging,
along
in
terms
of
working.
B
There's
there's
no
blockers
yeah.
I
think
it's
just
everything's
going
along.
They
said
that
it's
ready,
it's
not
ready
for
production,
but
it's
ready
for
testing.
Okay,.
A
D
B
A
Okay
sounds
good
next
one
then
stale
issues
that
we've
tagged,
so
I
think
we
can
go
sort
of
in
reverse
order.
Here.
I
see
that
nick
added
this
one
tracking
for
crash
of
callback
scope,
close
on
testing.
D
A
Main
branch,
so
but
but
we
need
well,
we
need
a
better
fix.
Is
that.
B
B
Right
because
I
guess
there
could
be
several
places
where
it
could
be
problematic,
either
in
the
core
or
something
in
our
wrapper
or
something
in
the
test
itself.
So
yeah
the
thing.
E
Is
tricky
when
they
come
to
a
synchronous
system?
Previously
we
run
tests
parallel
and
we
I'm
not
sure
if
there
is
anything
that
is,
they
are
widening
while
doing
there.
So
it's
going
wrong,
and
so,
since
we
are
already
like
say,
pipelining
our
asynchronous
tests
and
one
by
one.
So
I
believe
the
condition
will
be
better
to
testing
this.
I
think.
E
A
A
A
B
A
B
Right
that
was
with
the
acing
progress
worker.
In
that
scenario,
things
were
const
and
should
not
have
been
right.
B
D
B
C
D
B
D
B
B
But
maybe
that
doesn't
always
work,
because
if
I
recall
correctly
that's
what
the
gendercast
used
for
the
async
progress
worker
implementation,
he
was
using
that
as
a
guide
and
there
they
had
the
the
execute
progress
whatever
as
const.
So
that's
what
we
did
and
now
we're
seeing
that
it's
problem
problematic
right
so
but
I
guess
it
still
doesn't
hurt
just
to
look.
But
I
don't
know.
D
F
E
B
B
B
B
A
I
I
still
wonder
like
the
intent,
if
it's
purely
like
okay,
yeah
technically
at
the
sea
level,
we're
not
changing
state,
then!
Yes,
if
the
intent
is
like
hey,
I
can
call
this
and
I
know
nothing
changes
you
know
like.
I
haven't
affected
the
state
of
of
the
object,
so
I
could
use
a
cached
value
of
it
or
something.
That's
not
technically
correct.
Right.
A
B
A
Right,
and
so
I
guess
from
the
c
perspective,
you
could
still
use
the
you
could
still
use
the
object
right.
Let's
see.
B
C
E
A
D
D
A
E
E
C
E
D
B
A
B
A
D
E
D
Okay,
so
that
one
okay,
we
can
move
on
to
the
next
one,
which
is
this
one.
A
A
B
A
B
D
B
D
D
C
A
Okay,
so
yeah,
so
if
you
take
take
a
look
and
then
I'll
go,
you
know,
I
think
once
we
get
your
look,
then
we'll
just
say:
that's
it
and
we'll
land
it
so
make
sense.
Okay,
perfect.
D
Good,
okay
tracking
issues
for
modules
that
were
ported.
D
A
B
B
B
This
one,
yes,
so
the
actual
header,
the
not
the
inline
one.
I
guess,
okay,
this.
D
G
Yeah,
so
I
made
the
changes
I
I
tried
it
out
to
use
symbol,
but
the
problem
with
that
is,
it
seems
to
like
I
use
symbol
for
to
fetch
symbols
that
are
if
it
exists.
I
just
if
it
doesn't
exist,
I'll
create
any
symbol,
but
that
is
crashes
on
some
of
the
tests
and
seems
to
have
a
bit
of
a
unpredictive
unpredictable
behavior.
So
I
think
in
the
end
we
opted
to
just
use
like.
A
Yeah,
I
think
it
I
think
it's
because
we
we
came
to
the
conclusion
that
symbol
wasn't
gonna
work,
particularly
if
you
have
like
multiple,
if
there's
any
reason,
you're
using
different
m's,
you're
gonna
you're
gonna
get
a
different
symbol,
so
it
wouldn't
work
from
that
perspective,
and
I
can't
remember
the
discussion.
I
thought
there
was
even
another
like
it
was
like
symbol
might
be
nice,
but
it
just
didn't
like
it
didn't
add
enough
benefit
versus
the
potential
for
problems.
G
A
G
That
would
be
under
conversation.
I
believe
the
conversation
tab.
A
B
A
Okay,
so
we're
okay
to
move
on.
Yes,
okay,
drive
towards
full
coverage.
I
think
the
blog
post
to
point
to
the
external
option,
so
I
think
jack
you
were
gonna,
take
a
look
at
putting
together
the
draft
of
that
blog
post.
Oh
yes,.
G
F
Because
if
not
I'll
just
send
you.
D
B
C
A
The
other
thing
you
could
do
is
put
it
into
like
a
google
doc,
and
then
you
can
post
the
link
to
that
google
doc
easily.
A
Whichever
way
this
works,
for
you
sure
right
right,
enable
testing
for
add-ons,
we
don't
have.
A
And
then
burning
down
a
list
of
issues,
I
don't
know
if
anybody
has
any
particular
ones
they
want
to
highlight.
B
It's
still
the
asic
progress
one.
Unfortunately,
I
have
not
had
any
time
to
to
work
on
that.
Okay,
but
that's
the
only
one
that
I
know
of
right
now.
A
Okay,
I'm
just
looking.
I
don't
see
anything
that
this
one
is.
A
A
A
C
A
B
C
A
Okay,
great,
maybe
just
keep
a
look
at
the
ci
tests.
Just
when
it
runs
next
runs
just
to
see
the
testing
across
platforms.
I
don't
think
there
should
be
any
issues,
but
always
a
good.
You
know
like
that's
just
here
if
you
go
to
the
general
ci,
so
just
make
sure
this
is
still
green.
Tomorrow
is
what
I
typically
do
after
landing:
some
things:
okay,
cool,
okay,
great
good,
okay,
anything
else!
I
I
don't
know
so
high.
A
Yeah
and
if
you
have
any
questions
you
know
feel
free
next
week
to
like
to
you
know,
we
can
take
some
time
during
the
meeting
to
help
answer
those.
So.