►
From YouTube: Core Implementations 2019-09-16
Description
Description: https://github.com/ipfs/team-mgmt/issues/992
Notes: https://cryptpad.fr/code/#/2/code/edit/cOh5BpUBXwTyo76BG22OhI3L/
A
Hello,
everyone
welcome
to
the
Monday
September
16th
core
implementations,
weekly
sync
woot
I
am
facilitating
since
Alan
has
a
brand-new
baby
who
is
super
cute
baby,
no
name,
we're
very
excited
to
meet
baby,
no
name,
and
even
it's
even
birthday,
and
he
is
interested.
So
it's
a
it's
a
happy
day
for
everybody.
A
B
Sure,
well,
there's
no
piston
pastor!
This
is
going
to
be
a
new
release.
It's
been
a
very
quick
one
to
fix,
build
issues
ongoing,
but
one
three
and
I
believe
it
may
also
be
some
publishers.
It
won't
buy
one
two,
two,
two
upstream
disappearing
when
certain
kids
is
had
same
issue
with
the
last
police
ever
since
one
so
yeah
there'll
be
a
new
release
to
fix
issues.
That's
it.
C
Yes,
I've
been
in
really
central
this
week,
so
remote
been
running.
Our
tests
against
the
test
were
running
the
new
RC
against
tests
of
a
bunch
of
repo,
so
we
started
with
internal
repos
and
they
were
all
great
and
then,
of
course,
is
a
party
we
fell
over,
which
is
great
because
we
found
otherwise
wouldn't
affirm
until
after
release.
So
that's
cool,
so
I've
been
looking
into
that
yeah.
C
It's
a
difference
in
how,
because
we
upgraded
to
node
fetch
and
there's
something
different
around
that
than
how
you
send
requests,
because
if
it's
wait,
I
wait
for
Jes
dozen.
What
you
got
is
tedious
anyway.
So
looking
into
that
more
opened
a
bunch
of
issues
on
a
whole
bunch
of
third-party
repos
to
say:
hey,
join
the
early
release
program
so
that
we
can
like
get
basically
get
them
to
do.
What
I'm
doing
right
now.
C
Yeah
just
trying
to
automate
everything
so
I
added
running
the
intro
test
to
the
build,
so
they
now
run
on
every
PR,
which
is
going
to
be
interesting,
actually
like
running.
All
of
our
interface
test
has
led
to
more
stable
interface
test.
I
fear
this
will
lead
to
more
stable
interval
tests
as
well.
There's
like
a
fringe
benefit.
D
D
But
I
just
sort
of
looked
I
started
like
a
long
term
idea
like
wouldn't
where
all
the
things
that
we
might
possibly
want
to
test.
You
know
like
a
large-scale
environment
and
then
I
sort
of
I
could
look
good.
Look
at
the
ipfs
goals
we
did
early
in
the
year
and
try
to
match
them
up
to
so
that
cluster
them
and
put
them
in
little
buckets
and
I
came
up
with
10
sort
of
different
areas,
and
these
this
is
just
something
right.
They
came
out
of
my
brain
but
I'm,
sorry,
I'm,
sort
of
curious.
D
D
A
The
aim
is
that,
once
we
have
once
we
have
those
tests
up
and
running
it'll
allow
us
to
go
ipfs
through
those
tests
and
validate
that
it
any
changes
that
we
may
continue
to
support
the
network
being
fully
operational
and
hopefully
track
our
improvements
as
we
land
a
series
of
kind
of
outstanding
changes
that
we
think
you
need
good
network
emulation
prior
to
being
able
to
launch
those
publicly
to
all
of
the
the
many
nodes
on
the
network.
The
objective
is
to
you
know.
Our
aim
was
to
get
that
done.
D
C
F
The
initiative
is
closed.
The
PR
in
Jessup
Ephesus
merchants
will
be
released
with
garbage
collection
and
pinning,
and
now
we
have
also
the
config
to
choose
what
the
router
we
want
to
use.
It
floods,
our
gossip
so
in
the
gossip
service,
enabled
by
default
in
GSI
papers,
and
that's
it.
Congratulations.
H
So
that's
that's!
Going
on
there
there's
a
few
PRS
I'm
getting
feedback
from
from
Lupita
P.
There
also
seemed
to
be
some
leaking
go
routines
running
around
in
the
test,
I
one
of
them
over
there.
We
will
probably
run
into
more
I'm
out
next
week
for
the
ICN
conference
and
probably
will
be
putting
together
some
Luka
DP.
It's
an
IPS
like
overview,
slide,
etc.
Things
for
anyone,
who's
interested
and
that's
yeah.
That
is
all
for
now.
A
That's
awesome,
I'm
sure
the
IP
NS
overview
slides
would
be
very
interesting
to
many
people
and
we
should
also
find
a
ways
to
share
those
those
out.
If
you
have
any
recordings
of
the
work
you
guys
do
at
the
ICN
conference
and
putting
them
up
on
YouTube
so
that
people
can
can
view
and
learn
from
them
would
be
super
cool,
cool
migration
to
multi
hash
keys
in
blocks
tour
I
do
not
see
an
atom
or
a
an
Allen
on
this
call.
You
know
the
latest
status.
I
H
Yeah
I
mean
the
rest.
There's
there's
you
know,
I've
been
has
stuff,
which
is
his
ongoing,
should
be,
as
we've
already
talked
about
it,
Dominic's
doing
doing
mount
things
which
I've
been
seeing
some
demos
progress,
some
some
cool
progress
being
made.
So
that's
good
and
hopefully
we
should
be
able
to
just
get
people
to
sing
some
stuff
by
amount,
and
that
would
be
that
would
be
super
nice.
B
B
A
A
I
heard
that
one
all
right,
no
no
updates
this
week,
I
think
there
are
probably
updates,
but
we'll
hear
them
from
Dirk
later
snazzy
stuff,
more
improvements
in
the
works.
Alright,
then
a
sink.
A
waitress
factor
I'll
discuss
someone
going
to
present
on
Allen's
behalf,
while
he
is
taking
care
of
his
newborn
child.
Yes,.
G
Alan
has
put
in
a
ton
of
work
on
the
loopy
async/await
refactor
and
we
are
taking
that
off
his
hands
while
he
enjoys
life
with
new
baby.
So
but
a
few
things
we
just
released
the
lip
p2p
TCP
refactor
update
today,
interface
stream
Luxor's
today,
Libby
to
BM
Plex,
should
be
going
out
either
later
today
or
tomorrow,
and
then
we'll
be
wrapping
up
the
interface
connection
with
all
of
this
we've
been
working
on
the
new
jeaious
Libby
to
be
switch
dial
flow.
G
It's
going
to
be
separating
out
logic
a
little
bit
better
with
an
actual
upgrader
which
is
more
similar
to
how
go
Liberty
works,
and
so
we've
been
doing
all
that
parallel.
So
it's
been
a
little
bit
slow,
getting
everything
together,
but
we're
just
about
over
the
hump.
So
we
should
be
able
to
get
interface
connection
also
out
today
or
that's
the
next
couple
of
days
and
then
we'll
be
working
on
the
rest
of
the
dial
flow
is
that
Molly
is
pulling
up
here.
G
G
Let
p2p
like
the
Gospel
sub
like
chain
safe
team
things
like
that
to
try
to
work
on
making
sure
that
that's
a
smooth
upgrade
for
people
will
also
be
creating,
hopefully
this
week
we're
on
creating
a
contributor
guide
so
that
we
can
have
other
people,
either
internally
or
externally,
help
with
some
of
the
reef
actors,
so
I'll
be
creating
some
guides
for
that,
and
then
eventually,
we'll
create
user
guides
for
people
for
migrating
or
just
using
the
new
async
iterative
streams
going
forward.
So
hopefully
that
will
be
a
much
much
smoother
process.
A
A
Okay,
then,
moving
on
to
design
review
proposals,
Steven
UNIX,
FSB,
V
1.5,
not.
B
I
yeah,
so
if
your
internet,
please
it
by
uni,
meaning
basically
we're
one
point,
some
critical
issues
need
to
fix
or
package
managers
without
having
to
redesign
everything
so
that
we
don't
have
like
rush
UNIX
SB
out
the
door,
because
we
need
these
feature
max
managers.
Yes,
you're
interested
a
martini.
A
J
I
have
a
question
for
the
testbed
endeavour.
Is
it?
Is
it
documented
what
the
choices
around
containerization
like?
What
for
how
hurt?
What's
the
I'm
interested
in
the
process
we
get
to
from
here
is
a
tested
image
that
is
provably
working
better
than
the
previous
release
of
go
activist
and
how
I
ingest
that
in
the
gateway
infrastructure,
so
we
can
start
to
work
towards
deploying
the
images
that
we
test.
D
I
think
that's
interesting
like
what's
like
sort
of
like
gets
to
like
what
the
dashboards
look
like
and
how
does
it
look
in
there
a
CIA
test?
Yes,
you
know
we
have
all
these
unit
tests
and
things
that
run
on
the
single
mode,
but
then
we
also
want
to
test
things
with
run
these
things.
Cluster
type
tests,
yeah.
F
D
J
B
D
B
Some
context,
I,
believe
the
the
images
should
spit
out
that
results
in
2d
Jason
from
on
standard
out
yeah
well
be
dumped
into
in
foxy,
be
the
nodes
will
be
control
points,
probably
using
Redis
we're
building
some
libraries
around
this
to
make
it
easier
to
use
for
tests
that
you
think
you
were
to
run
on
like
one
or
two
machines.
This
is
less
important,
just
like
most
advanced
you
if
they
handle
things
like
hundred
or
thousands
of
nodes,
yeah
didn't.
J
They
dedicate
yeah
yeah.
It
would
be
nice
to
create
some
images
as
part
of
the
testbeds
project
that
bacons
configurations.
That
is
mostly
the
same
as
what
we
would
want
to
run
on
the
gateways
so
that
we
have
some
test
scenarios
that
tests
how
this
will
run
in
the
gateways
without
having
to
run
it
on
the
gateways
which
is
currently
where
we
do.
Most
of
our
testing
and
I'd
like
to
move
slowly
away
from
that
and
to
start
to
receive
well
tested
images
with
configurations
that
we
just
deploy
to
the
Gateway.
B
Believe
each
physical
machine,
own
bug,
Orchestrator
docker
image
and
then
other
Cocker
images
running
on
top
of
that.
So
the
other
documents
could
be
like
the
default
gateway
emitters
and
then
the
orchestrator
one
controller
I
think
we
can
do
that.
I'm,
not
sure
we
may
have
to
do
some
layering,
where,
like
we
start
with
like
a
gateway
image,
then
add
a
few
things
on
top,
but
that
with
run
we're
all
about.
J
A
Yawn
Jill,
okay.
Well,
then,
everyone
add
your
weekly
update
to
the
bottom
so
that
people
can
+1
and
and
see
all
the
cool
stuff
that
you're
doing
and
yeah.
Hopefully
we
have
a
design
review
coming
this
week
and
a
lot
of
exciting
things
headed
out
with
the
J
side,
give
us
release,
which
is
super
cool,
assume
Alex,
that
you
would
probably
be
a
good
person
to
add
to
this
unikz
of
us
meeting
as
well.