►
Description
C
Hey
so
I've
done
a
few
things
this
last
week,
I
spent
some
time
reviewing
changes
screen
stocks
PR,
which
is
looking
good
I'm
gonna,
probably
do
another
round
on
that.
At
the
end
of
the
week,
maybe
today
and
roughly
defined
that
defined
as
like
the
last
half
of
the
week,
doing
some
catching
up
on
the
zones
proposal
just
to
wrap
my
head
around
it
a
bit
and
looking
at
the
streams
read
into
proposal,
problem
pewter
and.
D
F
Hello
I
spent
most
of
my
time
continuing
to
investigate
standard
I/o,
woes
potential
fixes
and
problems
along
the
way,
different
platform
things
and
also
have
been
having
problems.
Testing
t
y
is
for,
though,
those
issues
also
done
some
general
issue.
Pr
review
and
made
a
couple
minor,
cember
minor,
pull
requests.
G
H
Yep,
that's
a
PR
triage
/
docs
were
also
can
in
the
background
working
on
some
URL
module
recurring
see
if
we
can
get
some
improved
alignment
with
the
Ural
standard,
having
a
semesters
getting
that
alignment
without
impacting
performance,
so
I'm
still
kind
of
looking
into
private
militia.
That's
move.
Next
is
Josh.
I
J
L
Ok,
alexis
is
having
trouble
unmuting.
So
not
let
me
be
dumped
in.
A
A
M
We'll
come
back
to
you,
then
Seth
Thompson
hi,
guys
I'm,
along
on
the
note
inspector
work
as
well
with
Ali
and
pas
a
hole
on
a
chrome,
devtools,
teen
and
and
actually
at
last
week
was
the
google
I/o
conference
and
we
gave
a
quick
demo
of
functionality
in
the
devtools
talk
and
the
v8
talk.
So
I'm
excited
to
talk
about
that
today.
B
Okay,
I
think
I'm.
Next
I
do
you
think
we've
got
Ben
and
Steven
Loomis
of
Julian,
so
I
love.
This
want
to
attack
them
on
at
the
end,
but
I
I
on-boarded,
a
bunch
of
people,
Brian,
English,
yuva,
brick,
staying
a
Wang
and
Bradley
I
do
want
to
make
one
a
note
about
how
the
onboarding
went.
B
Alexis
you
got
unmuted,
congratulations,
cool,
oh
okay!
So
we'll
go
back
to
your
after
I
finish
up.
I
guess
I
I
boarded
Brian
English
in
person
because
we
happen
to
be
in
the
same
place
at
the
same
time
on
saturday
and
then
I
was
going
to
on
board
everybody
else
on
google
hangout,
but
the
only
person
for
whom
it
really
worked
was
yuval,
so
rescheduled
with
with
firefox
Daniel
one
rescheduled
with
him
for
last
night
on
IRC,
and
that
seemed
to
work
perfectly
fine.
B
But
if
there's
any
concerns
about
you
know,
I
mean
I
would
prefer
to
onboard
people
in
a
more
personal
way
where
there's
voice
involved
and
so
on
so
forth.
But
you
know,
rather
than
tangle,
with
the
Great
Firewall
of
China.
We
just
went
to
IRC
and
I
think
that
that's
perfectly
acceptable,
but
if
anybody
has
concerns
about
that
for
some
reason,
please
feel
free
to
voice
them
been
fixing
a
bug
in
child
process.
B
Exec
mostly
I've
been
just
doing
inadequate
solutions
that
Brian
White
then
comments
on
and
I
fix
them
and
then
eventually
I
get
to
a
good
solution.
So
you
could
say
he
actually
did
most
of
the
work,
but
whatever
and
also
adding
lots
of
ya
moul
stuff
to
dot
md
files
saying
when
api's
have
been
added.
B
O
O
P
Is
this
thing
on?
It
is
okay,
excellent,
so
code
reviews,
of
course,
I
fixed
couple
of
minor
bugs.
If
you
start
node
with
the
death
at
how
many
Cindy
now,
then
simply
dives
gets
pretty
printed
in
the
repple.
So
that's
very
nice
just
same
old
same
old,
oh
yeah,
a
couple
of
Libya
v
bug
fixes
that's
yeah!
That's
about
it!
For
me!.
A
N
A
N
They're
not
working
at
HTTP
because
they
rely
on
WR
k,
which
is
a
tool.
That's
not
ported
it
on
windows
and
child
process.
They
just
had
some
bugs,
but
yeah
they
did
the
biggest
one.
Is
the
HTTP
one
really-
and
there
is
a
bit
of
controversy
about
replacing
our
proposal
solution
was
to
replace
w
arcade
with
a
patch
bench,
but
the
results
might
not
be
exactly
the
same,
even
though
they
seem
to
be
consistent.
Over
still
evaluating
I
mean
the
other
option
would
be
too
poor
to
make
a
fourth
wrkng
bv.
F
N
N
F
Q
Yeah
yeah
I
just
got
back
from
China
and
its
kind
of
catching
up
on
male
and
a
bunch
of
legal
stuff.
I
heard
your
comments
about
dealing
with
the
firewall
and
whatnot.
So
now
that
we
have
a
contributor
in
China,
I
would
suggest
kind
of
trying
to
get
them
up
to
date
as
quickly
as
possible,
so
they
could
actually
on
board
other
people
in
china
because
just
what
the
time
difference
it's
hard
enough
and
there's
just
like
for
communications
and
stuff,
there's
just
a
whole
nother
set
of
tools
to
deal
with.
H
Q
A
Okay
review
of
previous
meeting
and
please
holler
if
anything
stands
out
as
something
we
need
to
discuss
as
a
follow-up,
we
reviewed
es
modules
stuff
again
and
that's
an
ongoing
thing.
I
believe
Jeremiah
is
up
to
speed
with
Bradley
on
that
and
there's
still
some
continuation
of
that
we
don't
have
Bradley
this
week.
Is
there
anything
you
want
to
feel
thing
on
Jeremiah.
F
So
what
we're
now
investigating
is
how
to
deal
with
a
PM
vendors
or
other
developer,
usually
testing
tooling,
that
hooks
into
the
module
system
to
either
wrap
modules
or
similar
things
like
that.
And
that
is
very
hard
to
do
with
these
modules
and
they
were
very
much
designed
to
not
do
that.
But
we
kind
of
need
that
capability.
So
we're
investigating
that.
A
Next
week
looked
standard,
I/o
woes
and
we
will
be
getting
to
that
again
this
week,
so
we'll
jump
over
that
one
moving
sink
right
stream
to
internal
FS,
I
think
we're
going
to
go
ahead
and
do
that
deprecated
and
the
graceful
FS
issue
as
well.
We
discussed
and
I
came
up
with
a
resolution
for
that
which
I
don't
quite
remember.
I
think
it
was
putting
it
off
until
version
7
or
something
okay.
A
K
Right
so,
as
per
the
collaborator
guide,
any
changes
that
are
significant
enough
to
have
an
impact
to
know
they
should
be
brought
up
at
the
CDC
meeting.
So
that's.
Why
added
the
ctc
gender
label
I
Madrid,
so
there's
a
healthy
discussion
on
the
pull
request
as
well,
and
that
can
continue,
but
the
CDC
should
be
arraigned
on
whether
this
is
a
direction
that
node
is
interested
in
and
and
what
is
the?
What
is
the
goal
posts
that
we
need
to
achieve
in
order
to
get
this
landed?
K
So
in
fact,
actually
rod,
possibly
posted
a
really
good
summary
of
the
things
we
should
consider
some
of
the
questions
he
posted
about
this
post,
a
link
to
this
in
the
chat
here
and
we
can
run
through
the
issues
that
rod
mentioned
in
daughter.
You
mention
it
so
and
any
other
issues
of
the
CTC
remembers
want
to
bring
up
as
well
on
this.
So
so,
basically,
that's
a
discussion.
I
think
we
should
have
so.
K
Okay,
so
so
the
main
concerns
that
I
think
not
raised
was,
first
of
all,
it's
a
it's
a
rather
large
dependency
and
actually
there's
two
questions,
it's
large
and
secondly,
in
in
a
future
v8
version
it's
going
to
be
subsumed
into
v8.
So,
whether
or
not
we
should
be
carrying
this
dependency
and
the
way
I.
Look
at
this
question
is
it's
it's
a
question
of.
K
K
K
A
O
Well,
I,
guess:
okay,
so
I
look
at
it!
I
guess
the
response
was
basically
oh,
it's
pretty
much
easy
to
write
a
protocol.
You
know
like
a
script
I'll
handle
at
vertical.
Well
then,
if
it
is,
why
don't
we
support
it
in
mode
and
with
the
existing
debugger
protocol,
I
mean
you
need
to
write
the
parser
or
whatever,
but
it
still
just
uses
normal
protocol
that
our
support
right
there's
a
difference
between
like
API
protocol
right.
P
F
I
have
a
quick
question
on
the
snow,
so
if
we
were
to
go
the
road
and
say
well,
we
want
to
include
a
WebSocket
protocol
thing
with
this.
That
would
probably
be
written
in
JavaScript
like
net
and
HTTP
are
mostly,
but
this
is
written
in
C++.
Would
we
still
have
to
maintain
both
things
or
could
it
just
all
be
in
JavaScript
them
so.
K
In
the
future,
if
90s
decides
to
have
the
pockets
implementation,
whatever
that
implementation
is,
we
could
make,
then
the
inspector
interoperability
work
on
top
of
that
implementation.
So
so
this
is
not
going
to
be.
This
is
just
a
subset
of
web
sockets
that
we
needed
to
talk
to
the
inspector
actually.
R
My
name
is
Paul.
I
was
commenting
on
the
request.
One
thing
to
add
is
that
we
need
to
be
really
careful
with
running
JavaScript
at
the
inspected
target
in
the
node
that
is
being
inspected,
because
debugger
is
going
to
debug
and
profile
that
running
code
and
what
we've
learned
while
working
a
clone
is
that
the
entire
infrastructure,
including
transport,
needs
to
be
native
to
not
stand
in
the
debuggers
way,
as
you
are
debugging
and
inspected
instance.
R
F
K
A
G
A
K
I
think
it's
actually
fine,
because
it
allows
us
it
allows
it
provides
an
easy
way
for
people
to
test
it
out
without
mean.
The
current
state
is
that
there
is
a
polar
questions
already
hard
for
it's
harder
for
people
to
pick
up.
The
master
branch
apply
the
pull
request
on
top
of
it,
and
then
they
can
play
with
this
weather
inspector
makes
it
easier.
I,
don't
see
a
lot
of
downsides
but
feel
free
to
target.
K
I
think
that
the
the
one
thing
that's
missing
at
the
moment
we
did
add
smart
with
support
as
well,
so
I
think
it
should
work
a
smart
to
us,
but
Windows
is
pending
at
this
point.
So
it's
I
think
at
some
point
in
the
future
near
future.
We
can
turn
it
on
by
default,
but
this
allows
us
to
interoperate
and
collaborate
better
until
even
windows,
support
is
enabled
and
other
features
are
added.
It.
I
K
K
If
people
think
that's
a
good
idea,
but
the
right
now
I
think
the
windows
will
not
pass
in
the
sea
I
if
we
drop
the
flag
and
we
haven't
had
the
chance
to
go
deeper,
that
it's
not
it's
not
going
to
be
difficult,
we're
not
far
away
from
it,
but
it
getting
here
so
either
way
getting
admitted
make
it
easier
to
to
get
help
from
other
people.
Looking
at
window
specific
issues
too
yeah.
S
P
H
O
So
what
you
were
the
vm
summit
senior
right-
and
I
remember
them
saying
that
the
comments
at
all
e
how
they
had
the
debugger,
mostly
working
and
then
all
he
responded,
are
asked
in
response.
Wouldn't
they
had
light
code
editing
working
in
they
said
they
hadn't,
but
as
far
as
I'm
first
know,
this
doesn't
enable
white
hooded
note
either.
Does
it.
O
I
O
R
G
N
I
I
R
We
can
look
a
retrospective
Lee
in
into
how
debugging
protocol
was
defined
and
how
it
evolved
over
the
years.
It
was
originally
introduced
in
2010
and
we
haven't
broken
the
backwards
compatibility
since
then
for
the
runtime,
debugging
and
other
domains.
So
we
are
very
optimistic
in
our
abilities
to
keep
it
going
this
way
and
only
add
capabilities
in
a
backwards
compatible
manner.
There.
A
K
R
The
way
it
works
in
chrome,
for
example,
is
that
the
prodigal
exposes
several
domains
and
the
ones
we
think
are
applicable
to
note
hour
run
time.
Debugging
profiler
and
heap
profiler
with
console
following
up
tracing
is
yet
another
domain
in
chrome
and
the
way
you
control
tracing
his
you
to
the
chasing
you
issue,
tracing
start
command
and
tracing
stop
command
and
you
get
results
and
you
process
them.
So
as
far
as
the
automation
is
concerned
and
controlling
things
over
the
same
wire
remove
debugging
protocol
is
the
official
channel
into
the
chasing
for
the
automation
purposes.
A
K
A
The
the
other
questions
I
had
were
fairly
easy,
I
think
to
resolve
in
that
thread,
the
other,
the
the
the
one
that
did
that
probably
is
worth
discussing,
is
the
chrome
part
of
the
URL.
There
was
a
user
in
there
that
was
raising
that
as
a
concern
and
see
any
collaborators
actually
raising
them
as
a
concern.
But
it's
anyone
here
have
concerns
about
having
chrome
as
part
of
the
URL,
given
that
this
could
be
well,
that
will
will
be
used
by
other
do
out.
Debuggers.
Yes,.
F
P
K
Something
is
I,
think
it
I'm
actually
I'm,
actually,
okay
with,
if
not
really
note,
chord
thinks
this
should
be
no
URL
at
all,
I
mean
that
can
work
too.
I
think
at
this
point
the
only
the
users
will
get.
This
working
is
by
pasting
that,
in
a
that,
you
are
in
a
in
a
Chrome
browser
I
think
it's
easier
for
users
to
get
started
with
this.
If
it's
a
chrome,
URL.
R
Can
I
can
respond
to
that
and
I
actually
paste
it
in
a
pretty
expensive,
responding
in
the
trad?
Formerly
we
don't
need
any.
So
we
can,
we
can
just
run
note
inspect
and
it
will
open
the
port
and
that
court
will
listen
to
incoming
connections
and
just
with
that,
visual
city
code
or
chrome,
devtools
or
any
other
client
will
be
able
to
connect.
There
is
no
other
information
required
to
establish
the
connection.
In
order
for
chrome
to
discover
node,
you
will
need
to
restart
chrome
with
a
special
command
line
flag
which
is
optional.
Now.
R
What
currently
is
being
done?
We
just
paste
the
convenience
URL
into
the
prompt
so
that
the
user
could
copy
and
paste
it
into
the
browser.
The
chrome
part
of
the
URL
is
chrome,
specific
because
it
enters.
It
brings
chrome
into
this
sort
of
a
dev
tools.
Note
that
we
need
for
fountain
to
operate,
but
this
is
the
implementation
detail.
They
also
the
this
whole
purpose
of
this
URL.
R
Being
pasted
in
the
console
is
the
ergonomics
and
convenience,
and
this
is
entirely
up
to
you,
whether
you
want
it
or
not,
and
we
will
work
with
just
no
inspect.
There's
no
issue,
but
I
think
it
will
be
more
welcoming
to
the
users
and
more
engaging
for
the
users
to
be
able
to
discover
it
in
such
a
friendly
matter
where
it's
just
a
copy
and
paste
away.
But
that's
your
decision
to
me.
I
Have
you
guys
thought
about
like,
if
you
guys
use
chrome
devtools,
to
indicate
something
to
the
browser,
if
that
was
a
more
standardized
or
or
documented
scheme
like
maybe
other
tools
could
use
it
to?
Maybe
if
we
had
to
go
that
route
like
CDP
cone,
whack
whack
and
a
little.
R
Bit
more
Harrigan,
we
are,
we
are
working
on.
Is
things
that
we
were?
We
have
a
used-book
discovery
over
USB
that
works.
We
have
mdns
based
discovery
working
and
we
have
a
raw
TCP
discovery
working,
but
it
needs
this
additional
command-line
flag.
We
haven't
standardized
on
NE
undha
schemas,
on
top
of
that,
ought
to
be
interesting
to
look
into,
but
that
could
be
done
incrementally,
there's
nothing
that
we
would
have
for
it
add
at
this
point,
I.
M
Think-
and
this
is
Seth
again
just
to
chime
in
really
the
the
printing
of
the
URL-
is
probably
the
just
an
ergonomics
thing
that
can
be
decided,
probably
independently
of
landing
v8
inspector.
It
works
without
the
URL.
Currently,
the
URL
is
the
easiest
way
for
the
user
to
actually
test
this.
If
another
debugger
wants
to
support
the
protocol,
they
could
come
up
with
their
own
schema,
but
I
think
that's
something
to
determine
at
the
sort
of
node
CLI
level,
not
necessarily
the
level
of
this
module,
and
this
capability
yeah
I,
think.
A
A
A
You
know
okay
well,
if
anyone
thinks
otherwise,
then
you
should
raise
that
in
each.
You
know,
because
it's
currently
labeled
as
simpler
minor
and
that's
how
I'll
go
in
unless
anyone
sees
anything
that
might
be
breaking
now.
Let's
move
on
I've
got
a
hard
stop
it.
On
top
of
the
outside,
I
need
to
get
coming
as
well.
A
A
The
next
item
is:
we
need
to
take
some
minutes
by
the
way
if
anyone
would
like
to
start
typing
something's
in
there,
I'm
stedelijk
was
Jeremiah.
Where
are
we
at
with
this
I've.
M
F
You
so
where
we're
at
we
haven't
I,
haven't
really
done
much
with
the
flushing
on
exit
at
the
current
time.
I
think
we're
still
discussing
what
Libby
V,
how
do
that
Ben
might
have
bad
idea
or
anyone
else
that
was
involved
in
that
conversation.
F
P
L
F
Will
it
act
worse
than
the
current
behavior,
though,
because
Mac
has
always
been
blocking
up
until
this
point
and
there
was
not
significant
issues,
and
that
was
because
the
lib
UV
had
some
other
bugs
in
it
that
created
cause
it
to
still
be
blocking,
even
when
we
thought
it
might
not
be.
But
the
current
behavior
causes
pretty
bad
issues
with
co
eyes.
Yeah.
P
F
A
N
F
P
Right,
ok,
yeah,
so
interleaving
is
an
issue
and
always
has
been
I
posted.
The
comment
today,
where
I
outlined
a
possible
solution
on
how
to
address
that
it
will
requires
minor
changes
to
leave
UV
to
make
certain
things
work
with
pipes
on
Windows,
but
once
that
is
working
well,
I
think
we
should
be
able
to
to
fix
both
issues
in
one
go:
okay,.
P
P
So
it
currently
injured
on
a
relatively
small
thing,
and
that
is
that
so
luke
vs,
this
API
called
UV
try
rights
which
well
it
basically
tries
to
write,
and
if
it
doesn't
give
you
an
error
code,
it
doesn't
queue
up
request,
and
so
it's
basically
a
synchronous
right
for
asynchronous
handles
so
far.
So
good
problem
is,
it
doesn't
work
for
pipes
on
Windows.
It
has
to
be
implemented
yet
so
I
had
a
go
at
it
today,
but
well
it
didn't
turn
out
so
pretty.
H
P
N
N
G
I
guess
it's
probably
going
to
be
a
bit
off
alone:
OS
X,
because
of
select
hacks
that
we
have
her.
But
whenever,
okay,
whatever
I,
think.
A
A
F
Yeah,
so
it
sounds
like
everyone's
okay
with
my
temporary
approach:
I'm,
not
sure
how
testing
this
is
actually
going
to
go
or
getting
it
on
the
CI.
So
if
I
get
help
with
that,
that
would
be
great,
otherwise
I'm,
not
sure
it's
going
to
know
you.
A
F
N
A
F
There's
there's
an
actual
issue
for
it.
There's
a
Libya
V
issue
for
the
flushing
that
part
and
then
there
is
a
there.
Three
pull
request
of
mine.
One
is
a
pull
request
for
flushing
on
exit,
which
we
are
discussing
more
in
the
Libya
thread.
But
the
note
parts
are
in
that
PR
there's
a
PR
for
blocking
on
all
platforms
which
I
still
need
to
investigate
and
now
and
then
there's
my
temporary
fix
or
LSX
could.
A
F
A
That
I'm,
okay,
so
I
drop,
but
we
have
QA
urinate
on
the
agenda
Jeremiah,
maybe
if
you'd
like
to
take
over
and
and
when
incubator
comes
in
so
like
a
prior
second
at
the
end,
if
there's
anyone
talk
about
anything
privately
but
for
now,
I
have
to
go
so.
Jeremiah
is
okay.
Young.
F
F
G
F
Well,
I'm
not
sure
we're
going
to
get
anything
I
think
my
comment
is
still
carried
over
from
last
time
in
the
YouTube
shot,
so
I
think
we
can
call
it
on
like
we
might
be
going
to
a
private
meeting
to
get
a
brief
update
but
yeah.
So
thanks,
everyone
who
watched
and
we'll
probably
around
next
week
in
as
usual
thanks.