►
From YouTube: Gitaly Demo 2020 03 06
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
C
C
A
C
A
A
A
D
B
A
A
A
B
A
A
A
A
A
B
A
C
C
A
B
A
A
A
C
B
B
B
B
A
B
B
A
A
A
A
A
A
A
A
A
Okay,
get
back
look
at
me.
B
A
B
B
D
We
created
an
issue
for
using
Prometheus
to
meet
this
gage
for
this,
but
yeah
that
hasn't
been
done
yet
and.
A
A
A
A
B
C
Think
the
scenario
is
about
like:
how
do
we
tell
administrators
where
they
lost
data?
So
if,
if
the
Avenger
consistency
well,
if
we
aren't
consistent
as
the
data
store
and
we
feel
over
to
a
secondary,
then
we
want
to
know
what
they
know.
Not
what
data,
but
where
we
lost
data
and
John
is
now
working
on
the
rake
task
to
get
check
sums
for
each
repository
and
their
secondaries.
B
C
I
have
two
duplicates
one
and
then
for
my
ideas.
What
if
the
next
demo
were
snapshots
both
get
Liam
prefect
nodes
right
after
the
setup
that
should
reduce
the
amount
of
time
we
use
for
setting
up
before
the
call,
but
also
maybe
limits
configuration
errors
after
I
just
spotted
that
James
it's
the
next
demo
were
so
I'll.
Ask
him
personally
today.
A
B
I
think
it
was
the
figure
out
what
happens
without
prefect
when
it's
down
and
because,
if
we
tried
that
briefly
by
turning
prefect
off
and
we
got
a
404
again.
So
if
that's
just
what
reals
does
then
not
our
problem?
And
we
can
forget
about
this,
but
maybe
that
is
something
to
take
sit
down
and
check
for
a
moment.
B
C
And
then
this
is
a
bit
of
a
fake
one.
Sorry
for
this,
but
prefect
might
be
strong
down
recovery
of
the
gate
clean
out.
So
what
we
observed
if
I
got
it
right
is
that
we
take
down
to
get
early
and
prefect.
Apparently
things
get
to
be
still
on
line
because
it
keeps
the
connection
in
I.
Guess
a
GRB
SIBO
or
something
and
get
early
came
back
up
and
it
didn't
recover
too
fast.
C
C
A
C
Demo
venture
that
seems
to
work
well.
Yeah,
sir
stan
is
looking
into
console
for
now,
but
for
demos
we
should
just
move
to
an
environment
variable
and
the
change
should
be
fairly
minor
and
then
we
don't,
we
still
rely
on
only
was
generating
the
config.
So
there's
an
issue
for
it,
but
I'll
actually
schedule
it
and
ask
someone
to
pick
that
up
next
week.