►
Description
A
B
Was
on
vacation
last
week
of
this
week,
I've
started
going
through
the
egg.
My
script
spec
changes.
We
need
four
modules
and
that
is
going
to
be
rough,
but
we're
doing
it.
C
B
D
E
F
C
So
a
couple
PRS
around
the
users
or
experience
with
the
debugger,
how
I'm
also
trying
to
figure
out
how
we
include
guides
with
the
API
Doc's
I
know
we
gotta
fix
the
build
script
a
little
for
that,
so
I've
been
looking
into
that
I'm
actually
off
this
week,
so
I'm
doing
a
little
less
than
usual.
Next
is
Michael
Dawson.
G
Great,
so
is
offer
complete
on
vacation.
It's
a
code
coverage
nightly
job
at
a
PR
to
document
that
miscellaneous
issue
review
comments,
lands
the,
maybe
I
stable,
no
discussion
and
work,
and
there's
a
number
of
benchmarking
issues
that
I
took
an
initial
look
at
that
off
to
get
back
and
do
a
little
bit
more
on
as
well.
Next,
it's
balloon.
A
Nothing
nothing
really
significant
this
week.
Next
is
Brian.
I
H
J
K
Yep
I'm,
just
in
the
middle
I,
think
so
yeah.
So
back
from
being
away
I
see.
58
is
going
ga
end
of
this
week,
so
I
will
be
updating
78
44,
I
don't
know
if
I
have
a
PR
for
that,
yes
or
not,
but
anyway,
it'll
be
it'll,
be
there
and
also
I
did
back
forward
what
did
I
back
port
and
so
have
Asif
occasion,
I
backported
the
break
iterator
crash,
so
don't
crash
with
Greg
iterator
thing:
oh
I'm,
ee
ee
entered
here,
but
anyway,
yeah
I
backported.
L
A
A
A
A
A
The
time
to
do
so
is
like
now
so
coming,
and
I
don't
know
that
there's
anything
to
discuss,
but
I
believe
I
will
leave
I'll
stop
talking
for
a
few
seconds
in
case
people
have
things
they
want
to
say
about
it,
but
really
quickly.
The
the
hope
for
end
result
is
more
decisions
that
can
be
made
in
the
issue.
Tracker
will
be
made
in
the
issue
tracker
and
we'll
have
you
know
only
meet
things
that
have
to
be
in
meetings
talked
about
in
meetings.
A
E
E
A
E
Like
to
land
it
in
seven,
I,
don't
know
if
that's
going
to
be
possible.
At
this
point,
though,
and
a
chopper
said,
the
Nikita
said
that
there
were
three
there's
one
package:
that
there
were
three
instances
of
the
error
message,
but
it
looks
like
a
copy
of
the
HTTP
outgoing
pod,
but
he
did
say
that
he
needed
to
sync
the
data
set
in
recheck.
F
E
Yeah
not
have
been
at
expressed
some
concerns
regarding
whether
this
could
lead
to
like
an
information
leak.
If
the
header
name
is
attacker
control,
so
guys
like
I,
said
it's
not
that
complicated
of
an
issue,
but
you
know
if
everybody
could
kind
of
chip
in
on
how
they
feel
about
it.
It's
just
something
that
we
ran
into
and
was
difficult
to,
diagnose,
which
headed
up,
which
header
was
the
problem.
A
A
E
In
the
chat
in
this
chat
for
Hoover
conference,
there's
three
hits
and
the
package
name
is
HTTP
dash
node
and
it
looks
like
it's
just
the
under
for
HTTP
underscore
outgoing
doc
Jes
file
from
live,
but
did
again
makita
said
they
needed
to
sync
to
get
the
latest
data
set
as
well.
So
I
don't
know,
maybe
a
possible
workaround
could
be
to
add,
add
like
a
debug
statement
in
there
before
the
throw.
Then
it
wouldn't
actually
change
the
error
message.
Not
maybe
that
could
be
a
compromise,
because
that
would
make
it.
H
G
A
L
A
Okay
sounds
like
there's
a
short
term
resolution
on
that
and
then
the
longer
term
conversation
can
continue
in
the
issue
tracker
and
then
James
added,
oh
I'm,
sorry
yeah,
I
yeah
so
I
I
said
the
last
one
was
the
net
module,
but
that
was
Evan
correctly
pointed
out.
That
was
the
HTTP
module.
I
read
the
wrong
description,
James
added
the
multiple,
listen
events
fail,
silently
take
away.
James.
F
F
J
A
Sounds
like
no
okay,
so
meaning
no.
Nobody
wants
to
comment
at
this
time,
not
now
on
that
change.
So
last
issue
on
the
agenda,
unless
somebody
has
something
they
want
to
add,
is
from
the
tsc
repo.
It's
issue
number
146,
consider
folding
the
tsc
into
the
CTC
rod,
put
it
on
the
agenda.
He
can't
make
it
today
is
not
here
and
I.
Don't
think
there
was
any
decision
to
be
made.
He
just
wanted
that
make
sure
the
CTC
had
the
conversation
I'm
happy
to.
A
Let
people
talk
about
this
as
much
as
they
want
to
I'm
of
the
opinion
that
I,
don't
really
have
anything
to
say
that
can't
be
said
in
the
issue
tracker
at
this
time
and
I
think
that
we
probably
want
this
eye
on
until
rod
until
rod
is
around.
So
we'll
probably
just
have
the
conversation
again
when
he's
here,
but
that's
not
necessarily
a
reason
not
to
talk
about
it
now.
If
anybody
has
anything,
they
want
to
say.
A
I
A
Right
there
was
something
from
miles
he
wanted
to.
He
wanted
there
to
be
a
conversation
around
v6
91.
He
doesn't
say
what
I
don't
think
other
than
whether
we
should
try.
I'm
thinking
he
probably
wanted
us
to
express
opinions
about
whether
it
should
be.
We
should
try
to
have
the
release
this
week
or
next
week.
I.
G
F
E
A
So
I'm
going
to
I'm
going
to
unless
somebody
thinks
they're
going
to
want
to
dive
in
on
this
right
now,
I'm
going
to
suggest
that
we
just
make
sure
that
if
you
actually,
you
know
since
miles
was
asking
about
it
if
we
want,
if
you
want
to
make
sure
miles,
you
know
sees
it
put
your
comments
in
that
issue
and
we
probably
don't
need
to
have
the
conversation
here.
Anything
else
on
that,
just
in
case
I'm
wrong
about
that.
C
Just
wanted
to
bring
up
89
78,
where
we
were
discussing
a
bit
than
the
hint
text
that
comes
when
you
run
node
with
the
inspector
am
and
I
brought
up
there,
switching
to
the
just
a
URL
to
the
web,
sockets
and
I
think
we
were
going
back
and
forth
on
the
issue
about
whether
the
time
to
remove
the
URL
into
chrome,
devtools
might
be
now
or
whether
it
would
be
later,
perhaps
around
55,
so
I
just
wanted
to
bring
that
up.
Because
today
is
the
last
day.
C
Don't
think
so
it
would
be
just
the
technicals.
The
standard
error.
F
F
E
E
J
Don't
think
there
should
be
an
urgency
to
change
the
URL
I
do
think
it's
it's
a
good
change
down
the
road,
but
let's,
let's
give
the
ecosystem
and
the
debugging
tool
some
some
time
to
catch
up
and
provide
a
good
user
experience,
because
making
this
change
now
makes
it
harder
to
debug
things,
and
people
have
to
go
figure
out
how
to
connect
so
I
would
prefer
keeping
it
at
it.
As
is
and
I,
don't
think,
there's
an
urgency
here
that
we
must
do
it
before
v7
or
be
71
or
anything
of
that.
G
C
A
A
A
They're
gone,
they
were
here,
okay,
no
all
right
right,
so
upcoming
meetings,
let's
hear
so
next
CTC
meeting
will
be
one
week
from
today
on
october
26th.
It
will
be
nine
a.m.
pacific,
of
course,
I
know
pacific
time,
because
that's
where
I
am,
that
probably
doesn't
help
everybody
else
too
much,
but
anyway,
tsc
meeting
is
tomorrow
right
or
yeah
tomorrow
at
so
look
that
up
and
yeah
that's
the
same
time
as
this
meeting
yeah.
A
So
in
about
23
and
a
half
hours
diagnostics
working
group
is
going
to
have
a
meeting
the
first
week
of
November
and
no
other
meetings
are
listed.
I'm
pretty
sure,
there's
a
build
workgroup
meeting
on
Monday.
Okay,
so,
let's
see
do
we
have
any
questions.
Some
in
the
YouTube
comments.
Michael!
Very
you
don't
look
very,
very
not.
A
A
A
Okay,
all
right,
I'm,
not
seeing
any
questions
so
I'm
just
going
to
move
on
I!
Think!
That's
it
we're
done.
Aren't
we
all
right?
This
has
been
a
wonderful,
wonderful
meeting
experience.
Thank
you
all
for
being
part
of
it.