►
From YouTube: 2022 07 15 Git Cache Maintenance
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
Rishikesh
does
that
work
for
you
or
what
would
you
like
on
the
agenda
yeah
that
that
will
work
all
right?
Okay,
so
tell
me
what
you're
thinking
about
the
presentation
and
let's
talk
about
ideas
of
how
so
how
much
time
do
you
have?
You
have
15
minutes,
15
minutes
yet,
okay,
so
15
minutes
good.
All
right
and
people
like
to
see
demonstrations.
A
B
Okay,
when
I
was
thinking
about
you
know,
you
know
demonstrating
it
on
my
computer,
only
oh
good
yeah,
because
we
have
the
git
login
installed
right,
so
I
thought
I'll
load
few
caches
on
my
computer
beforehand.
You
know
install
few
caches
and
you
know
create
few
caches,
and
then
you
can,
you
know,
run
the
maintenance
also
on
my
computer
and
show
display
all
the
logs.
This
is
what
I
was
thinking
in.
A
Mind
that
that's
that's
exactly
the
thing
that
I
was
considering
was
the
this
is.
This
is
very
much
a
back-end
thing
right.
This
is
not
something
that's
going
to
show
pretty
pictures
to
the
user.
So
what
we're
going
to
do
is
show
you
look
here.
Is
this
jumbled
cache
with
lots
of
garbage
in
it
right?
It's
got
many
many
individual
things
and
and
I
think
you
had
said
you
have
a
command
line
that
will
actually
split
a
split.
C
A
Yes,
yes,
yes,
yes
good!
So
so,
then
you
do
that
say:
watch
I'm
going
to
I'm
going
to
intentionally
damage
this
repository.
It's
going
to
now
be
full
of
garbage
that
needs
to
be
collected
so
watch
this
boom.
Look
at
all
the
objects
in
the
directory
yeah.
There
are
a
lot
of
those
okay.
Now
we're
going
to
schedule
a
maintenance
task
and
off
it
goes.
B
Yeah
I
think
that
that
that
looks
that
sounds
good.
Last
night
I
was
trying.
You
know
unpacking,
although
objects
from
the
pack
file,
so
good.
D
A
So
and
then
so
the
demonstration
piece
I
assume
you
probably
also
want
some
form
of
orientation
on
structure
or
architecture
or
approach.
A
A
Little
bit
about
how
you,
how
you
put
things
together
and
what
you
evaluated-
okay
and
I
you
don't
have
to
I-
was
just
thinking.
Sometimes
it
helps
people
if
they
see
a
picture
that
says,
look:
here's
how
here's,
how
the
caches
work
I
mean.
You
certainly
know
in
detail
how
the
caches
work
right.
They
are
on
the
controller,
not
on
the
agents.
They
are
in
this
location,
they're.
B
A
No,
no
I
was
thinking
a
few,
a
few
blobs,
a
few,
a
box
here
and
a
box
there
and
you
describe
this
box-
is
where
all
the
caches
are
and
this
box
is
is
on
is
inside
the
controller
and
that's
it
I
would
definitely
not
do
anything
detailed.
No,
no,
so
architecture
is
probably
the
wrong
word.
It's
a
high
level
diagram
to
explain
the
the
concepts
and,
and
now
now
I've
got
a
question
for
you
is
it?
A
Is
it
worth
talking
about
the
complexity
of
dealing
with
multiple
versions
of
command
line
git,
because
I
know
that
was
that
that
continues
to
me
for
me
to
be
a
real
challenge?
Is
we've
got
ancient
versions
of
command
line,
get
on
some
some
user
machines
and
we've
got
very
modern
ones
on
others,
foreign.
B
A
B
A
D
Do
we
want
to
for
the
last
point
we
want
to
generalize
that
with
the
challenges
that
rishikesh
faced
about
whatever
he
thinks,
what
the
challenges
for
the
current
for
the
space.
While
you
know
he
was
developing
this
feature
and
then
he
could
talk
about
the
let's
say,
multiple
kit
versions
or
if
there
was
any
other
thing
that
he
thought
was
or
or
still
is,
a
challenge
for
the
project.
D
Yeah
I
mean
it's
it's
more
up
to
you.
It's
not
like.
There
is
a
set
format
to
the
demonstration.
It's
more
up
to
you.
If
you
feel
like
by
talking
about
them,
you
would
be
effectively
communicating.
You
know
the
the
essence
of
what
you
did
for
the
month.
B
B
Like
the
UI
changes,
you
know
what
would
be
added.
How
would
we
display
you
know
so
certain
things
in
the
table
also.
A
B
If
you
guys
don't
mind,
can
we
do
it
on
like
next
Wednesday
one
day
before,
though,
yes.
A
A
A
For
me,
at
least
it's
pretty
common
for
me,
to
think
the
demonstration
will
be
take
less
time
than
it
actually
does,
because
I
have
to
explain
things
on
the
way
and
I
have
to
hey
wait
for
this
to
complete
and
while
it's,
while
I'm
waiting
for
it
to
complete
I,
need
to
find
something
to
say
hey.
This
is
this
is
happening
what's
happening?
Is
this
and
we're
now
going
to
look
at
this
other
thing,
while
that
happens
and.
B
E
A
I
was
just
wondering:
do
I
need
to
do.
We
need
to
do
some
more
testing
before,
but
probably
not
because
the
crucial
thing
for
you
is
the
most
important
thing
for
you
is
the
demonstration
and
that
you'll
you'll
construct
it
in
a
way
to
assure
that,
hey,
let's
be
sure
this
works,
that
it
behaves
the
way
we
expect,
and
so
rishabh's
in
my
testing
and
and
code
reading
is
good
to
have,
but
not
required
for
the
day
for
the
presentation,
oh.
A
B
Yeah,
so
I
will
I'll,
try
it
once
like
what
commands
I
would
run
and-
and
you
know,
check
it
out.
C
D
A
D
Presentation,
so
you
know
one
of
the
difficult
things
that
to
do
is
when
you
don't
have
a
UI
to
show,
and
you
just
have
a
bunch
of
code
that
you've
written
down.
You
know
through
the
whole
phase,
and
now
you
need
to
demonstrate
something
right
and
I
did
not
so
I
didn't
have
a
UI
for
myself,
so
it
was
so.
What
did
I
have
I
had
Benchmark
tests
and
the
code,
and
it
was
much
more
boring
than
what
you
have.
D
You
have
a
whole
new
section
for
yourself,
so
I
I
think
it's
going
to
be
really
easy
for
you
to.
When
it's
going
to
be
much
more
intuitive
for
the
users
to
understand
your
feature
and
how
it's
going
to
impact
the
users,
then
you
know
just
showing
them
the
code
and
then
reading
that,
because
that
becomes
awfully
you
know,
Virgos
are
boring.
There
is
a
chance
that
that
happens
while
you're
looking
you
start
reading
it
yeah.
A
Good
yeah
and
okay
I
still
I
still
have
to
admit
this
is
less
less
demonstration
than,
for
instance,
the
the
web
page
changes
that
are
being
done
in
one
of
the
other
projects.
Right:
okay,
fine
you're,
not
doing
web
page
changes,
but
we've
got
a
UI
to
show,
and
the
UI
that
you
can
show
is
something
that
can
talk
about
hey.
This
is
familiar
to
Jenkins
users.
Yes,
in
fact
this
is
this
is
how
cron
jobs
are
scheduled
in
Jenkins
everywhere.
It's
just
the
same
good.
B
I
think
this
is
fine.
I
think
this
is
this.
Would
you
know,
be
a
15
minutes
presentation,
I?
Think
if
I
cover
all
these
topics,
so
yeah
I
I,
thought
I'd
work
on.
You
know
the
presentation
this
weekend.
A
D
A
B
About
you
know
the
the
tests.
There
are
three
tests
which
are
healing
continuously
on
you
know
when
I
tried
running
those
tests
as
well
on
my
computer,
two
of
them
are
running
successfully,
but
I.
Don't
know
why
I'd
be
failing
on.
You
know,
though,.
A
On
GitHub
so
yeah,
so
let's
go
here
this
one
and
what
you're
seeing
is
there
are
failures.
There
are
test
failures
and
we
need
to
get
those
fixed.
That
would
that
would
be
a
healthy
thing,
that's
something
that
rishab
and
I
may
be
able
to
help
Okay.
So
let's
see
what
we've
got
here.
So
let's
look
at
the
check
at.
B
A
A
Foreign,
but
only
on
Java,
8
and
then
get
caches,
fails.
Okay,
this
one
might
be
a
race
condition,
so
maybe,
but
that's
those
are
okay.
Those
are
in
interesting
failure
mode.
A
So
the
plug-in
is
not
fully
ready
for
that
yet,
and
and
that's
sort
of
embarrassing,
because
it
should
be
it's
been
months
and
years
that
that's
been
in
progress,
so
so
I
think
it's
okay!
If
we,
if
you
ignore
these
test
failures
for
now
as
long
as
they're,
not
getting
in
the
way
of
your
doing
your
your
demonstration,
they'll
wait
until
after
the
demonstration
and
if
rishab
or
I
are
able
to
to
help
with
them.
Somehow
I
assume
you
won't
reject
our
attempted
help.
A
B
Because
you
know
I
thought
I.
You
know
finish
this
part
because
there,
every
time,
whenever
I'm
sending
you
know
pushing
my
changes,
there's
a
failing
test.
Okay,
so
that's
kind
of
embarrassing
from
my
side,
I
I
tried
debugging
it
last
night
as
well,
but
I
couldn't
find
you
know
the
solution
to
it.
So
yeah.
A
Yeah
and
and
I
I
think
it's
okay
to
admit
that
hey
this
project
is
a
real
project
and
as
a
real
project,
it's
got
priorities
and
it's
more
important
to
focus
on
the
presentation
right
now.
Yes,
test
failures,
it's
a
it's
a
little,
embarrassing
fine,
we'll
we'll
deal
with
being
a
little
embarrassed.
We
want
to
be
sure
you
get
a
good
presentation
done.
A
A
A
A
B
So,
basically,
right
now
the
current
status
is
like
you
know,
for
whatever,
whatever
we
have
planned,
you
know
for
the
phase
one
of
G,
so
if
I
think
that
has
been
completed
successfully
yeah.
B
So
the
aim
was
to
finish,
you
know,
execute
you
know,
coding
the
git
maintenance
for
all
version
less
than
3.2.30
and
greater
than
that
so
I
think
that
has
been
completed,
I'm,
not
sure
about
the
bugs,
but
yeah.
A
B
I
think
that's
it
yeah.
There
are
no
other
topics
from
my
side.
It
was
mostly
it
was
about
the
presentation
so
yeah.
A
Great
well
and
and
congratulations
on
your
progress,
this
is
this
is
very,
very
good.
Well
done
thanks
very
much
for
what
you're
doing
Jenkins
users
will
happily
thank
you
just
like
they
happily
thanked
Richard.
So
thanks
very
much
to
both
of
you.
That's
great.
A
If
there's
nothing
else,
we
may
be
able
to
end
and
thou
then,
for
now
is
that
okay
for
the
two
of
you
yeah
yeah,
it's
fine
all
right!
So
then,
given
that
I
have
enough
time
before
I
go
to
sleep
to
upload
the
the
recording,
so
you
have
chosen
well
in
about
30
minutes
or
45
minutes.
I'll
have
the
recording
uploaded,
thanks
to
both
of
you
have
a
great
evening
have
a
great
day
good
day.
I
forget
it's
it's
starting
your
morning.
It's
actually
early
morning,
thanks
very
much
and
good
date
about
that.
Bye-Bye.