►
Description
A
B
Am
getting
readable
stream
official
tree
the
new
major
version
of
minimal
stream
out
later
on
this
week?
So
hey,
if
you
want
to
check
it
out,
it's
going
to
be
live
sooner
rather
than
later,
so
I
will
put
the
URL
for
testing
it
out.
It
is
already
on
our
release.
Candidate
out
and
I
will
put
the
URL
to
test
it
in
the
notes.
So.
A
Okay,
if
not,
let's
move
on
to
the
regular
items
that
were
tagged
for
the
agenda.
The
first
one
is
request
for
elevated
permissions,
one
three,
three:
seven,
that
one's
being
worked
in
the
build
workgroup
I
think
we
left
it
on
the
agenda.
Just
as
a
reminder,
I
have
looked
at
the
issue,
I,
don't
think.
There's
anything
new
posted
there
and
I
do
know
that
you
know
we're
working
through
you
know.
A
Currently,
the
focuses
is
on
whether
we
can
figure
out
how
to
sort
of
break
down
different
permissions
into
smaller
groups,
and
they
currently
are
are
now
and
sort
of
push
those
out.
But
it's
gonna
be
sort
of
a
longer
ongoing
thing.
So
I,
don't
think,
there's
anything
necessarily
to
talk
here
about
unless
somebody
else
has
something
to
bring
up
this
week.
A
Okay,
moving
on
to
the
issues
tagged
under
no
js'
node,
so
the
first
one
clobberin
nomination,
GM's
21
934-
we
said
welcome
last
week
so
that
one
I
think
just
knew.
We
need
to
get
him
on
board.
I'm
gonna.
Look
to
see
if
I
can
do
that
later
this
week,
unless
somebody
else
beats
me
to
it
so
I
don't
think,
there's
anything
to
discuss
on
that
one.
A
A
A
This
was
an
issue
that
was
raised
out
of
the
user
feedback
sessions
that
we've
had
with
the
tooling
teams
with
that
community.
You
know
basically
having
a
broad
belief
that
you
know
this
make
deer
pee
was
something
that
just
should
actually
be
there,
and
you
know,
throughout
of
the
discussions
from
that,
it
was
suggested
that
you
know
we've
come
up
with
PR
which
it
was,
and
it
seems
to
be,
at
least
in
my
opinion,
fairly
incremental.
That's
in
there
in
terms
of
not
being
a
you
know,
a
major
addition.
It's
miles.
C
C
If
we
consider
the
lead
part
of
small
core
in
the
past,
it
hasn't
been
but-
and
it
also
kind
of
opens
the
door
to
the
question
about
some
other
person
file
system
operations
and
whatever
not,
we
want
to
have
file
system
operations,
but
I
think
when
you
go
and
you
look
at
the
fact
that
you
know
make
their
PN
Rim
RAF
get
downloaded
over
eight
million
times
a
day.
It's
a
pretty
clear
signal
about
how
much
this
is
happening
in
the
ecosystem.
C
Some
hanging
questions
inside
of
the
thread.
We
have
a
bunch
of
approvals,
so
I
think
it's
ready
to
go,
but
one
was
what
the
flag
should
be:
I
think
they
they
went
forward
with
recursive,
which
is
prior
art
from
the
community,
but
there
were
people
who
were
thinking
that
it
should
be
create
parent
would
match
the
possible
implementation
if
anyone
has
any
concerns
about
one
flag
over
the
other.
You
know
now
kind
of
the
time
to
see.
I
is
looking
green
and
everything's
looking
about
ready
to
land.
A
A
Okay,
so
the
next
issue
is
21
7,
6
6,
which
is
the
password
half
hashing
API,
that
one
chocolate
provided
an
update
on
the
agenda
item
earlier
in
that
he
was
gonna.
You
know
last
time
we
did
discuss
it
and
he
was
gonna
come
up
with
a
PR
as
the
next
step
he
mentioned.
He
hasn't
done
that
yet
so
that
we
we
shouldn't
necessarily
discuss
it
but
defer
to
next
meeting
where
you
know.
He'll
you'll
have
more
of
an
update,
any
objections
to
moving
on
from
that
one.
A
A
A
B
B
Specifically
on
our
change
that
as
landed
with
them,
so
basically,
if
you
had
led
stream,
you
could
tag
it
readable
or
writable,
so
you
can
close
either
side,
but
they
were
not
really
enforcing
this
up
up
to
1.20.
Then
they
started
enforcing
this
now.
The
problem
is
that
there
is
no
way,
so
we
because
of
this
we
had
on
the
system
that
supported
it,
which
I
think
that
the
UNIX
systems
you
had.
We
had
standard
output
and
standard
error
that
to
TTI's
TTY
to
be
both
readable
and
writable.
B
In
practice,
however,
in
somewhere
in
around
no
10
dot,
something
when
we
learnt
the
new
WV
updates
this
changed
and
that
behavior
stopped
and
we
request
if
the
error
is
super
bad,
so
the
error
is
completely
unreadable.
So
I
did
this
PR
that,
instead
of
giving
out
bad
error
it,
which
is
like
Enoch
Khan
whatever
something
that
is
completely
unreadable
and
unusable,
I
am
just
actually
throwing
a
good
error
for
this,
with
a
good
explanation
of
their
and
itself.
So,
basically
done
we
are
trying
to
read
something
that
is
not
readable.
So
don't
do
it.
B
That's
about
it.
That's
about
the
case,
however,
and
single
wants
to
see
if
we
can
get
that
behavior
restored
in
libuv.
However,
we
got
no
reply
from
the
libuv
team.
What
it
will
actually
happen
is
there
will
be
we
team,
my
tab
to
add
a
different
parameter
or
another
function
to
their
code.
Ways
to
actually
support
this,
so
that,
instead
of
having
TTY
for
the
tty,
they
just
have
two
things
readable
and
writeable.
They
don't
have
duplex,
so
you
can
create
a
duplicate
object
for
the
tty,
only
only
movie,
while
I
think
in
theory.
B
D
B
D
Was
this
like
I
move
on
the
VP's
part
to
make
that
more
consistent.
D
D
B
B
D
C
B
B
But
that's
replying
that
they
are,
but
that's
well,
it's
a
you
know
it's
I
I!
Don't
have
so
to
me
the
solution
tool
and
that
error.
It's
that
landing,
that
helm
is
assemble
major
one,
but
after
this
is
done,
I
will
actually
open
the
staging.
If
these
lands
I
will
actually
open
the
staging
PR,
the
the
one-to-ten
staging
straight
away
to
back
port
ATV,
disassembler
Bajor,
and
because
these
adding
a
new
API
to
UV
might
take
some
months
and
I
don't
right.
B
C
B
C
B
Is
the
kind
of
the
the
end
result
and
it's
even
more
complicated
because
it
only
happens
from
some
operating
systems
because
it's
some
other
operating
system?
It
does
not.
So
because
it's
not
the
functionality
at
all
and
I
never
even
thought
that
you
could
actually
write
to
standard
output
to
me,
sorry
to
read
from
standard
output,
because
to
me
it
seems
a
little
bit
weird.
B
B
A
B
Have
a
little
bit
challenging
to
do
that?
Yeah!
That's
my
take!
So
at
the
moment
there
is
no
way
I
and
unless
we
revert
to
that
thing
only
you
me
and
we
float
a
faster
on
top
of
the
movie,
but
that
they
made
that
change
for
a
reason,
for
other
reasons
which
I
agree
on.
So
it's
is
not
an
easy
solution
and
I.
A
Okay
sounds
good
okay,
so
unless
anybody
has
any
objections,
let's
move
on
to
the
next
issue-
that
is
twenty
one,
three
five
one
which
is
run
time,
deprecated
buffer,
constructor
everywhere
by
default,
is
chalk
or
on
no
chakra
mentioned.
He
couldn't
make
it,
but
he
did
have
an
update.
I
want
to
go
back
to
the
issue.
Just
a
second
cuz.
He
commented
with
a
suggestion.
There.
A
It
was
a
suggestion
that
you
know
I
think
he
was
kind
of
long
the
lines
of
yes,
we
shouldn't
go
all
the
way
for
ten,
but
he
was
suggesting
that
we
do
something
at
least
in
eleven,
and
so
he
was
really
looking
for
people
to
chime
in
there,
and
you
know
I
think
that's
what
we
should
do
it
should
should
take
away
for
this
week
is
chime
in
look
at
his
proposal.
If
you're,
okay
or
not,
okay,
you
know
express
your
opinion
and
we'll
come
back
and
discuss
it
when
he's
here
next
week,.
B
A
C
Is
a
call
right
now
to
figure
out
when
the
next
board
meeting
is
gonna
be
a
noodle?
Is
opening
people
are
putting
in
their
availability?
If
you
have
items
that
need
to
be
brought
to
the
board,
you
just
put
it
into
the
project
tracker.
It
is
project
1,
yep,
comm,
/,
nodejs,
/,
TOC,
/
project
start
1,
or
you
can
email
to
me
and
I
will
appropriately
file
them.
It's
a
good
time
to
get
those
to
me.
C
B
A
A
You
know
the
TSC
isn't
necessarily
super
happy,
but
not
unhappy
enough
to
say
it
shouldn't
move
forward
and
one
you
know
there
was
a
comment
that
maybe
a
suggestion
on
on
documenting
what
different
modules
wouldn't
would
wouldn't
move
and
so
forth
would
be
useful.
So
there's
been
some
discussion
back
and
forth
on
that,
but
it
hasn't
closed.
So
I
don't
know
if
there's
anything
new
to
discuss
on
that
front.
Anybody
else
have
points
or
comments.
They
want
to.