►
Description
B
C
Hi
everyone
I
mostly
to
normal
issue
in
peer
review.
I
did
one
bigger
thing:
that's
the
deep
PR
for
change
locks
for
individual
items
in
the
in
detox
and
I'd
like
everyone
to
take
a
look
when
they
have
the
time
and
see
whether
anything's
missing
in
their
personal
field
of
experience
and
yeah.
Next
one
is
Tucker
Nikita.
D
A
Arguing
about
promises
on
twitter
at
I've
been
attempting
to
update
my
promised
rejection
crush
on
gcp
are,
but
it
the
failing
miserably
at
it
because
of
some
changed
the
internals,
mostly
something
relating
to
how
they
changed.
Was
it
native
week?
Map
I
think
doesn't
work
the
way
I
used
to
use
it.
So
I
need
to
use
like
a
C++
primitive
for
that
and
that
just
hasn't
gone
very
well,
so
not
really
much
there
yeah
I,
guess
not
too
much
else.
I
J
Scheduled
and
basically
attended
the
PTO
deep
dive
benchmarking
meeting
did
some
investigation
and
wrote
a
proposal
for
how
we
should
approach
our
NPM
module,
publishing
ongoing
work
with
a
bi-stable
module,
API
team
we're
starting
to
get
close
to
the
vm
summit,
which
is
scheduled
from
arch
third
I.
Think
that's
a
week.
This
Friday
investigation
of
sums
390
submit,
suggested
Jim
issues
landed.
The
quality
was
feed
blog
that
has
been
in
the
pipe
for
a
while
and
finally,
just
general
issue.
Reviewing
commenting
landing.
B
K
The
release
of
v48
yesterday
in
6
10
0
and
I
mentored
Italo
through
the
V
760
release,
which
was
his
first
release.
It
was
really
exciting:
neck
senior
releasers
on
board
Scotch
module
with
Brad
yesterday
and
discuss
modules
with
Ali
yesterday,
I
thought
about
modules,
just
modules,
modules,
modules
modules,
I
got
relief
guides
together
for
carrying
the
gold
mine,
I'm,
not
sure
where
we're
at
from
the
technical
steering
committee.
K
As
far
as
improving
the
story
of
MDM
modules
that
are
owned
by
the
foundation,
but
getting
things
in
in
the
repo
so
that
as
soon
as
are
ready
to
hand
over
credentials,
people
are
ready
to
go
and
I
just
wanted
to
do
a
plug.
My
ret
mentira.
This
awesome
guide
on
streams,
which
was
very
well
received
last
week
and
next
up
his
alley.
L
So
I
got
the
internet
back
up
for
the
arm
cluster
last
week
and
reconnected.
All
of
that
and
fixed
up
some
problems.
There
still
got
some
outstanding
problems
on
some
ass,
so
I've
got
three
of
them,
disconnected
there's
still
a
problem
with
a
one
of
the
arm,
v8
machines.
So
if,
if
you
get,
if
you're
getting
Jenkins
type
values
on
an
arm,
v8
build
I'd
like
to
hear
about
it.
Just
and
they've
been
coming
up
occasionally
and
I'm.
Just
there's
this
one
machine,
that's
it's
causing
problems,
but
I
still
don't
know
what
the
problem
is.
L
So
try
to
address
that
I've
been
dealing
with
historical
reported
problems
on
branch,
different
changelog
maker,
merging
some
things
there
and
making
some
new
pull
requests.
Sorry
for
everyone
for
being
behind
on
those
and
just
general,
get
him
back
into
the
fray
on
gear
he's
so
is
Michael
Michaels.
B
F
N
My
name's
all
right
so
I'm
prepping,
acing
cooks,
I'm,
going
to
placing
it
in
a
new
PR
because
the
old
PR
so
old
and
you're
tagging
the
ctc
so
that
everybody
can
come
start
picking
apart,
also
been
writing
a
new
PR
for
FS,
so
that
read
and
write
will
accept
array
buffers
along
with
you
and
ADA
raise.
Although
all
the
reasoning
for
that
will
be
explained
in
the
PR
next
is
rich
doing.
B
Stuff
with
tests
I've
been
doing
stuff
with
the
assert
module
doing
stuff
with
docs
I've
been
doing
stuff
with
no
to
do
have
a
new
stuff
without
Ricci
and
like
everybody
else,
I've
been
commenting
on
issues
and
reviewing
PRS,
which
probably
we
don't
really
need
to
say
in
the
stand
up,
but
you
know
feels
good
to
mention
it.
It's
work
so
other
than
that.
Let's
get
on
with
this
meeting,
unless
I
skipped
anybody,
do
we
miss
anybody.
B
Okay,
yes,
Brian
did
just
joined,
let's
see
here
well,
we
did
read,
we
did
read
out
what
Brian
wrote,
so
I
think
I'm
going
to
just
charge
ahead,
okay,
so
the
first
item
our
way.
No,
we
go
to
previous
meeting
first,
so
we
didn't
have
a
meeting
last
week
because
we
had
a
sparse
agenda
and
light
attendance,
and
that
happens
sometimes
but
two
weeks
ago,
I
think
the
things
we
talked
about
were
updating
the
cutler.
B
Maybe
this
was
last
week
was
updating
the
copyright
which
James
reported
in
the
issue
tracker
that
there's
he
doesn't
have
an
update
on
that.
Yet,
but
my
next
week
and
yes,
modules
module
loader,
which
we
now
have
a
tracking
issue
for
the
async
loader
for
module
interop,
so
I
think
we
can
I.
Think
I,
don't
know
that
we
have
anything
to
talk
about
about
last.
The
resolution
from
previous
meeting
someone
interrupt
me
if
I'm
wrong.
B
I
I
This
has
been
deprecated
use
inspect
instead,
so
as
the
sunburn
major
change
of
relation
go
in
till
eight,
but
we've
discussed,
including
it
in
a
7
release
to
give
because
the
time
frame
is
pretty
short
anyway
and
to
give
people
as
much
extra
time
as
possible
to
prepare
if
they
need
so
I
had
one
other
factor
that
I
they
want
to
bring
up.
Is
that
what
exactly
will
happen
in
8
is
a
little
bit
dependent
on
whether
V,
whether
we
go
with
v8
5.7
or
5.8.
I
I
If
we
use
v8
5.8
5.7
still
there
so
would
still
work
and
I
bring
that
up,
because
if
we
go
with
5.7
and
therefore
note
8
continues
to
support
the
old
debugger
interface,
then
maybe
we
don't
land
the
deprecation
until
too
late
point
0
now
so
yeah,
so
just
kind
of
two
intertwined
questions.
First
of
all,
do
we
landed
in
7x
and
does
whether
we
go
with
v8,
5.7
or
5.8?
In
the
initial
release
of
note,
8
effect
that
decision,
hey,
Josh
one
question.
B
B
C
B
Should
we
should,
we
doesn't
make
sense
to
mention
that
I
guess
and
but
whether
or
not
it
does
make
sense
to
mention
that
I'm
I'm
all
for
deaf
the
deprecated,
the
runtime
deprecation
on
this
happening
sooner
than
we
normally
do
for
all
the
reasons
josh
outlined,
and
also
because
this
is
not
like
a
deprecation,
that's
going
to
end
up
in
people's
log
files.
This
is
a
deprecation.
It's
going
to
end
up
when
they
go
to
use
an
interactive,
CLI
tool
and
that's
a
different.
You
know
that
that's
a
different
takes
it
doesn't
require.
I
I
think
there
might
be
something
for
me
to
clarify
here,
so
there
are
actually
there's
no
dash
dash
debug,
which
actually
just
activates
the
interface,
it's
not
the
actual
CLI
tool
and
then
there's
no
debug,
no
space,
which
actually
runs.
I
think
it's
the
underscore
debugger
jas
as
the
main
on
the
main
event
loop
and
then
spins
off
the
script,
to
be
debugged
in
a
separate
process
so
that
the
node
debug
no
dash
it's
a
new
space
debug
is
anna,
actually
helped
land
the
PR
from
yon
crumbs.
G
A
I
G
A
So
I
just
wanted
to
chime
him
to
let
people
know
or
remind
people
that
some
precedent
has
been
set
for
something
like
this
before
we
did
agree,
although
we
did
never,
no
one
ever
took
it
up
the
fall
through
because
I
guess
well.
We
didn't
probably
care
enough
that
we
would
do
essentially
the
same
thing
for
essa
Malik
when
the
buffer
changes
happen
and
I
believe
one
other
thing
too
around
that
time.
So
we've
agreed
to
do
this
sort
of
thing
before
can.
C
M
I
missed
the
earlier
part
of
the
discussion,
so
I
don't
know
the
exactly
what
point
we
are
debating,
but
but,
from
my
point
of
view,
I
think
for
version
8.
It
would
be
good
for
us
to
switch
the
debug
come
online
flags
to
inspect
it,
so
the
flags
continue
working
in
it.
They
just
use
a
supported
version
of
the
debugger
as
opposed
to
a
to
a
one.
That's
going
to
go
away.
M
So
it's
a
semper
major
change,
because
behaviors
are
subtly
different
because
note
inspector
words
lightly
differently
from
no
debug,
but
but
at
least
we'll
have
a
more
supportable
thing
and
it
enables
a
few
other
things
to
happen
that
are
currently
blocked.
That
would
be
terrible
not
to
get
into
it.
I
I
I
was
just
gonna
say.
Maybe
what
we
can
conclude
here
is
that
we
should
land
the
dash
dash,
debug,
deprecation
electronics
in
the
notes,
ace,
debug
aliasing
it
to
note
inspect,
will
continue
the
work
on
that
and
basically
we
can
approve
now
that
go
ahead
and
well.
Maybe
we
shouldn't
approve
landing
that
till
eight
guess,
I
was
going
to
say
we
can
improve
landing
that
as
soon
as
it's
ready
to
but
I'm
almost
not
sure.
If
that's
the
same
now
as
I
was
saying
it
if.
B
L
A
A
M
Go
hand
in
hand
I
mean
so
the
debug
debugger
is
matched
with
the
dash
track,
debug
sort
of
Egypt.
So
if
one
is
the
radius
I
think
that
there
should
be
an
alias
as
well
but
I
as
for
the
deprecation
I,
so
in
node
9
we're
only
going
to
have
inspect
so
it
does
make
sense
to
added
replication
in
node
7
saying
that
debug
is
going
to
go
away,
for
it
will
keep
debug
functional
it
just
will
be
plumbed
differently.
A
M
M
A
I
Yeah
I
think
we
were
going
on.
The
I
was
going
on
it.
So
I
think
we've
been
going
to
submission
that
debug
and
inspect
are
two
different
things,
and
so
we
wouldn't
alias
dash
dash
debug
the
dash
dash
inspect,
that's
how
it
landed
and
master
I
mean
we
could
change
that.
I.
Think
yeah,
note
space
debug
we've
been
saying
we
would
alias,
but
maybe
we
should
revisit
that.
B
E
I
B
B
You,
okay,
cool
next
issue,
is
an
issue
I
put
on
there,
but
it's
really
Bradley's
issue
and
I'm,
not
sure
we
need
to
talk
about
it
this
week,
but
I
guess
they'll.
Let
us
know-
and
that
is
the
tracking
issue
for
the
async
loader
for
module
interop.
Is
there
anything
the
CTC
needs
to
either
know
or
make
a
decision
on
regarding
this
at
this
time,
Bradley
or
things
just
kind
of
moving
along
and
the
let
us
know
when
stuff
is
needs
more
attention.
Oh.
D
There
isn't
really
anything
interesting
about
implementing
esm.
Going
on,
we've
got
a
prototype
which
has
some
nasty
hacks,
because
the
v8
API
needs
to
be
fixed
up
a
little,
but
it
works
I'm
starting
to
write
a
whole
slew
of
unit
tests.
So
we
actually
check
the
behavior
against
require
the
behavior
differs
somewhat
radically
since
its
URL
based,
but
that
was
known.
I
did
expose
something
while
implementing
it,
which
is
there's
an
interesting
behavior
in
require
where
it
can
actually
fall
through
and
have.
D
Files
added
to
other
people's
packages
when
resolving
which
I
noticed
and
that's
a
slightly
different
issue
from
esm,
but
we've
got
Lucian
rules
going
on
and
I'm,
not
sure
that
that
behavior
should
be
preserved
for
esm.
So
a
the
basic
concept
is:
if
I
have
a
react,
node
module
and
it
doesn't
have
a
file
named
foo
I
can
actually
put
a
react.
Node
module
in
the
node
modules,
folder
above
react
and
add
a
file
foo
and
require
will
find
the
parents
foo.
This
kind
of
violates
some
black
boxing
expectations.
D
B
D
F
D
A
Yeah
I
mean
that
kind
of
like
sounds
like
a
bug
to
me.
I
don't
know
if
we
would
want
to
get
rid
of
it
and
require
because
we
like
this,
there's
a
reason
why
we
have.
The
module
system
is
going
on,
quote
locked
and
it
for
all.
We
know
someone
depends
on
it
somewhere
in
existence
and
will
complain
about
it.
They
will
probably
be
bigger
than
we
suspect,
but
like
I,
don't
really
see
why
we
would
preserve
that
behavior.
A
D
A
D
And
that's
part
of
what
I'm
writing
tests
for
right
now,
so
URL
encoded
characters
that
were
previously
allowed
now
can
have
effects,
if
you
don't
URL,
encode
them
so
like.
If
you
had
a
question
mark
in
your
file
name
or
something
like
that,
so,
but
those
are
kinda
just
by
the
nature
of
using
URL
base
paths.
D
D
B
B
B
B
Right
great,
then,
we
won't
talk
about
this
one
and
then
the
tsc
is
something
James
updated
us
on
in
the
in
the
in
the
issue
tracker,
so
we're
all
set
there,
and
he
also
put
in
the
issue
tracker
a
couple
other
proposed
deprecation
'he's,
a
couple
other
links
to
pull
requests.
The
very
proposes
deprecation
so
definitely
take
a
look
at
those,
but
I
think
it
would
probably
be
premature
to
talk
about
them
here.
If
anyone
disagrees
start
the
conversation
now
I'll
shut
up
for
10
seconds.
B
B
There
is
a
calendar,
no
Jess
foundation,
calendar
maintained
by
William
khaki.
That
is,
there's
a
link
in
the
minutes.
So
if
you
go
to
the
CTC
repository
and
look
at
the
minutes
for
this
meeting
or
any
of
the
recent
meetings,
you'll
see
a
link
there
for
a
calendar
that
will
give
you
complete
meeting
listings
or
complete
ish
meaningless
things.
I
should
say
this
ctc
this.
This
meeting
will
happen
again
in
one
week.
It
will
be
15
hours
earlier.
It
will
be
at
five
a.m.
B
UTC
if
you're
on
the
west
coast
of
the
United,
States
or
Canada,
that
will
be
9
p.m.
the
tsc
meeting.
Next
one
is
tomorrow
same
time
as
this
meeting
started.
Twenty
twenty
hundred
UTC,
the
diagnostics
meeting-
is
also
tomorrow,
one
hour
after
the
tsc
meeting.
So
a
2100,
UTC
and
I
believe
all
of
these
meetings
are
streamed
on
the
YouTube
channel.
Is
that
right,
everybody.
B
J
Well,
I'm
happy
to
do
it
so
basically
there's
an
in-person
vm
summit.
We
had
one
at
the
last
note
interactive.
The
two
main
things
that
we're
tracking
at
this
point
is
is
the
first
one
is
the
work
on
the
stable
ABI
module
API.
So
we're
going
to
be,
you
know
doing
an
update
on
where
we
are
on
that
it,
the
last
one.
J
It
was
discussed
that
we
would
likely
put
it
into
master
in
time
for
v8,
we're
sorry
for
node
version
8,
and
so
it's
a
checkpoint
to
review
that
agree
that
we're
still
on
that
on
that
track
and
get
it
in
the
other.
Major
thing,
that's
being
tracked,
is
the
work
that
alley
and
team
are
working
on
in
terms
of
FF,
I
and
so
I
think
we'll
get
an
update
on
that
as
well.
A
D
L
It's
worth
just
a
filling
some
avoid
here
worth
pointing
out
to
listeners
that
we
have
a
formal
nomination,
24
Francisco
who's
joining
us
as
an
observer
here
to
join
the
CTC.
Let's
issue
number
one
1488
so
she'll
be
joining
us
is
observed
for
another
couple
of
weeks
before
we
finalize
the
vote
on
that.
So
welcome
consistent.
Thank.