►
Description
A
B
Maybe
yeah
there's
a
PR
open
that
would
may
know
Prentiss
back-trace
when
you
abort
the
process
with
with
sting
in
flight,
pressing
ctrl
C,
and
there
were
people
if
people
could
take
a
look
at
that
and
say
like.
Is
this
something
you
wanted
to
do
in
this
farm?
I
think
the
code
is
ready.
It's
just
like
people
should
take
a
look
at
it
and
say:
is
it
something
major
or
something
it's
PR
to
nine
qo7
elbows
doing.
D
And
very
briefly,
lot
of
things
currently
being
discussed.
The
things
that
are
more
importantly
for
more
important
for
the
node
community
are
the
trouble
fund
and
the
organization
of
the
collaborator
summit.
So
the
travel
fund
is
there's
been
a
request
for
feedbacks
on
by
the
CPC
on
the
admin,
repo
and
the
travel
fund.
Management
is
going
to
move
from
the
node
fund,
funded
from
the
node
PSC
and
can
come
to
the
sea
beads
to
the
CPC
and
yet
accessible
by
all
the
other
projects
as
well.
D
Then,
the
next
the
regarding
the
summit,
the
organization
for
the
summit,
is
going
to
be
great
to
the
course
to
this
open
the
s
foundation,
github
repository
they're,
going
to
migrate,
the
repo
from
one
to
the
other,
and
if
there
are
any
objection
to
that,
please
let
me
know
and
I
will
try
to
raise
them,
but
it
seems
like
pretty
straightforward
and
the
Ganesha
will
take
place.
There
also
be
book.
Your
travel
like
consider
coming
to
the
node
plus
J
s,
Interactive
conference
and
attending
the
club
earth,
or
some
ik
afterwards.
D
So
the
conference
is
on
the
eleven
and
twelve
of
December
in
Montreal,
and
the
collaborator
summit
will
be
on
the
13th
and
14th.
So
please
come.
We
need
you,
okay,
it's
the
greatest
moment
about
the
is
one
of
the
greatest
moment
of
the
node
community
and
overall,
all
the
new
open
areas,
foundation
community.
So
everybody
is
weicome
to
come.
Yeah.
A
It's
really
a
great
way
to
connect
with
a
lot
of
the
discussions
that
are
going
on
and
progress
on
things
that
can
take
a
little
bit
longer
over
github
and
and
meet
the
people.
So
yeah
I'd
echo
Mateos
suggestion
that
it's
it's
really
something
good
to
attend:
yeah,
okay,
so,
on
the
board
level,
the
there
was
a
board
meeting
last
week
and
I've
added
the
link
to
the
recording.
A
So
if
you
want
to
watch
the
public
session,
it's
there,
the
one
thing
I
want
to
call
out
of
note
is
that
planning
thinking
for
the
next
nodejs
plus
interactive,
so
in
2020
is
underway,
and
one
of
the
things
I
thought
I
just
want
to
make
sure
people
are
aware
of
upfront.
Is
that
the
date
for
next
year's?
So
not
this
one,
but
the
next
one
is
potentially
going
to
shift.
Think
dates.
A
Since
you
know
late
spring
early
summer
being
considered
even
October
was
thrown
out,
you
know,
and
some
of
that's
being
driven
by
a
sort
of
event,
space
and
and
when
we
think
you
know
we're
gonna
get
the
best
attendance
other
than
that
I.
Don't
think
there
was
anything
of
note
to
call
out
any
questions
comments.
A
Okay,
then,
let's
move
on
to
the
next
issues,
tag
for
the
agenda,
so
the
first
one
in
the
know
just
know:
GS,
/,
Note
repo,
is
streamed.
Dota
midair
after
destroy
this
is
number
29.
197
feel
free
anybody,
who's
involved
in
that
to
jump
in
otherwise
I'm,
just
looking
to
see
how
it
was
added
to
the
agenda.
E
D
And
here
it
is
so
this
will
issue
2
9
197,
it's
a
significant
change
for
easiest
close
the
PR
right
now,
okay,
anyway,
the
key
part
here
in
the
key
question
here-
and
this
is
something
that
we
probably
need
to
talk
about-
a
little
bit-
is
related
to
the
behavior
in
streams.
So
when
a
streams
error
is
it's
still
possible
in
a
lot
of
cases,
that
error
will
be
emitted
again
and
there
is
no
way
to
intercept
that
in
any
form
and
tear
it
down
the
string
properly.
What
running
is
progressing
here
is
essentially
assembly.
D
F
A
D
A
D
D
A
D
A
G
G
You
know
because
I
know
well,
I,
guess
what
I'm
saying
is
that
you
know
after
a
stream
is
destroyed.
You
know,
at
least
the
semantics
in
my
mind
of
destroy
are
that
all
resources
related
to
the
stream
have
been
released
right,
and
so
so
the
ability
to
the
ability
to
trigger
an
error
is
only
due
to
to
an
artifact
of
of
JavaScript,
which
is
that
the
actual
JavaScript
object,
that
is
the
stream,
is
still
around.
But
it's
it's
just
Hollow
right,
there's
nothing
associated
with
it
anymore.
Exactly.
G
Know
and
and
obviously
the
the
the
the
place
in
the
code
where
the
error
is
thrown
has
a
reference
to
it
and
it
can
keep
a
reference
to
it
essentially
forever,
but
but
does
it
makes
sense
that
that
it's
it's
still
a
stream?
You
know,
because
then
you
can
essentially
expect
errors
from
streams
that
you
closed
15
years
ago.
D
D
D
D
Likely
likely
that
might
be
a
good
feedback.
Okay,
it's
saying
instead
of
swallowing,
let's
just
throw
the
error
back
to
the
to
the
user
ascension
that
can
also
be
you
know
just
change
that
behavior
instead
and
say
you
know,
if
you
call
it
more
than
once,
then
it's
a
bug
on
your
code,
essentially
I.
D
D
A
A
We
understand,
there's
an
issue,
but
it's
not
something
that
we
think
we
want
to
change
now,
because
of
that
potential
breakage,
like
in
terms
of
a
priority
list,
is
this
okay
I'm
gonna
promote
rich
to,
but
is
this
something
we
think
we
need
to
do
in
the
short
term
or
you
know?
Is
it
something
that
we
can?
A
A
D
E
A
A
Klaus
can't
make
it
today,
but
he
has
flagged
that
issue.
29
to
46
needs
help,
which
is
some
of
the
C++
testing
tests.
Failing
I
did
have
a
quick,
quick
look
at
it.
It
seems
to
need
a
little
bit
of
more
information,
at
least
for
me
to
understand
exactly
where
help
is
needed,
so
I
might
try
and
see
if
I
can
help
him
do
that.
But
the
call
was
that
that's
sort
of
the
major
blocker
right
now.
So
if
people
can't
help
out,
that's
that's
a
good
one
to
get
involved
with
I'm
rich.
D
D
D
B
D
A
I
Whoops
wrong
button-
I,
don't
know,
but
we
do
have
a
rule
about.
You
are
allowed
to
dismiss
objections.
If
they're,
if
they're,
not
you
know,
explained
and
22
days
would
seem
to
be,
it
seem
to
be
a
long
time.
I'm
not
saying
we
should
do
that,
but
I'm
saying
that
it's
it's
an
option.
If
this
you
know,
if
that's
the
only
thing.
A
A
A
A
A
B
A
E
D
Is
core
promise
API
is
so
I
have
been
slowly
progressing
on
adding
things
to
Amenti
meter.
Am
I
PR
to
having
2
meter
so
that
my
work
on
a
mentor
meter
overall
and
those
streams,
so
this
is
really
progressing.
Unfortunately,
add
some.
You
know
there
was
other
things
added
other
areas
in
core
that
needed
my
attention,
so
I
would
not
able
to
put
enough
effort
as
much
as
I
wanted.
There
is
this.
My
most
of
my
work
is
currently
on
on
this
I'm.
D
D
Asked
if
you
could
take
a
look
to
these
BR,
which
is
two
seven,
eight
six
seven
and
and
so
that
that's
it
I,
don't
know
why
Google
Docs
does
not
load
up
for
me.
So
if
you
can
fast
it
okay,
yeah
it
just
loaded
so
I'm,
adding
it
to
the
notes
but
yeah.
If
you
can
take
a
look
at
that
PR,
it
includes
many
most
of
my
changes
and.
A
A
I
A
I
We
go
there,
you
go
okay,
let's
try
this!
Then
I
was
saying
that
if
there
was
I,
don't
think
there's
anything
from
the
open
Jas
and
from
meeting
that
needs
to
be
recounted
here,
although
I
watched
it
after
the
fact
and
you
were
actually
there.
So
if
you
have
anything
to
say
about
it,
great
otherwise,
I
need
to
talk
to
you
and
rod
and
maybe
show
out
this
week.
I'll
shoot
an
email.
It
just
keeps
circling
back
to
you
guys
so
yeah.
A
There
was
some
discussion
of
which
overlap
in
terms
of
some
of
the
same
challenges,
but
I
suspect
that
there's
going
to
be
a
relatively
long
ramp
up
there
in
terms
of
and
in
terms
of,
you
know,
figuring
out
what
to
provide
and
how
to
provide
it,
and
you
know
it
may
start
to
you
know,
do
things
around
the
edges
like
our
managing
our
certificates
and
and
other
resources
which
we
could
take
advantage
of,
but
I
don't
think
it's
going
to
necessarily
change
the
discussion.
We
need
to
have
internally,
at
least
in
the
short
term,.