►
From YouTube: ⚡️ⒿⓈ Core Dev Team Weekly Sync 🙌🏽 March 04, 2019
A
A
If
you
are
here,
please
put
your
name
on
the
happened
in
under
the
attendees
list,
because
we
like
to
know
who
is
here:
I
have
pasted
the
link
in
the
chat,
so
you
can
do
that
and
if
you
haven't
already
and
you're
doing
been
doing
some
work
on
on
Jay
s,
core
FS
stuff,
then
put
down
your
weekly
update
this
week.
I
have
decided
that
if
we
have
time
I'm
glad
to
try
something
that
the
go
team
do,
which
is
this
cross
team
update.
A
So
if
anyone
is
here
from
actually
this,
there
is
people
here
from
other
teams
who
would
like
to
share
an
update
from
their
team,
their
working
group
in
this
working
group.
Then
please
put
down
your
names
at
the
bottom
of
the
list
and
your
your
win
and
or
update
and
will
maybe
get
to
you.
If
we
have
time-
and
you
can
read
it
out
and
tell
us
about
what
you've
been
doing
so
without
further
ado,
let's
get
on
with
it
weekly
updates.
So
what
do
we
do?
A
A
So
that's
good
so
that
took
a
while
taken
all
those
and
what
else
we're
doing
so.
I
had
a
look
again:
the
IPO
API
refactor
okay.
Last
week,
I
did
a
couple
of
interviews
and
a
whole
bunch
of
my
time
got
got
taken
up
with
investigating.
There
is
a
well.
There
was
a
issue
with
the
in
go
bit.
Swap
for
the
preload
notes
that
JSI
BFS
uses
an
image,
ASI
PFS
users,
people
who
are
creating
creating
nodes
were
not
able
to
actually
share
content
with
each
other.
A
What
was
happening
was
the
the
node
was
connecting
to
the
preload
nodes
and
it
looked
like
it
was
sending
want
lists,
but
never
actually
receiving
the
content
from
the
note,
even
though
than
those
definitely
have
that
content
and
I
think
that
has
boiled
down
to
the
fact
that
there
was
another
node,
another
preload
node
spun
up,
which
used
the
same
peer
ID
as
a
as
a
current
one.
So
there
was
to
preload
nodes,
running
and
I
think
the
one
that
was
spun
off
failed,
but
never
got
taken
down
properly.
A
So
those
to
preload
nodes
were
the
same
peer
ID
and
it
was
apparently
messing
everything
up
so
I
think
that's
pretty
much
below
now,
which
is
and
then
so
fun
times
fun
times,
work
that
I've
been
doing
just
basically
every
weekend
to
be
honest,
I
couldn't
find
caveat,
I'm
really
bad
at
googling
for
stuff
I
couldn't
find
a
module
that
would
allow
me
to
map
over
some
content
like
an
iterables
content.
In
parallel
and
said,
like
the
situation,
is,
you've
got
like
a
a
so
some
sort
of
stream.
A
You
want
to
concert
the
consume
from
or
an
iterator,
it's
a
rule
that
you
are
consumed
from
and
that's
coming
in
asynchronously
every
so
often
you
want
to
do
some
transform
with
the
value
that
comes
back.
But
if
you
do
in
like
a
for
away
of
loop,
that's
like
doing
it
in
serial.
So
you
have
to
wait
for
that
operation
to
complete
before
you
start
consuming
the
next
chunk
from
the
thing
and
actually
what
you
want
in
a
lot
of
situations-
and
you
can
do.
A
Is
that
chunk
where
you're
doing
the
transform
you
parallel
eyes
it
and
do
a
whole
bunch
of
them
at
once
and
then
and
then
yeah
anyway.
So
this
module
takes
iterable
and
a
mapping
function
and
here
apply
the
mapping
function
to
each
item
from
the
iterable
in
parallel
and
give
you
back
in
iterable
that
you
can
iterate
over
and
consume
and
it
preserves
the
order.
So,
whilst
all
of
the
async
stuff
will
be
done
in
parallel
and
the
order.
A
A
Some
proper
testing
of
the
DHT
that's
in
there
now
and
I
also
want
to
do
some
more
work
towards
the
async,
iterators,
endeavor
and
and
more
work
again
towards
the
cid
v1
base,
42
encoded
by
default
stuff,
like
I,
think
from
my
perspective
now
areas
what's
left
to
do
is
get
all
the
tests
working.
Basically,
all
your
tests
with
you
build
in
see
IDs
the
strings.
A
That's
that's
kind
of
annoying
for
me,
especially
if
the
the
content
has
is
actually
chunked
into
multiple
bits
of
truck
content,
because
when
we
changed
the
version
of
the
cid
to
be
version
one
by
default,
the
cid,
the
actual
bytes
stored,
get
a
bit
longer,
there's
a
little
bit
more
to
store.
So
the
cid.
A
It's
not
just
a
case
of
converting
the
cid
to
base
30
to
encoding,
because
the
content
has
actually
changed
as
well
of
the
links
of
the
node,
so
yeah,
that's
kind
of
annoying.
So
here
we
go,
it's
gonna
be
fun
science,
but
so
I
need
to
do
that.
But
then
there
is
the
whole
problem
of
like
bits
or
from
the
DHT
using
c
ids
and
they
should
probably
be
using
multi
hashes,
and
I
need
to
look
into
and
resolve.
B
A
C
For
the
for
the
async
iterator
stuff,
like
you've,
created
that
module
and
I
know,
you've
created
a
few
other
modules
and
I
think
who
goes
greats
themself
as
well.
I
think
it
would
be
nice
to
have
maybe
in
the
async
iterator
issue
itself.
To
have
like
a
glossary
of
here
are
the
modules
that
we
have
created
to
make
this
easier
or
modules
that
exists
and
make
all
this
stuff
easier,
so
that
we're
not
recreating
them
if
we
can't
Google
to
find
them
yeah.
A
Yeah
I
think
that's
a
good
idea
and
I
think
that
we
should
also
be
careful
not
to
reinvent
the
wheel
and
just
make
a
lot
of
modules
that
already
exist
and
I.
Think.
If
we
can,
we
should
settle
on
like
a
kind
of
async
iterator
tool,
yeah
I
like
if
people
are.
If
you
have
suggestions,
it
would
be
cool
to
note
them
down
in
the
async
iterators
awesome
endeavor
and
we
can
maybe
pick
one
and
looked
at
the
bundle
size
for
one
of
them.
A
A
D
Please,
yes,
so
I've
been
working
on
the
IP
LD
selectors
thing,
I've
linked
the
current
draft
of
the
spec.
If
you're
interested
also
comments
are
welcome.
If
you
have
any
ideas,
if
it's
cool
up
and
there's
also
an
implementation
already
in
JavaScript,
which
will
improve
it's
still,
not
like
that
good,
but
yeah
it
kind
of
works.
You
can
even
have
your
own
tests
without
doing
JavaScript
work
and
I
did
I.
Think
I
also
put
it
in
the
notes
last
week,
some
some
tooling
around,
but
it's
also
improved
so
yeah.
D
If
you
were
to
check
it
out,
then
a
lot
of
moving
the
JavaScript
proteins
to
Travis
CI,
there's
only
two
projects
left
I'm,
the
maintainer
of
and
then
I'm
done
and
yeah.
Next
I'm
not
blocked,
not
really,
but
I
really
want
to
get
this
JSI
LDPR
merged,
so
there's
I
yeah,
so
hopefully
Allen
will
have
times.
D
We
have
another
view,
and
hopefully
this
time
it
doesn't
find
any
new
issues
and
then
it's
hopefully
you're
ready
to
get
merged
because
I
really
like
to
get
it
much
before
we
do
all
this
other
single
register
a
weight
stuff,
because
else
I
feel
that
it
gets
delayed
more
and
more
so
yeah
and
then
hopefully
start
doing
to
work
on
the
IP
LD
formats.
Api
changes,
that's
all
from
my
site.
A
C
So
most
of
what
I
did
last
week
is
triaging
issues
which
I
will
continue
to
do
this
week.
But
there
are
some
issues:
I
was
working
on
the
pull,
em
Plex
integration
and
was
looking
at
ipfs
interrupt
and
that
had
some
issues
and
so
I
was
checking
against
the
latest
version
of
the
latest
iOS
release
candidate
and
the
issue
exists
there.
C
So
it's
not
in
pull
in
Plex
itself,
which
is
good
but
bad,
because
there's
an
issue
with
the
exchange
files
hitting
heap
issues
so
I'm
going
to
look
into
that
I'm,
probably
going
to
write
some
basic
benchmark
tests
for
at
least
the
switch
to
see
if
there's
something
going
on
in
the
switch,
that's
causing
the
heap
to
get
out
of
control,
but
because
that
will
probably
be
a
blocker
for
the
next
ipfs
release.
So
that
is
going
to
be
at
the
top
of
my
list
for
folks
focusing
on
that
this
week.
C
An
issue
that
I
am
blocked
on
somewhat
is
Travis
doesn't
seem
to
properly
support
IP
six
tests,
so
I
went
to
update
the
PDP
TCP
and
that
is
having
some
failures
and
was
worth
looking
at
some
additional
IP
6
tests,
but
that
was
not
working
properly,
so
not
a
huge
priority
at
the
moment,
but
that
will
probably
be
an
issue
so
yeah
other
than
that
released.
A
small
update,
form
J's
multi
adder
to
support
to
JSON
so
that
we
can
stringify
and
parts
from
the
config
multi
adders
so
other
than
that.
That's
pretty
much
it.
A
E
A
little
so
last
week
I
mostly
spent
almost
every
of
my
time
in
the
HT
diagonals
in
the
bank
for
the
superior
to
John,
Jessup.
Fs
Jacob
also
helped
me,
and
basically
the
problem
is
that
when
we,
when
we
do
the
Ibanez
republish
at
the
HT
put
his
triggers,
which
consequently
tries
to
get
the
closest
beers
and
the
or
when
we
are
trying
to
get
the
closest
peers.
E
The
things
were
getting
out
of
control
because
we
basically
crawl
the
entire
network
and
the
query
just
blows
up,
because
it
wasn't
finishing
and
so
I've
been
discussing
possible
solutions
with
Jacob
and
we
ended
up
going
with
temporary
fix
for
foreclosed
beers
and
that
will
hopefully
and
block
the
release
for
now,
because
we
now
can
can
put
without
problems
and
I.
Think
that's
the
biggest
problem
of
efficiency
right
now
will
be.
If
we
do
the
HD
query.
E
We
end
with
this
fix.
The
CPU
is
fine
and
from
now
I
think
we
can
just
improve
the
things
without
being
which
is
AB
FS
like
all
crashed,
then
I
also
got
a
little
progress
in
the
DHT
in
drop
tests
not
ready
for
period,
but
I
had
some
progress
on
that,
as
well
as
the
purpose
of
support
for
demon
enjoyment.
Client
I
already
have
the
commit
sin
in
my
update,
I
and
I
hope
to
get
in
a
state
for
PR
during
this
week,
then
other
minor
stuff
there
I
did
like
migrate.
E
They
were
able
to
use
Travis
AI
interviews
for
for
Volker
and
I
also
did
a
PR
for
fixing
the
DNS
formats
images
and
my
fmt.
So
as
I
said
this
week,
I
really
wanted
to
to
get
the
HD
interrupt
tests
and
website
support
for
the
demons.
Ready
and
I
I
also
want
to
do
a
new
review
for
the
hospital
orientation.
E
It
wasn't
a
things
that
I
wanted
to
do
last
week,
but
thanks
to
the
HD
I
couldn't
manage
to
get
that
and
also
there
Kempsey
made
a
couple
of
pairs
for
sync
migrations
for
every
NS
in
DHT
and
is
also
waiting
for
my
feedback,
so
I
realized
also
to
get
those
parents
reviewed
this
week.
Is
everything
any
questions.
I.
A
Have
so
the
the
fixes
that
you've,
the
owner
temporary
success
that
you've
done
to
to
help
fix
up
the
CPU
usage?
Well,
does
that
effectively
mean
for
the
like?
What
what
have
we
lost
by
doing
those?
So
it
sounds
like
so
we're
disabling
DHT
discovery?
Does
that
mean
I'm
not
going
to
get
lots
and
lots
of
beers
appearing
in
my
Jess
IVFs?
No,
it's
not
going
to
discover
them,
but
content
like
I'll
still
be
able
to
get
content
from
the
network
that
I
wasn't
able
to
before.
A
E
Basically,
first,
when
we
do,
the
the
DHT
puts
will
not
put
to
as
many
beers
at
it
would
be
great
to
put,
because
what
we
are
doing
now
is
just
do
a
first
iteration
of
closer
beers
and
not
like
carrying
the
closer
peers
of
the
closer
peers
and
the
cause
appears
of
the
closer
closer
peers
and
so
on.
This
is
what
was
happening
before
and
basically
all
right
what
we
discussed
to
fix
that
it
would
probably
help
to
have
the
sink.
It's
Reiter's,
because
we
put
like
it
right
to
through
the
query
and
abort.
E
B
E
A
E
A
E
I'm
not
really
really
sure
it
now,
because
it
will
depend
on
the
on
the
discussion
that
we
have
in
the
in
that
issue,
because
I
think
for
for
this
to
be
really
in
a
good
shape.
We,
we
also
should
have
some
efforts
in
improving
the
connection
manager,
because
if
we,
if
you
were
able
to
smartly
close
connections,
we
would
be
able
to
have
more
proper
forum
panicked
to
two
other
beers
which
no
is
a
problem:
okay,
okay,.
A
F
G
G
G
Basically,
it's
exactly
as
I
told
them
the
the
way
they
said
that
they're
their
windows
VMs
is
wrong.
I
told
them
how
they
should
set
up
the
windows
vm's,
because
I
validated
that
the
way
I
explained
to
them
works
at
least
for
us
and
he's
mostly
what
everyone
does
when
they
won't
and
nodejs
and
me
to
compile
native
stuff
for
nodejs.
Do
was
basically
installing
NPM
package
that
does
all
the
things
needed
to
a
debt
working
on
Windows.
G
G
Indeed,
a
prioritization
of
the
async
traitors
for
requests.
Basically,
right
now
on
the
issue,
we
have
all
the
repos
with
a
p0,
p1
p2
parrot
elation.
Everything
else
has
a
p3
plus.
Basically,
what
I
did
I
only
did
like
be
zeros,
be
ones
in
peaches.
Basically,
p0
depends
on
nothing.
The
at
least
our
dependence
is
not
like
streams
or
stuff.
G
P1
depends
only
on
p0
s
and
P
to
depend
on
P
ones
and
be
zeros.
Everything
else
is
gonna
be
on
another
wave
and
that's
why
some
of
them
have
like
p3
plus
that's,
because
they
either
depend
on
P
suit.
Peaches
are
higher
than
that,
so
we
now
have
everything
like
privatized,
so
we
can
start
looking
at
the
pz
rose,
merging,
doing
a
release
with
a
place
of
minor
and
go
from
there
to
the
p1
and
p2.
The
one
thing
I
noticed
when
doing
this.
This
work
is,
let
me
give
you
an
example.
G
The
dependencies
and
a
lot
of
our
repos
have
like
ok
dependencies.
They
mostly
have
only
third
party
dependencies
at
least
be
zeros,
but
then
under
the
on
the
dev
dependencies
they
depend
on
higher
higher
level
repos
as
we
go
through
these
repos
and
do
the
sync
traitors.
Full
requests
would
be
a
good
thing
to
try
to
remove
the
higher
level
packages
from
the
tests.
Some
of
our
repos
are
really
hard
to
do,
especially
the
ETP
ones,
because
it's
kind
of
really
hard
to
not
use
higher
level
repos
to
do
the,
but
others
like
this
one.
G
The
multi-part
we
shouldn't
like
any
like
IVFs
apir.
This
is
really
all
the
HTTP
client
to
do
the
test.
You
should
do
the
the
mocks
and
features
manually,
maybe
going
to
the
HTTP
client,
getting
the
output
and
just
copy
edit
copy
pasting
it
suited
to
the
test.
So
we
don't
kind
of
need
to
depend
on
Eire
level
Ripple's
to
do
the
tests.
G
That
would
make
the
ripples
more
modular
and
more
like
not
directly
dependent
on
a
level
repos,
and
that
would
be
probably
a
good
thing
and
the
tests
would
be
more
atomic
for
the
repo
logic,
not
like
only
world
with
ours
stuff,
because
if
anyone
wants
to
use
multi
parts
they
it
will
probably
like
break
because
the
it's
made
for
HTTP
client.
So
if
you
can,
when
you
go
through
the
PRS
about
this
stuff,
try
to
remove
as
much
as
you
can
from
the
dev
dependencies
for
the
rest,
I
already
lost
my.
G
A
F
Cool
so
I
found
PRS
for
the
Jas
data
store
packages,
a
problem
for
justice
or
Court
and
CI
is
failing
notes
locally,
which
is
now
allowing
you
to
sort
of
test.
The
packages
that
are
further
downstream,
so
I
hope
to
like
clear
the
triad
of
or
trio
of
packages
and
get
all
those
working
this
week
and
addressing
PR
comments
as
well,
and
thanks
for
this.
A
H
So
last
week
I
was
holiday,
so
very
much
I
was
I
was
looking
to
a
perceived
problem
with
hubsan
agency
to
stop
working
after
one
and
after
a
bit
of
investigation,
it
turns
out
there's
a
magic
number
for
this,
the
maximum
size
of
a
message
that
you
can
send.
If
you
send
a
message
to
subscribers,
there
is
bigger
than
this
position.
They
would
disconnect
from
you
and
laughing
out
the
hard
way.
B
H
We've
kind
of
fallen
by
the
wayside
somewhat
so
I'm
going
to
make
that
not
be
a
thing
and
get
some
of
that
stuff
done.
Yeah,
mostly
probably
like
trying
to
add
to
be
missing,
features
too
I
profess
that
we
don't
have
so
that
we
can
be
feature
complete.
That
would
be
me.
I've
got
my
blurry
and
that's
better,
so
I'm
trying
a
new
webcam
folker
thinks
I
look
oversaturated.
I
have
just
been
on
holiday.
A
Cool
all
right,
thank
you,
Alex
and
all
people
who
have
shared
of
us
an
update
if
you
weren't
here
at
the
start
of
the
call
hey
we're
over
time.
So
if
you
want
to
leave
them,
you
can
just
leave,
but
we
went
here
at
the
start.
The
cool
I
wanted
to
try
something
new
and
do
across
teams
update
sections.
A
So
if
you
are
in
a
team
and
a
different
team,
but
would
like
to
share
with
us
a
win
or
an
update
from
your
team
and
we've
got
a
section
for
that
now
and
we
can
all
hear
about
each
other's
wins
and
we
can
like
share
information
a
bit
more
readily
and
encourage
people
to
do
that
and
I
think
that
would
be
awesome.
So
I
said,
if
we
had
time,
if
you
don't
have
anything
else
to
do
then
stick
around
and
if
Jim
would
like
to
share
his
his
cross
team
update.
That
would
be
rad.
A
B
Well
well,
I'm
here
so
maybe
go
quickly
mentioned
that
Hugo
already
mentioned
that
he
created
a
very
nice,
in
my
opinion,
take
on
redoing
the
interface
of
our
browser
extension.
So
if
anyone
is
interested,
I
extracted
that
idea
into
a
separate
thread
when
we
can
brainstorm
how
we
can
improve
the
current
UI
or
how
can
we
design
absolutely
new
one-
and
here
is
the
Hugo's
idea
and
feel
free
to
post
I'll,
stop,
sharing
and
I'll
paste
link
to
the
chart
in
case
anyone
is
interested.
A
All
right,
thank
you
later
cool,
that's
in
the
chat
and
that's
it
for
this.
We
covered
notes,
wait
Jacobs
out
next
Monday
vodkas
out
next
week
be
aware,
don't
message
them
they're
busy,
all
right!
Thanks
a
lot
everyone,
and
thanks
for
sticking
around,
if
you
did
so
to
take
up
more
time
than
I,
am
allocated
and
we'll
see
you
next
week
for
another
exciting
around
of
what
I
done
that
this
week.
That's
only
you
hey!
Are
you
going
question?