►
From YouTube: Conversation with Adam Liter and Stan Hu
Description
Conversation with Adam and Stan on how a simple MR to fix typos led to discovering a bigger issue
A
Hi,
my
name
is
very
Paik
the
community
manager
at
get
lab,
and
I
have
a
couple
of
guests
here.
On
this
session.
There
was
a
community
contribution
that
came
through
last
week
from
Adam.
You
know
let
the
participants
like
introduce
himself
in
a
few
minutes,
and
we
thought
this
was
going
to
be
relatively
simple
fixes
on
our
on
our
web
pages
and
Adam
actually
helped
identify.
A
B
A
Yeah
so
I'm
showing
the
I
mean
there
I
think
there
are
26
pages
as
you
can,
as
you
can
see,
and
you
can
highlight
the
merge
request
number
under
www
lab
comm,
so
people
can
follow
along
during
the
recording
or
afterwards.
But
we
thought
this
were
relatively
simple,
like
a
typo
fixes
that
Adam
was
generous
enough
to
find
and
notice
a
pipeline
issue
that
we,
because
because
of
that,
we
could
emerge,
but
so
first
of
all,
I
Adam
like
how
did
you
even
find
like
I
mean?
A
B
I
had
originally
noticed
just
a
few,
just
as
I
was
kind
of
looking
through
the
website
and
I
decided
I'd
go
ahead
and
fix
those
and
I
thought
while
I
was
fixing
just
a
few
I
would
run
some
of
the
other
documentation
things
through
a
script,
so
I
did
end
up
using
a
script
for
most
of
them.
There
were
a
few
I
just
caught
from
just
browsing
the
website,
but
cool
yeah
awesome.
A
Yeah,
it's
great
to
have
a
linguist
contributing
to
get
lab
and
I.
Think
you're
being
somewhat
modest
here.
I
think
you
I,
think
you
told
me
you
initially
started
out
studying
computer
science
in
University
and
got
fell
in
love
with
linguistics.
I.
Think
that's
I
think
so
you
still
kept
interest
in
computer
science
or
coding
on
your
side.
I
guess!
But.
C
Sure
my
name
is
Stan:
hey
I'm,
an
engineering
fellow
I
can't
live
I've
been
with
the
company
for
close
to
four
years
now,
and
before
I
get
loud.
I
was
actually
working
before
I
worked
at
Goodlatte,
full-time
I
was
contributing
it
lab
and
much
in
the
same
way,
adam
was
always
happy
to
help
out
contributors.
A
Cool
yep,
so
yeah
I
was
going
to
point
that
out
to
us
and
like
a
lot
of
our
a
lot
of
the
gitlab
employees
today
like
started
out
as
contributors
before
joining
the
company,
so
so
I'm
going
to
quickly
scroll
through
the
Mr
here
I
mean
you're
not
going
to
be
able
to
see
it
right
now,
but
obviously
you
submitted
AMR
I,
reviewed
him
and
notice
that
there
was
a
pipeline
there,
and
then
this
was
late
in
the
evening.
I
don't
think
I
was
very
helpful.
A
I
just
said:
hey
yaddam,
can
you
fix
these
pipeline
issues
so
I
can
merge
them
and
I.
Think
I
went
to
bed
for
four
for
the
for
the
day
and
then
when
I
woke
up,
I
saw
a
couple
of
comments
from
you.
So
Adam
tell
me
about
like
some
of
the
what
you
notice
and
some
of
the
debugging
that
you
had
to
identify,
help
identify
the
problem.
A
B
B
I
took
a
look
at
the
build
that
failed
to
see
what
might
have
gone
wrong,
and
there
was
this
error
about
not
being
able
to
find
the
G
Lib,
see
this
system
little
C
library,
so
I
did
end
up
trying
your
suggestion
of
just
fixing
like
one
type
of
at
a
time,
but
I
was
unsure
if
that
was
gonna
work.
So
at
the
same
time,
I
was
kind
of
like
trying
to
take
a
look
at
some
of
the
other
merge
request,
because
at
that
point,
I
had
noticed.
B
After
just
clicking
on
the
general
merge
request,
tab
and
kind
of
looking
at
some
of
the
recent
ones
going
down.
There
were
a
lot
of
them
that
were
passing
and
then
a
lot
that
were
just
or
sorry
a
lot
that
we're
passing
and
like
only
one
other
one
I
saw
that
was
failing
and
conveniently
on.
You
all
have
these
like
labels,
so
I
happen
to
notice
that
this
other
one
that
was
failing
was
labeled
as
a
community
contribution.
B
So
yeah
you're
pulling
up
the
failed,
build
and
there
I'll
let
you
get
to
it.
But
there
was
this.
As
I
mentioned,
the
G
Lipsy
error
like
it
was
it
couldn't
find
the
expected
library,
so
I
thought
that
suggested.
It
was
something
to
do
with
the
container
that
was
being
used
for
the
build.
But
then,
when
I
was
taking
a
look
at
the
jobs
from
some
of
the
other
merge
requests
where
the
everything
was
passing
it
looked
like
they
had
the
same
docker
image.
So
you
saw
the
same
docker
like
image
hash.
B
The
only
one
difference
I
noticed
was
the
one
that
you
want
to
had
it
just
highlighted
ray
the
fact
that
my
job
and
then
this
job
from
this
other
community
member
was
using
this
web
Ruby
2
6
cache,
whereas
the
the
builds
from
the
ones
that
were
passing
were
using
a
different
cache,
which
was
red
web
guru,
b-26,
splash
and
that's
kind
of
when
Stan
jumped
in
to
help
debug.
So
maybe
he
can
take
over.
A
Yeah
I
mean
I,
really
appreciated
the
fact
that
you
pointed
out
hey.
There
were
other
like
similar
Amar's
that
were
failing,
that
came
from
the
community.
I
noticed
that,
like
there
like
a
previous
week
and
and
obviously
they
didn't
get
to
the
bottom
of
it
and
that's
when
I
started,
asking
for
help
internally
I
went
to
the
slack
Channel
for
merge,
request,
coaches
and
Stan
kind
of
jumped
in
and
and
Stan
one
from
there.
C
I
was
just
picking
up
where
Adam
had
and
he
had
raised
a
good
question
about
this
ones,
and
this
one
isn't
doesn't
have
it,
and
my
first
question
is:
where
is
that
to
come
from
because
I
have
no
idea,
you
know
our
gitlab
see
I
yeah.
Well,
I,
don't
see
that
anywhere
and
so
I
first
asked
you
know.
I
just
was
kind
of
in
that
merger.
Guys
I
just
asked
somebody
on
our
team
to
mosh
because
he's
next
from
our
runners
like.
C
Where
is
that
to
come
from,
but
then
occurred
to
me
that
we
have
this
button
in
the
and
the
CIC
they
pipelines
that
allows
you
to
clear
the
runner,
cache
and
I,
never
actually
known
what
that
actually
did.
All
I
knew
is
you
who
clicked
that
button?
All
the
runners
seem
to
have
wiped
their
cache
and
him
and
went
about
their
way
so
I
figured
it
might
have
done.
I
had
something
to
do
with
that.
C
So
I
looked
at
the
code
and
realized
in
that
comment,
you
can
see
is:
is
its
jobs,
cash
index
and
so
I
thought
that
was
actually
a
really
smart
way
for
us
to
implement
this.
All
we
did.
Is
we
increment
a
number
to
clear
the
cache
so
that
the
runner
would
come
in
and
get
this
number
and
basically
append
this
little
index
to
the
number?
So
that's
that
explains
what
Adam
had
been
seeing
so
naturally
I
just
assumed.
C
Okay,
if
that
number
is,
it
must
have
meant
somebody
internally,
click
that
button
and
reset
the
cache,
and
therefore
it
makes
sense
for
all
our
contributors
to
do
the
same
thing
so
I
just
did.
The
naive
thing
is
that,
okay,
if
I,
clear,
Adams
cache,
does
that
solve
the
problem
and
it
at
least
got
his
pipeline
to
pass.
C
So
that
was
a
win
at
the
same
time,
I
I
think
I,
I
decided
I
was
gonna,
clear,
increment
the
cash
to
clear
that
button
again
by
pushing
that
button
and
make
our
number
go
from
2
to
3
and
as
a
result,
our
the
pipeline's
on
the
main
repo
had
the
same
problem
that
I
don't
have
to
face
so
and
then
other
people
started
mentioning
into
like
their
pipelines
were
failing
and
then
I
realized.
Ok,
we
just
we
just
managed
to
reproduce
the
same
problem.
C
I
don't
have
run
G,
so
there's
something
deeper
here
and
then
I.
So,
instead
of
like
just
doing
the
naive
thing,
I
had
to
go,
dig
a
little
deeper
and
look
at
the
actual
error
message
and
think
a
little
bit
about
why
that
is
happening,
and
so
I
think
on
that
merger,
because
I
started
mentioning
well,
it's
gotta
be
a
different
version.
Got
to
be.
C
Did
some
have
something
to
do
with
different
operating
system
versions,
because
this
happens
when
you
have
a
different
G
Lipsy
version
and
I
think
I
mentioned
that
I
ran
that
in
that
company.
You
can
see
that
I
tried
to
look
at
that
that
image,
I
was
I
was
failing
and
it
was
clearly
using.
You
know,
I
think
one
I
think
this
docker
image
is
using
version,
2.2,
4
and
then
and
the
the
pipeline
failure
was
complaining
about
needing
2.28
and
so
I
think
I
walked
away.
C
C
So
the
way
it
works
is
that
we
in
one
step
we
build
all
the
gems
we
need
and
we
cache
it
and
I
think
the
cache
gets
uploaded
and
then
a
different
step
comes
along
as
and
runs
our
tests
and
extracts
the
cache.
So
you've
got
these
two
different
images
if
they
don't
match.
This
is
exactly
what
happens
and
Adam
was
dead
on
here,
and
so
as
soon
as
he
pointed
out,
it
became
very
obvious
how
to
fix
it,
and
so
you
know
this
next
comment.
C
You
see
that
I
I
run
the
test
you
can
see
on
the
top
one.
This
is
the
build
image.
It
actually
generates
the
gem,
it's
using
Debian
Buster
version
10,
which
was
a
little
fish
at
least
on
July
6th,
but
I
think
there
was
some
lag
time
where
the
Ruby
image
moved
up
and
upgraded
to
this
version,
but
I
think
it
happened
in
the
last
week
or
so,
and
then
the
second
image
is
the
image
that
we
use
to
actually
test
the
website
and
that's
using
that
being
stretched.
C
So,
even
though
it's
nine
point
nine
to
ten,
it's
a
big
difference,
don't
number
difference
for
you.
They
significant
change
and
I,
think
it
bumped
up
the
library.
So
that
explains
why
it
failed.
They
have
these
two
different,
inconsistent
States.
So
the
way
you
fix
it
is
just
make
them
the
same
right
in
that.
Second,
what
you
see
is
the
image
we
actually
use
the
test
get
lab
Cee
and
we
actually
pin
it
to
Debian
stretch.
For
this
reason,
we
don't
want
these.
C
You
know
operating
systems
upgrades
to
happen
without
us,
making
a
conscious
decision
to
do
that,
and
so
to
fix
it.
You
can
see
the
next
merger.
Quick
follow-up.
Merger
glass
is
just
a
tag
that
build
image
with
Debian
stretch
instead
of
Buster,
and
so
you
can
see
this.
This
is
a
really
simple
change.
C
You
click
on
the
changes
button
there,
but
essentially
all
I
did
is
make
sure
that
you
know
I
just
changed
the
tag
from
slim,
2.6
slim
to
the
super
boy,
6
slim
stretch
and
kicked
off
the
builds
and
refreshed
everything,
and
basically
that
fixed
the
problem.
So
what
started
out
as
a
simple
typo
home
I
ended
up.
C
A
So
I'm,
just
like
yeah,
this
was
like
7:00
p.m.
Pacific
Time,
confirming
that
it
was
like
late
afternoon
in
the
evening
it
was
still
going
on
I,
remember
like
after
clearing
like
atom
and
another
contributors,
cache
like
we
thought
that
was
going
to
fix
everything.
But
then,
when
that
wasn't
the
case,
I
I
was
starting
to
get
worried
like
you're
sans
struggling
with
this,
like
what's
really
going
on
here,
but
so
yeah
I
think
like
in
a
couple
of
crucial
areas.
A
Adam,
you
you
know
pointed
us
in
there
in
the
right
direction,
so
that
was
definitely
appreciated
and
and
thanks
for
bearing
with
us
like
I,
think
some
people
I
mean
tend
to
get
kind
of
discouraged
when
things
get
a
little
bit
more
difficult
if
gulp
with
NMR,
but
you
stuck
through
it
over
the
over
the
past
couple
of
days.
So
we
definitely
appreciate
that
as
well.
So
yeah.
A
I
mean
so
like.
Obviously,
this
wasn't,
like
very
I
mean
this
wasn't
very
like
evident
what
the
problem
was.
If
this
said
have
been
like
left
alone
for
a
few
more
days,
I
think
we
would
have
gotten
seen
a
pile
up,
a
lot
of
mriswith
a
lot
of
errors
and
not
knowing
what
was
going
on
I.
Think
that's
like
an
obvious
impact,
but
yeah
it's
you
can't
imagine.
Our
website,
like
including
a
handbook,
gets
updated
very
very
frequently
what
lots
of
em
are
so
this
would
have
been
really
annoying
for
a
lot
of
us.