►
Description
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/425392
Possibly similar to: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/124271
Sorry that most of this video is just us walking through debugger breakpoints. We don't end up finding anything but Malcolm later on DID figure it out!! See https://gitlab.com/gitlab-org/gitlab/-/issues/425392#note_1568228654
A
A
B
A
C
A
This
is
specific
to
issues
it's
specifically
when
an
award
emojis
on
it
and
I
know
how
to
fix
it,
which
is
if
I
remove
inverse
of
so.
If
I
remove
this
inverse
of
from
the
have
money
award
emoji,
it
works.
Everything
saves
as
expected,
and
so
you
could
say
well
just
remove
that,
and
maybe
that's
something
you
should
do,
but
I
I
really
want
to
understand
why
I
really
don't
want
to
understand
why?
Because
it's
so
weird
to
know
this
is
happening
I'm
just
this
one
model
when
they
all
have
this
defined
on
them.
A
A
Any
other
has
many
relations,
so
it
could
also
be.
Labels
are
another
thing
that
another
relation
on
an
issue
or
a
merge
request
not
on
the
snippet.
So
I
didn't
add
labels
to
this
because
Snippets
don't
have
labels,
but
if
this
test
were
just
for
issues
in
merge,
requests,
I
could
also
create
labels
and
the
labels
would
fail
to
save
as
well.
A
A
Yes,
exactly
yeah,
you
get
like
really
deep
and
then
you're
like
well
just
step
forward
and
then
you're
in
this
weird
place.
But
basically
what
I
observed
is
that
the
parent
object,
because
when
you
call
save
the
way
that
the
child
of
the
other
objects
are
saved
on
a
parent
active
record
class,
is
with
this
auto
save
associations
module.
A
It
defines
a
method
on
each
one
and
when
you
first
go
in
that,
you
can
see
that
the
parent
that
the
issue
or
merge
across
or
whatever
it
is,
has
notes
on
it
and
then
at
a
certain
point
that
gets
nulled
out.
So
basically,
like
my
hypothesis,
is
that
somewhere
the
object.
Id
changes
like
it's
reloading,
the
parent
object.
So
it
loses
all
the
other
sub-relations,
because
the
award
Emoji
is
saved
first,
so
I
think
somewhere
in
the
process
of
stating
the
award
Emoji
because
of
the
inverse
of
attribute
being
set.
A
C
B
A
A
So
I
think
that's
what
like
the
Ruby
on
Rose
guides
say
like
well,
I,
don't
know
the
Ruby
on
girls
guide
to
say
actually
nothing
very
helpful.
This
is
not
very
helpful
yeah
and
that
you
it
used
to
be
that
sorry.
Let
me
look
at
this
J.
Why
I
had
I
have
too
many
branches?
I
had
a
branch
because
there's
it
used
to
be
there
for
polymorphic
relationships
you
like
had
to
include
it
or
something
right
and
we
have
one
to
find
somewhere.
That's
like
oh
here
it
goes
a
general
case.
A
A
A
C
A
A
Which
again
makes
me
want
like
think
that
this
is
like
a
memory
reloading
issue,
because
it's
like
inverse
off
is
doing
a
memory
optimization.
So
something
is
happening.
It's
looking
in
memory,
and
so
maybe
it's
somehow
doing
a
Reload
in
this
scenario
and
that's
why
the
other
children
are
being
lost.
A
A
A
B
A
B
B
A
C
A
B
A
B
A
A
A
A
C
B
A
C
A
C
A
A
A
C
B
B
A
B
C
A
A
C
A
A
B
A
A
A
A
A
A
B
C
A
B
A
C
A
A
A
A
A
This
is
by
the
way,
the
method,
save
collection
Association,
which
is
automatically
it's
it's
the
method
that
is
invoked
by
the
other
method
in
an
active
record
relation
that
basically
says:
okay,
save
all
of
the
sub-relations
on
this
object,
so
it's
being
called
here
for
a
word
Emoji,
but
then
like
it,
never
ends
up
getting
called
for
other
relations,
because
this
call
for
a
word
Emoji,
which
I
think
happens.
First
Mills
out
all
the
other
sub
relations.
A
B
A
I
just
want
to
know
that
here
so
self
is
the
issue
this.
The
issue
has
already
been
persisted.
It
has
an
ID
and
then
notes
is
here.
This
is
the
note
and
then
record
in
this
context
is
the
award
Emoji.
So
this
is
the
Callback
that's
happening
when
it's
trying
to
save
the
children
of
the
issue,
so
it's
being
called
right
now
for
a
word
emoji
and
Theory.
It
should
also
be
called
for
notes,
but
it
never
happens
so
help.
How
do
I
watch
something
VAR,
okay,.
B
B
A
B
C
A
A
A
A
A
A
A
A
Was
a
there's
a
part
there's
a
time
and
I
was
like
what,
if
it's
like
a
Threading
issue,
and
it's
like
no,
no,
it's
definitely
just
related
to
inverse
of
so
I.
Don't
even
know
why
I'm
in
here,
but,
like
you
know
just
gotta,
see
if
you
see
something:
okay,
we're
almost
out
we're
almost
out
we're
almost
out.
B
A
A
A
A
C
A
A
A
A
A
A
C
A
It
was
never
well
in
this
context.
It
was
called
it
was
first
self
and
then,
in
the
context
of
the
ACT
record
collection,
it
was
known
as
the
owner,
so
we
had
owner
and
record.
So
first
we
had
self
like
the
issue
with
salt.
Then
we
went
into
the
active
record
collection
Association
and
that
self
was
the
collection,
it's
the
association
itself,
but
it
had
access
to
both
the
owner
and
the.
B
A
A
A
C
A
Then
it
saves
the
associations
and,
like
an
active
records,
smart,
it
seems
like
if
you
have
a
validation
on
the
parent,
that
it
has
to
have
the
child
like.
It
knows
to
not
fire
that
until
after
the
children
have
been
saved
or
something
like
it
does
interesting
stuff.
This
is
all
the
contests
are
just
calling
issue.save,
but
the
transaction
that
actually
saves
the
or
the
the
database
call
actually
saves.
The
issue
has
already
happened
now,
we're
saying
the
awardable
and
then
the
note
is
still
here
so
that
actually
isn't
memory.