►
Description
A
B
A
A
B
The
other
changes
being
made
is
now
there's
two
different
objects
between
like
what
the
next
objective,
the
one
that
we
keep
track
of,
or
the
purposes
of
you
know
actual
next
stick
loop
and
then
there's
a
separate
object
that
gets
emitted
to
the
async
research
Huck.
Actually,
when
we
in
it,
so
the
expectation
from
acing
hooks
would
be
that
those
two
resources
one
the
same,
that's
the
whole
point
of
having
a
resource,
otherwise
I,
don't
really
know
why
it
would
be
there.
This
fundamentally
changes
that,
because
now
there's
two
different
objects
that
you
know.
A
B
I,
don't
know
how
people
are
using
it.
I
know
I'm,
you
know,
I'm
I,
don't
think
it's
our
call
how
people
are
using
it,
but
the
resource
is
there
and
the
assumption
and
everywhere,
throughout
the
code
base.
The
assumption
has
held
up
that
those
two
resources
are
one
the
same.
This
be
our
changes
that
makes
them
two
different
objects.
From
my
perspective,
I
don't
think
the
performance
upside
is
worth
the
trade-off
of
deviating
from
well
from
the
precedent
that
we've
established
with
how
a
singles
work.
C
So
it
it
seems,
like
I,
mean
I
put
this
in
the
chat,
but
for
you
know,
because
we're
on
YouTube,
I'm
gonna
just
say
it
as
well.
It
seems
like
we're
at
an
impasse.
You
know
MSC
Dex,
Brian
white
thinks
the
change
should
go
through.
That
has
said
as
much
I
said
that
he's
you
know
said
everything
needs
to
be
said
in
the
tracker.
Anatole
thinks
it
shouldn't
go
through,
has
expressed
the
reasons
here,
but
also
has
said
that
he's
basically
said
everything
that
he
thinks
needs
to
be
said.
C
You
know
in
the
tracker,
so
you
know
this
is
not
necessarily
heading
for
vote,
but
it's
very
likely
heading
well,
somewhat
likely
heading
for
vote
and
I.
Don't
know
you
know
we
can
talk
about
it
more
here.
I,
don't
know
if
we're
gonna
really
get
anywhere,
because
as
long
as
you
know,
because
the
the
real
person
that
needs
to
be
persuaded
is
is
Brian.
A
C
C
A
B
Here's
what
I
guess
I
posted
this
in
the
chat,
but
here's
the
fundamental
thing
that
Sumeet
breaks.
If
you
use
icing
hooks,
you
want
to
wrap
an
X
to
call
back.
So
you
understand
you
know,
maybe
you
want
to
install
some
sort
of
a
wrapper
around
it
to
log.
Whatever
data
is
coming
through
it
with
this
new
change,
your
wrapper
is:
never
gonna
get
invoked.
B
B
E
A
C
No,
let's
post
the
snippet
and
see
if
that
persuades,
Brian
or
if
he
has
a
response
to
it,
that's
persuasive
in
the
other
direction.
Let's
as
long
as
as
long
as
there's
conversation
happening,
let's
let
it
play
out,
but
if
Brian
Ryan,
if
Holly
wants
to
call
for
a
vote,
that's
fine,
but
the
TSC
needs
to
pretty.
You
know,
there's
there's
no
rush
on
this.
There's
no
reason
this
has
to
happen
this
week
and
said
the
next
week
or
something
so
I
would
say.
Let's
let
the
conversation
play
out.
A
D
D
D
D
Comic-Con
flag
couldn't
show
that
this
piece
code
that
is
not
and
to
be
a
partial.
Before
the
quest,
and
apart
from
what
I
said,
there
are
also
some
cigars
that
make
this
T
not
usable
from
libraries.
It
is
it
targets
only
the
top
level
application.
It
will
throw
J
if
it
is
called
from
node
models
and
if
it
will
throw
if
it
is
called
more
than
once,
I.
D
D
G
G
G
It
would
be
interesting
to
to
like
also
think
about
if
we're
you're
going
to
go
with
that
kind
of
approach.
How
applicable
is
with
other
API
is,
for
example,
like
some
people's
deployments
have
when
I've
run
into
this
too
can
have
issues
with
applying
sealife
flags
to
to
node
so
which
I
guess
is
part
of
the
the
idea
behind
this,
and
maybe
extending
that
to
more.
D
G
Just
this
would
be
helpful
and
maybe
that
would
be
a
that
might
be.
Obviously
that
would
be
more
work,
but
it
might
be
a
less
controversial
pot,
for
example,
as
people
are
saying
well,
this
should
be
a
command-line
option,
which
I
kind
of
agreed
in
a
sense
I
do
think
there
should
be
a
command-line
option
with
it
because
it's
got
sort
of
functionality,
but
then,
if
there's
a
way
to
you
know
properly
set
command-line
options
only
from
the
top-level
module
etc.
You
know
where
they
can
be
set.
G
D
A
D
G
G
Well,
I
guess
that
I
guess
the
process
thing
is
is
only
for
things
that
really
deal
with
like
the
processes
is
only
operating,
but
maybe
like
processed
up
higher
than
buffers
would
make
a
little
bit
more
sense.
Actually,
then,
buffer
hardened,
maybe
not
I'm,
not
really
sure,
like
it's
just
a
thought
of
okay.
What
what
else
could
we
apply
this
thinking
to
so
that
it's
not
the
only
thing,
if
that's
kind
of
like
the
objection,
because
I
don't
think
that's
really
been
thought
about
before,
and
that's
definitely
something
that
has
run
into
I.
G
D
The
relationship
between
process
and
buffer
models
and
I
think
match
usual,
but
models
could
have
similar
apiece
for
the
edge
separately
and
one
more
thing
that
I
did
not
mention.
This
applies
only
to
one
office
that
is
correct
and
II.
For
example,
it
does
not
automatically
apply
to
chair
process
created
by
the
same
process
and
so
any
child
process
that
is
called
by
this,
which
applied
edge,
call
itself,
I
thought
about
propagate
Jeanette
for
child
cross,
but
that
is
more
complex
and
each
coach
should
reduce
some
baggage.
So
I
don't
want
to
do
this.
A
G
G
Mean
child
processes
inherit
the
command-line
option?
There's
not
that
doesn't
so.
If
we
make
something
that
applies
a
command-line
option
or
something
similar,
he
doesn't
need
to
actually
beat
the
cran
line.
But
like
applies
of
the
functionality
of
options,
that
would
otherwise
be
there,
because
you
know
having
people
tamper
with
them
in
node
modules
and
stuff
could
cause
unwanted
side-effects.
D
I
call
it
work
on
all
these
folks
with
workers,
but
once
again
about
the
commander
allenford.
My
vision
of
the
Commonwealth,
like
his
son
flight
required
hardened
equals
buffer,
so
sometimes
edge
will
require
a
buffer.
The
hardened
called
in
in
the
first
week
of
the
process,
and,
if
does
not
happens,
it
will
crash
the
causes
and
let
into
a
group
of
H.
So
both
your
cousin
will
have
to
be
energy
applied
to
heat
process,
I
mean.
G
G
D
D
A
A
Okay,
if
not
we'll
move
on
to
the
next
items
on
the
agenda,
the
next
one
is
nominating
that
Beth
great.
So
there
has
continues
to
be
some
discussion
on
how
we
might
address
numbers
and
caps,
but
there's
no
update,
I,
don't
think
in
terms
of
what
we're
gonna
do
next
on
that
anybody
else,
I'm
making
that
on
that
one!
Okay.
A
If
not,
the
next
issue
is
the
tracking
super
updating
TC
on
board
meetings,
so
the
board
meeting
was
held
last
Friday.
The
next
meeting
is
August
23rd.
So
just
keep
that
in
mind.
If
there
is
anything
that
do
you
want
me
to
bring
to
the
board,
because
some
lead
time
is
good,
all
just
some
of
the
highlights.
There's
two
new
foundation,
members,
Vincent
and
sauce
labs,
who
both
joined
at
the
Silver
level,
I've
added
the
link
for
the
public
recording
of
the
meeting.
A
If
you
want
to
reach
that
there
was
an
update
on
the
note
plus
GS
interactive-
and
you
know,
the
CFPs
are
still
on
track
for
being
announced
today.
So
we
should
be
seeing
those
go
out.
There's
data
on
the
transition.
You
know
basically
the
the
bringing
of
the
two
foundations
you
know
in
the
key
update
that
was
given
is
that
CPC
is
operating
regularly
and
that
you
know
working
on
key
policies.
A
As
part
of
that,
if
you're
interested
sorry
one
of
the
other
things
that
has
been
done
since
the
last
board
meeting
and
update
was
on,
is
that
there's
been
an
addition
of
links
for
participation,
so
there's
now
https,
open
gsa,
org,
slash
collaboration
and
that's
intended
to
provide
entry
points,
so
you
know
pointers
to
the
repos
to
the
and
all
that
kind
of
stuff.
So
if
you
take
a
look
at
that
and
see
anything,
that's
missing
that
would
be
good
to
bring
to
people's
attention.
A
A
The
other
thing
that
was
mentioned
was
that
there's
some
discussion
of
the
travel
fund
and
there's
a
proposal
currently
being
worked
at
stage
zero,
which
the
very
initial
like
hey.
Let's,
we
have
an
idea
of
something
we
might
do.
It
still
needs
to
go
through
stage.
One
two
and
three
before
it
would
be
adopted
so
still
expect
loss
of
discussion,
and
you
know
once
that
lands
a
stage.
A
A
Okay,
it's
not!
Let's
move
on
to
that
I
guess.
The
other
thing
I
should
mention
on
that
front
says:
I
did
move
our
project
board,
which
we
had
into
the
TSC
repo
for
issues
to
be
taken
to
the
board
and
I've
moved
it
over
to
the
admin
we've.
Also,
if
you're
looking
for
that,
that's
where
it
is
now
moving
ørsted
to
mr.
teaching
instruments.
A
A
A
H
Progressing
implementation
is
there
there's
quite
a
good,
so
he's
a
checklist.
If
you
want
look
at
the
issues,
listen
to
the
creep.
Oh,
it's
just
making
progress
tracking
the
spec,
its
pre,
damn
complicated
implementation,
and
you
know
plus
there's
something
that
I'm
doing
there
to
you
know
to
ensure
we
get
absolute
best
performance.
Most
of
the
effort
has
been
kind
of
figuring
out
how
to
work
around
the
existing
and
limitations
in
the
neck
and
in
the
noticing
sure
we
kill
performance
there.