►
From YouTube: 22 Oct 2021 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
A
Share
screen
desktop
share.
A
All
right,
so
the
first
thing
that
we
have
in
our
milestones
is
the
review
for
node
serial
port.
They
have
been
slowly
making
contribution
edits
to
their
to
the
pull
request.
I
do
know
that
there
was
a
comment
made
to
you
specifically
gabe
regarding
a.
A
I'm
not
exactly
sure
what
this
is.
I
just
wanted
to
point
this
out
to
you.
I
haven't
had
that
much
time
to
look
into
exactly
what
is
going
on
here.
B
A
B
B
B
Interesting,
I'm
trying
to
figure
out
why
you
would
even
need
to
do
this.
You
shouldn't
need
to
do
anything
right
now.
A
A
Yeah
this
is
on
node
serial
port.
Maybe
the
easiest
way
would
be
from
the
milestones
it's
on
the
first
one.
Okay,
so
that's
all
that
there
is
for
this
pr.
So
far,
maybe
nicola,
I
think
nicola
is
also
one
that
has
been
reviewing
their
work
as
well.
Since
he's
all
out
this
week.
A
A
A
Right
probably
help
yeah,
okay,
so
so
jack,
then
so
have
you
been
able
to
to
read
and
process
and
sort
of
understand
this
comment,
and
I
guess
what
we've
discussed
last
week
as
to
as
to
why
you
get
the
crash
when
you
do
this
in
the
in
the
rebel.
D
Yeah
I
read
over
a
legit
castle's
comment
and
I
didn't
look
into
the
code,
but
I
think
yeah.
I
think
I
know
what
he's
saying
as
far
as
solutions,
I'm
not
quite
sure
what
next
steps
for
this
ticket
is
or
if,
like
yeah.
This
is
just
sort
of
what
it
is
because
yeah
like
in
my
previous
comments,
I
think
like
if
you,
if
the
v8
repo
sorry
grapple,
doesn't
show
that,
like
sort
of
side
effect,
it
works
fine,
so
yeah,
I'm
not
quite
sure
what
we
could
do
about
this.
One.
A
A
If
it's
a
v8
issue
legendarcast,
do
you
think
that
there's
something
that
we
can
do
to
work
around
it
like
we
did
with
the
throwing
primitives?
We
have
that
that
workaround
we
have
now
is
there
something
that
you
can
think
of
that
would
fix
this,
that
we
could
probably
implement.
C
C
A
I
thought
that
this
issue
comes
when
you're
using
the
rebel
and
it's
in
it,
and
you
want
to
do
the
the
the
look
and
not
look
ahead,
the
auto
suggestion
or
whatever
you
want
to
call
it,
and
it
ends
up
trying
to
evaluate
something
that
throws
an
error
and
then,
since
it
throws
an
error,
you
can
no
longer
run
javascript.
C
If
it's,
if
it
is
calling
javascript,
then
the
weird
things
these
native
functions
have
side
effects
and
they
should
not
invoke
these
native
functions
for
previews
and
that's
so
we
have
the
the
method
of
determining
that
in
this
native
functions
is
invoking.
Javascript
is
that
that
will
throw
a
primitive
values.
C
C
So
it's
not
it's
not
the
problem
about
the
throwing
things
it's
very
common
in
the.
As
far
as
I
can
tell
you
know,
you
can
already
throw
in
strings
from
javascript
right.
So
I'm
not
sure.
So,
let's
say
if
we
can
have
the
not
p
error
object,
wrapping,
primitive
values,
then
w
the
problem
can
be
resolved
by.
C
We
can
throw
in
a
error
when
we
disarray,
javascript
exceptions
and
that's
going
fine,
since
we
they
can
catch
that
error.
But
if
we
cannot
wrapping
primitive
values
into
the
noppy
error,
then
the
problem,
then
the
program
will
crash
and
that
that's
you,
that
is
the
problem
here,
as
far
as
like
I
can
tell
so,
I'm
not
sure
with
with
jax
speaks
if,
if
it
works,
but
if
it
doesn't
work,
I'm
not
sure
okay.
C
A
Okay,
so
then
so
do
you
want
to
keep
this
open
and
then
wait
for
jack's
fix
to
go
in
and
then
re-look
at
this.
C
We
have
to
wait
for
the
we
have
to
wait
for
the
error
object.
Wrapping
primitive
values
landed
on
that,
okay
and-
and
let's
say,
I'm
not
sure
we
have
dry
protests
in
northern
olympia
as
far
as
there
is
no
repetitions,
but
in
other
courts
there
are
reporters,
they
are
testing
reports,
repreviews
and
inspections.
C
A
Okay,
that
makes
sense.
So
then,
let's
put
some
comments
in
here
to
say
that
we
want
to
the
node
poles
wait
for
the.
A
A
All
right
and
we'll
go
back
to
that
pr
when
we
go
to
the
spot
in
the
milestones
all
right,
so
that's
it
for
for
sale.
Do
we
want
to
keep
it
in
this
list
as
stale?
I
don't
necessarily
want
to
always
come
talking
about
it.
Every
week
like
we
have
a
plan
of
action
for
it,
I
think
we
should
cross
it
out
yeah.
It
sounds
good
to
me
yeah.
A
I
can't
all
right.
I
will
have
michael
do
that
all
right.
So
moving
on
to
the
next
item,
no
additional
comments
here,
but
we
always
check
npm
for
node
add-on,
api.
A
I
believe
last
week
we
noticed
that
we
hit
the
the
six
million
and
this
week
it's
six
and
a
half.
It
is
it's.
It's
jumping
I
don't
know
what's
going
on,
but
I
guess
we
never
do
all
right.
So
we
can
just
keep
on
moving
on.
A
Then
we
have
create
matrix
of
testing
methods.
So
we
typically
hear
jack
talk
to
you
about
your
your
open,
pr's.
A
D
Have
yeah,
sir,
so
you
have
a
pr
for
that,
so
it'll
be
a
function
yeah
that
one.
So
I
I
made
some
changes
to
that
based
on
some
like
feedbacks
and
I
think
should
be
good
for
now.
A
Yeah
I
took
another
look
and
it
looked
good
to
me,
but
I
wasn't
the
one
that
had
made
the
majority
of
the
comments
so
gabe
once
you.
If
you
could
have
another
look,
that'd
be
great
too,
and
then
we
can
move
forward
with
this.
A
D
I
think
that's
it
for
now
yeah
I
haven't
been
able
to
get
on
this
recently.
Okay,.
A
That's
fine
did
deepak
end
up
joining.
A
No
okay,
then
we
will,
I
guess,
continue
moving
forward.
I
did
he
did
review
my
comments
about
his
unit
tests.
I
mean.
A
I
don't
understand
why
it's
necessary
to
still
have
two,
but
it
really
has
nothing
to
do
with
the
actual
functionality
of
of
the
pr
or
anything
like
that.
So
I
mean
he
answered
all
of
the
other
questions
of
mine,
so
I
don't
necessarily
have
any
problems
landing
this
if
anybody
else
wants
to
put
any
comments
or
anything
in
that'd
be
great
as
well.
A
Okay.
Moving
on
now
we
talk
about
the
debug
testing,
and
this
is
what
michael's
working
on.
I
don't
believe
there
has
been
any
progress
since
last
week
and
he's
not
here
this
week,
so
we
will
just
move
on
then
burn
down
list
of
issues
raised
by
module
owners.
A
B
A
Let's
see,
this
is
one
that
I
that
we
had
sort
of
been
discussing
for
a
couple
of
weeks
now
it's
regarding
the
removal
of
const
to
signal
and
we
were
sort
of
discussing
about
first,
if
the
cops
can
go
somewhere
else
and
he
tried
that
and
that
didn't
seem
to
work
very
well
because
he
ended
up
needing
to
remove.
A
Let's
actually
go
to
his
pr
to
the
questions
that
I
asked
if
he
could
change
where
he
was
adding
const
and
then
it
needed
to
sort
of
trickle
all
of
these
other
effects.
A
And
so
what
I
ended
up
doing
was
trying
to
take
his
test
that
he
wrote
and
compile
it
against
the
existing
main,
no
dad
on
api,
and
you
do
get
the
the
error
that
he's
that
he
had
initially
reported.
A
Various
const
issues,
so
basically
what
that
means
is
that
you
really
would
have
never
been
able
to
to
use
this
method
or
even
compile
code
with
this
method
or
even
attempting
to
to
use
this
method.
So
in
my
mind,
I
believe
it
is
safe
to
just
remove
the
const,
because
anything
that,
because
you
wouldn't
have
had
anything
working
in
the
first
place,
so
then
we
had
also
thought
well,
maybe
that
means
that
signal
was
never
tested
and
that
it
that
does
seem
to
be
the
case.
A
A
So
I
don't
know
if,
when
we
created
those
individual
issues
for
each
object
and
all
of
their
properties,
I
don't
know
if
we
use
this
as
the
as
a
guide
or
if
it
was
just
overlooked
or
if
signal
came
after
I'm
not
sure
what
what
happened
but
either
way
it
just
was
never
tested.
So
since
it
was
never
tested,
we
never
had
code
to
see
that
it
would
have
never
compiled.
A
A
All
right,
then,
the
second
issue
that
he
pointed
out
was
that
in
async
progress,
q
worker
signal
does
not
trigger
and
I
was
able
to
validate
that
locally.
A
I
have
not
gotten
any
further
than
that,
so
that
will
be
the
next
steps
that
I
have.
B
A
A
B
So
I
think
yeah,
I
think
lucas
lucas
wrote
this
code.
I
just
did
like
a
get
blame
and
I'm
wondering
lucas.
Why
did
you
make
these
cons
because
it
kind
of
makes
sense
because
it
shouldn't
change
any
of
the
shouldn't
change
anything
inside
the
class?
But
then
why
doesn't
it
work?
I
don't
get
it
like.
You
should
be
able
to
like.
If
you
have
a
non-const
class
instance,
you
should
still
be
able
to
pass
it
into
a
const
method
right
and
then
that
method.
C
C
So
since
we
are
just
like
say,
the
name
have
the
action
called
facing
progress
worker
and
the
using
progress
key
worker.
So
we
have
read
about
how
it
in
order
api.
So
let's,
let's
design,
that's
the
original
design
thought,
but
I
didn't
have
time
to
look
into
it.
Why
it
wasn't
working,
but
I
was
maybe
I
should
take
time
to
look
into
this
next
week.
A
All
right,
so
we
will
say
all
of
that.
So
this
is
the
issue
that
we're
creating
for
async
progress.
Q
signal
does
not
trigger
the
tsfn
and
then
here
we
should
now
see.
B
A
A
Then,
let's
see
what
well,
we
have
a
little
bit
of
time.
Let's
see
what's
going
on
here,
so
I
remember,
we
had
talked
about
adding
a
linter
to
our
javascript
because
we
right
now
just
have
one
for
our
c
plus
code,
I'm
guessing.
That
is
what
this
pr
is
for.
A
Let
us
look
at
the
example
and
then
we
can
sort
of
see
if
this
sort
of
works.
What
we
were
thinking
about.
A
A
All
right
and
michael
had
taken
a
look,
seemed
to
have
some
issues,
finding
the
changes,
all
right,
just
waiting
for
feedback
from
the
original
poster
then,
but
in
general,
this
is
sort
of
you
know
what
we
would
want
before
committing.
You
would
get
an
error.
A
Forth,
okay,
it
sounds
like
it's
expected:
behavior
just
needs
proper
documentation
and
that's
why
this
issue
is
still
open
all
right
and
then
this
last
one
that
we'll
look
at
here
is.
A
I
remember
looking
at
this
one
earlier.
This
person
is
trying
to
use
some
async
worker
inside
electron
and
it's
basically
just
using
one
of
the
examples
and.
A
However,
someone
else
said
that
he's
having
no
problems
with
it
and
I
think
it
was
due
to
where
the
add-on
was
being
loaded
for
whether
it
was
in
the
renderer
or
the
native
main
process,
and
I
think
that's
sort
of
where,
where
they've
left
off
he's
commenting
back
and
forth
about
that.
A
A
Yeah,
okay,
so
what's
this
result?
A
Yeah?
Okay!
So
we'll
just
leave
it
at
that
then.
So
that's
all
the
issues
that
I
wanted
to
bring
up
here.
We
can
go
to.
C
A
A
I
think
this
is
this
is
pretty
old
right.
I
don't
really
have
any
context
about
it,
though,
does
anybody
else
have
context
about
this?
One.
A
B
Yeah
this
this
this
is.
This
is
a
recurring
problem
like
if
you,
if
you
create
references
in
a
tight
loop,
then
then
you
know
the
they
they
are
not
recycled
in
time.
So
yeah,
it's
it's,
not
a
hundred
percent
that
it's
gonna
get
recycled
because
it's
it's
it's
up
to
the
garbage
collector,
whether
or
not
it
will
actually
garbage
collect
anything.
A
I
see
okay,
so
is
that
sort
of
what
we
are,
so
he
just
updated
his
example
here.
A
B
Yeah
that
there
there
is
like
for,
for,
I
think
for
node
buffers
we
have.
We
have
like
a
like
a
special
handling.
We
have
special
handling
for
node
buffers
and
I
think
in
the
destroy.
So
if
it
is
a
node
buffer,
then
then
it
might
be
different.
A
B
A
B
Yeah
so
we
have,
we
have
a
class
called
buffer
finalizer,
which
is
which
is
a
subclassifier
and
finalizer.
So,
let's
see
where
we
use
that.
B
Yeah
because
yeah,
because
the
it's
a
different
finalizer
but
then
okay,
so
nappy
create
external
buffer
right.
So
when
you
do
that,
okay,
I
see
okay,
so
so,
okay,
what?
What
is?
What
is
this
person
using
to
create
the
the
deal.
B
B
B
Okay,
so
so,
basically,
what
I'm
trying
to
say
is
that
if
we
we
need
to
special
case
the
creation
of
a
reference
for
for
a
buffer
rather
than
any
other
object,
because
when
you
create
a
buffer
from
native,
then
you
use
an
api,
create
external
buffer
right,
and
so
so
then
you
attach
a
you.
You
attach
a
finalizer,
etc,
etc.
But
the
way
you
attach
the
finalizer
is
different
from
from
the
way
you
attach
a
finalizer
to
any
other
type
of
object.
B
That
gets
attached,
it's
just
a
regular
finalizer
yeah
yeah
yeah,
okay.
So
what
was
that
again?
Github,
no
js
node!
A
A
Invalid
argument,
all
right,
yeah
we'll
take
I'll,
take
a
look
at
this.
Let
me
assign
this
to
me
so
that
I
don't
forget.
A
I
am
not
a
member
of
node
core,
I
guess
well,
I
will
take
a
look
at
this
one
when
I
have
some
time
so
then
that
is
all
the
issues
in
node.