►
From YouTube: BE Pairing - EMEA/APAC - 2023-09-13 - Reactive Caching
Description
Exploring weird behavior in reactive caching / rescue in this MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/129561
Documentation on reactive caching: https://gitlab.com/gitlab-org/gitlab/-/blob/5209dd4b628df856e8ac1abe7a42a509730c0dd6/doc/development/reactive_caching.md
C
B
B
B
It
wasn't
covered
by
our
tests,
I
subsequently
added
a
test
which
actually
picked
it
and
we
reverted
the
change
and
but
during
the
during
the
analysis
of
it,
I
came
across
something
very
odd
with
the
reactive
caching
code.
Is
anybody
on
the
call
know
how
to
elevate
a
pitch
reactive?
Caching
as
we
use
it.
A
B
So
I'm
not
entirely
sure
about
everything
that
it
does,
but
my
understanding
is
that
you
can
brings
concern
into
a
what
usually
seems
to
be
used
in
model
objects
and
you
can
perform
an
expensive
operation
in
the
background
job
that
will
eventually
load.
It
will
cache
the
result
from
that.
Oh
that
one.
C
D
B
B
I'll
I
think
it's
less
important
like
what
this
is
doing
to
actually
and
to
just
show
the
weird
Behavior
we
would
gain
so
I'll
just
go
ahead
and
try
and
do
that.
Okay,
so
we
have
these
training
provider
binders
now
they're
not
actually
binders
like
most
of
our
finders
they're,
not
active
record
query
builders.
B
Folks
who
provide
security,
training
for
different
issues
and
they
and
they
come
back.
Those
providers
come
back
with
the
URL.
So
if
you've
got
you
know,
cve
one
two
three,
you
can
say
give
me
a
URL
that
will
give
me
some
training
on
that
issue
and
the
training
provider
comes
back
with
that
URL.
So
that's
the
part
that
we
cache
is
the
call
out
to
those
providers.
B
B
B
C
C
B
D
B
C
B
B
A
B
B
B
B
C
A
A
B
B
B
B
A
B
C
A
C
B
B
A
D
B
A
D
C
B
C
B
D
C
B
B
B
D
B
B
A
B
A
D
A
C
A
B
B
D
B
B
B
B
B
B
B
A
B
Only
because
I
couldn't
reproduce
it
using
like
regular
methods
in
no,
it
might
be.
Another
Factor,
but,
like
I,
tried
to
make
a
really
simple
test
case
with
just
a
module
and
a
couple
of
and
a
class
and
a
base
class
and
a
method
that
calls
insure
and
I
just
didn't
see
the
same
Behavior
I
guess.
The
thing
that
maybe
we
could
look
at
is.
B
D
B
D
B
D
B
B
A
B
D
D
D
D
B
D
C
D
A
D
D
B
B
D
C
C
C
D
B
C
B
B
B
B
B
A
A
That
are
like
the
nice
thing
about
going
through.
That
is
that
you
were
looking
into
kind
of
like
weirdness
with
rescues,
and
that's
exactly.
The
kind
of
bug
that
I've
been
working
with
is
like.
It
feels
like
something's
being
rescued
somewhere.
That
shouldn't
be
like
things
are
silently
failing,
which
is
the
scariest
type
of
failure.
So.
B
A
A
C
B
C
A
B
B
A
D
B
A
B
C
A
Know
exactly
well,
and
it's
just
it
is
helpful,
like
I,
really
love
the
way
I
get
lab.
We
use
rural
cop
to
when,
when
it's
used
to
enforce
things
that
actually
like
you
always
want
to
do
like.
Sometimes
it's
annoying
because
you
have
to
say:
oh
I,
don't
actually
don't
want
to
do
that
in
this
situation,
but
this
seems
like
a
case
where
anytime
somebody
got
through
book
up
error.
They
would
just
change
it
and
they
wouldn't
be
like
no
I
need.
You
know.
A
I
need
to
rescue,
not
Implement
air
I
need
to
raise
an
implemented
error.
It
seems
like
that
would
never
happen
that
has
happened
to
me
today.
We
talked
about
this
I.
Think
almost
was
it
last
week
about
people.
Misspelling
aggregate
failures
are
doing
aggregated
failure.
I
did
today
I
did
that
I
added
aggregate
errors
like
three
times
in
the
rubicop
raised
before
I,
could
commit,
because
that
doesn't
do
anything.
I
was
like.
Thank
you,
so
I
think
this
would
be.
D
A
B
C
A
C
C
A
Yeah
double
Advocate,
exactly
like
I
guess
when
I've
used
this
pattern
in
the
past,
the
intention
is
that
it
would
never
reach
an
end
User.
It's
like
it's
almost
like
just
a
tip
to
developers,
and
so
you
really
kind
of
want
to
throw
the
air
in
their
face
because
you're
like
this
is
an
error.
You
cannot
rescue
it
like.
You
have
to
override
this
method.
That's
how
I've
used
it
in
the
past,
but
I
understand
that
there
are
situations
where
those
kinds
of
things
sneak
through
to
end.
C
B
Yeah
I,
don't
know
if
you
look
at
if
you
look
at
the
class
of
errors
that
are
in
that
group,
they
are
literally
things
like
out
of
memory
like
there
is
literally
no
way
you
can
carry
on
executing
if
you're
out
of
memory
is
done,
you're
over
finished,
yeah
yeah,
this,
like
not
not
having
a
method
available,
is
not
on
that
kind
of
spectrum
of
Errors.
You
know
it's.
D
C
D
Why
does
it
need
to
be
a
hard
hard
hit
like
that?
The
only
reason
it
it's
useful
is
because
we
have
some
form
of
coverage,
specs
that'll
make
sure
every
path
gets
hit
and
then,
through
that
it'll
hit
the
not
implemented
error
currently,
but
in
another
sense
you
should
have
probably
have
the
unit
specs
anyway
that
are
going
to
ensure
that
whatever
you're
calling
on
that,
whatever
your
subclassing
is
doing
something
useful.
So
it
seems
like
safety
net.
That's
not
really
needed
seems
weird.
B
Yeah
I
think
the
other
thing
for
me
is
using
that
patent
was
the
you
know
the
error
method
in
the
base
class.
It
kind
of
moves
the
stack
Trace
to
a
potentially
less
like.
If
you
do
error
out,
you
end
up
erroring
out
from
the
Base
Class
rather
than
from
the
caller
yeah,
which
might
make
more
sense
if
it
errors
out
in
the
caller
of
that
method.
It's
like
okay,
I,
see
where
this
happened.
I
don't
know
it's.