►
From YouTube: 2022-01-19 Code Review Weekly Sync
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
All
right,
so
the
only
one
on
the
agenda.
This
was
brought
back
up
yesterday,
and
so
I
thought
it
would
be
interesting
to
talk
about
since
we're
meeting
today.
Anyways-
and
this
is,
I
know,
thomas
you've-
done
a
lot
of
investigation
on
this-
that
the
generically
merged
request.
Diffs
are
broken
when
there
are
large
files,
which
is
not
a
great,
a
great
issue
to
solve
a
problem
for,
but
I
was
trying
to
get
some
clarification
in
that
it
seems
like.
C
Go
ahead,
andre
I
I
actually
can't.
I
can't
see
the
the
document
right
now,
so
I
don't
know
exactly
what
the
topic
is.
But
yes,
all.
B
That
is
true,
okay,
so
I'll
I'll
complete.
So
a
couple
miles
ago.
Yes,
thomas,
did
a
big
analysis
on
two
issues.
Actually
that
was
causing
some
rendering
issues
and
we
thought
basically,
the
conclusion
or
the
the
gist
is
that
we
definitely
have
a
very
complex
front-end
application.
When
there's
a
lot
of
data,
it
breaks
down
so
yeah
and
we're
entertaining
several
threads
of
conversations
around
the
path
forward.
B
But
I'm
with
you,
I
think,
there's
something
here.
I
looked
at
the
video
and
it
seems
like
the
scrolling
might
be
showing
a
weird
bug,
which
is
a
separate
conversation
from
the
original
issue
that
caused
this
issue.
So
it's
not
really
just
because
of
the
big
file,
I
think
there's
something
there.
We
have
been
working
on
scrolling
and
stuff,
so
that
might
be
something
that
we
cause
the
regression
or
something.
B
B
So
maybe
we
can
include
that
work
in
that
issue,
because
we
need
to
fix
it
basically,
because
so,
basically,
what
we
see
in
the
video
is
like
when
you
click
to
leave
a
comment
you
jump
to
another
part
of
the
page
and
that
shouldn't
happen.
That
should
not
happen
at
all.
So
I
think
that
there's
a
bug
which
is
then
causing
that
report
from
that
that
customer
he
got
thrown
into
this
issue
because
it
does
seem
similar,
but
but
the
original
thing
is
completely
separate.
B
So
I
think
thomas's
analysis
is
great
to
lead
those
more
long-term
conversations
and
strategies
to
rethink
diffs
right
now.
We
should
totally
look
at
this
into
interim.
A
C
Anything
no,
I
generally
I'm.
I
am
disappointed
with
the
way
that
our
scrolling
works.
C
It
seems
like
it's
like
whack-a-mole
sort
of
like
fix
something
and
then
something
else
pops
up
and
we
fix
something
and
something
else
pops
up,
and
I
I
don't
really
have
a
great
solution,
but
I'd
really
like
to
get
like
the
way
that
we
manage
scroll
position
really
lock
down.
So
this
stops
happening.
B
Yeah
yeah
there's
a
couple
of
trade-offs
that
we've
made
in
the
past
I
mean
once
we
were
talking
about
virtual
dom,
then
we
no
longer
operate
in
a
direct,
full,
dom
access
mode.
So
there's
a
couple
of
technicalities
on
the
front
and
that
okay
brought
us
down
this
this
path
and
we're
thinking
about
rethinking
it
all
from
scratch.
B
How
we
do
diffs
how
we
render
them,
how
interact
with
them
all
that
stuff
is
being
up
to
be
reevaluated,
but
that's
a
long-term
thing
and
we
need
to
clean
the
house
now
so
yeah
we'll
look
into
that
during
this
milestone.
It's
slightly
related
to
things
we
already
have
on
the
pipeline,
so
I
don't
think
we
need
to
schedule
this
in
particular,
but
I'll
leave
a
comment
on
that
issue,
directing
people
to
the
one
that
is
being
scheduled
so
that
they
can
follow
the
evolution
there.
B
If
we
did
schedule
this
then
schedule
this
issue
specifically,
then
the
expectations
some
people
will
be
expecting
a
completely
different
output
than
the
fix
of
that.
But.
A
B
Okay,
it
was
not
create
another
issue:
yeah,
okay,
we'll
create
another
issue
for
that
particular
bug.
I'll
leave
a
comment
there
do
explaining
this
that
I
would
what
I
just
said
saying
that
all
right,
based
on
the
of
the
video
I'll,
create
another
issue
separate
from
this,
because
we
don't
want
to
close
that
we
don't
want
to
rename
this
one
as
well,
so
we'll
open
a
new
issue,
I'll
direct
people
there
and
we'll
work
on
that
for
today.
A
I
am
not
pressing
to
move
it
to
14
8,
I
guess
is
how
I
feel
about
it.
I
feel
if
we
want
to
put
it
in
14
9,
that's
fine.
I
think
I'd
rather,
I
know
we're
on
a
path
in
fourteen
seven,
eight
nine
to
like
fix
the
jump
to
next
shenanigans
is
the
best
word
and
so.
A
A
I
will
also
say
I
believe
this
customer
is
on
an
older
version
of
get
okay,
based
on
a
comment
that
jamie
left
in
another
issue
that
they're
like
14-2,
and
so
even
if
we
fix
it
in
8,
it
doesn't
really
matter
they're,
not
there
and
if
they're
fixed
in
49
they're,
not
there
either
right
so
and
we
don't,
we
don't
get
a
ton
of
reports
of
this
sort
of
behavior
either,
which
is
also
makes
me
wonder
if,
like
although
jamie
reproduced
it
on
dot
com
but.
B
Yeah,
okay,
we'll
look
into
it.
I
understand
that
you're
not
pressing
to
pick
it
up
right
now,
but
I
feel
like
if
this
is
happening.
It
is
disruptive
and
this
would
fall
under
that
category
of
usability,
bug
which,
even
if
it's
severity
too
like
immediately
makes
it
a
priority
one.
So
we'll
just
we'll
just
take
a
look
at
it.
I
think
honestly,
this
might
fall
under
the
category
of
a
regression,
but
since
it's
been
there
since
142,
apparently
at
least
yeah,
it
might
be
a
silent
one
or
a
transient
one.
B
So
we'll
take
a
look
at
it.
We
won't
commit
a
lot
of
resources
to
it,
but
we'll
take
a
look
at
it
for
sure.
Thanks
for
bringing
it
back.
A
D
So
I
just
act
on.
I
have
a
vague
memory
that
I
was
supposed
to
do
something
with
this
issue
that
we
discussed
last
week.
I
didn't
do
that.
So,
if
I'm
blocking
this,
what
can
I
do
to
unlock
it,
or
are
we
good
to.
B
Go
so
if
I
remember
correctly,
the
idea
was
to
reach
out
to
people
in
growth
just
to
see
how
they
usually
handle
these
sort
of
things
if
they
have
any
advice
or
something
for
the
rollout,
but
we
didn't
block
it.
I
believe
I
feel
like
we're
good
to
go
in
that
front
right,
kai.
B
A
Privacy
or
other
things
and
we're
doing
it,
I
think
we
have
everything
we
need
to
go
implement
it.
As
far
as
I
know,.
B
A
B
B
The
links
so,
of
course
that's
not
what
I
wanted
to
do.
Apologies,
I'm
screwing
up
the
agenda.
B
All
right.
This
will
do
nicely.
So
that's
the
issue.
You
want
to
bring
into
14
8,
revisit
the
mremt
states,
and
then
I
gave
you
the
link
for
the
issue
board.
Then
you
came
back
with
that
follow-up.
So
a
context,
that's
a
follow-up!
Yes,
it's
it's
improved
testing
and
it's
a
sort
of
a
tech
debt
follow-up
thing
that
we
would
like
to
address.
B
Mostly
it's
because
it's
unblocked
work,
it's
kind
of
like
straightforward
engineering,
work
that
we
want
to
put
out
and
improve
the
the
code
base.
I
was
thinking
about
some
other
kind
of
work
because
feature
feature.
Work
does
involve
more
time
and
I
would
like
to
keep
it
in
for
for
addressing
that
that
it's
growing.
So
did
you
see
anything
else
in
your
that
you
could
throw
out
stop.
B
Points
yeah
yeah.
We
already
have
a
bulky
milestone,
not
a
lot
of
pto,
so
we
have
a
lot
of
issues
to
juggle.
So
that's
why
I'm
being
careful
with
that
one.
A
I
know
I
don't
necessarily
have
anything
else
that
like
stands
out
as
something
we
should
pull
out
in
favor
of
this
one.
B
It
was
one
from
the
merge
button
flashes
back
to
active
again
after
clicking.
That
was
one.
A
B
Can
put
it
as
a
stretch,
we
know
what
that
means
that
we
usually
don't
get
to
them,
but
I
mean
I
saw
the
the
show
function.
Signature
in
dis,
that's
a
new
feature,
but
it's
still
nice.
I
guess
ui
update.
It's
always
nice.
I
don't
know.
A
Yeah,
I
think
I
think
what
we'll
do
is
we'll
148.
It
stretch
it,
which
is
essentially
what
had
been
happening,
every
milestone,
anyways
and
then,
when
we
get
to
14
9,
we
just
need
to
make
a
more
conscious
effort
to
like
groom
this
back
over
to
the
deliverable
side
for
14.9
right
that
works.
For
me,.
B
Nobody
said
anything
about
my
logo:
a
little
logo
over
there.
I
noticed
it,
hey
I'm
playing
around
with
obs.
So
there's
a
couple
of
things
that
I
can
do
now
and
I
can
do
that
and
I
can
do
that-
and
I
can
do
that
too,
and
I
can
just
go
back
to
webcam
I'm
playing
around
I'm
just
joking
great
to
see
everyone.
A
Good
to
see
everyone
enjoy
the
rest
of
your
day
and
enjoy
the
week.