►
From YouTube: Weekly Compliance Pairing - Aug 3, 2023
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
Hey
welcome
to
backend
pairing
for
compliance.
We
all
right
so
I'll
start
sharing.
A
A
Where
is
thread
there?
We
go
the
big
one
yeah,
so
we've
had
some
database
maintainer
feedback
and
I'm
currently
trying
to
take
some
of
that
into
account
specifically
like
the
last
one
from
Adam,
where
He
suggests
not
putting
a
finder
query
in
the
in
operator
query,
but
then
just
loading
the
records
afterwards
I
sort
of
started
that
here:
okay,
where
I'll.
A
Do
it
here
grab
basically
the
IDs
and
then
load
them
afterwards
as
the
records?
A
It's
ordered
by
that's
just
the
okay,
it's
the
last
500.
ID
descending
yeah,
so
export
the
last
500
violations,
which
is
okay,
start,
but
not
what
I'm
looking
for
I
would
like
to
do.
All
of
them.
A
B
A
A
D
A
A
very
common
use
case
where
we
have
a
sub
query
with
that's
an
in,
and
this
is
sort
of
an
observation
and
the
the
scope
parameter
is
basically
like
where
to
search
in
so
we're
searching
compliance
violations
and
the
array
scope
is
basically
like
the
in
so
we're
searching
in
a
certain
range
of
project.
Ids.
A
A
A
B
That
makes
sense
to
me
it's
good
yeah.
So
on
that
page
you
were
looking
at
I.
A
A
I
haven't
gotten
into
that
fully
yet,
but
yeah,
that's
just
that
is
a
page.
I
was
like
calling
up
before
the
pairing
and
then
I
haven't
had
a
chance
to
really
really
yeah
yeah.
A
B
A
What
we're
looking
for
batch
of
Records
possible
with
the
iterator
class.
C
A
B
B
Are
you
just
testing
with
the
games
database
slab
when
you
like?
How
are
you
running
this
locally.
A
A
You
check
the
double
naming
now
since
I
already
used
records.
C
A
B
A
B
Is
this
correct,
though,
because
it's
just
batch
of
a
hundred.
A
D
A
B
D
B
A
B
D
D
A
D
B
I,
don't
know
about
you,
but
if
my
GDK
is
never
explode,
I
like
tail
the
development
log
and
then
I
also
dgdk
tail
and
I
swear
it
speeds
up
because
it
notes,
let's
be
I'm
watching
it
like
the.
A
So
it's
a
Quantum
State
dependency,
yeah,
yeah,
yeah,
I
kind
of
feel
that
sometimes
it's
like.
Oh
no,
a
big
watch,
I
better,
not
yes,
dilly
dally,
yeah,
no
output
coming.
Someone
knows.
A
So
I
guess
that
works
better,
throw
that
away
then.
A
A
Was
the
initial
pretty
sure
it
was
the
initial
review
or
shark
I
had
a
comment
about
that?
Let
me
see,
or
maybe
it
was
life.
B
C
C
C
A
Yes,
that's
stupid.
All
right,
so
I
usually
grab
that
and
then
I'll.
A
A
Yeah
I,
don't
I,
don't
clean
this
up
very
often
I
just
this
is
like
I
only
use
vs
code
like
as
a
Dumping
Ground,
usually
pair,
not
that
that's
supposed
to
reflect
on
vs
code
itself.
A
Last
night
yeah
yeah,
and
then
you
can
just
you
basically
tag
them
with
a
name
or
less
and
you
can
find
them
better.
A
It
has
a
bug
because,
as
soon
as
it
paginates,
it
forgets
that
you
said
my
history
because
then
it'll
start
showing
up
either
it's
fixed
because
I'm
showing
it
now.
A
It
knows-
maybe
maybe
it's
fixed.
That
would
be
cool
because
last
time
I
tried
it.
It
was
like
as
soon
as
it
started
paginating
then
it
started
showing
like
other
people's
queries
as
well,
and
it
felt
kind
of
useless
at
that
point,
but
it
looks
fixed.
That's
cool
thanks,
okay,
the
bug
I
meant
to
report,
but
haven't
yet.
Let's
don't
need
to
anymore
yeah,
but
yeah.
That's
the
that's!
The
life
hack.
B
Is
that
post
warm-up,
or
do
you
just
care
about
the
cold.
A
I
recently
had
it
comment
down
here.
This.
A
B
C
D
B
A
B
Yep,
did
you
sorry,
did
you
keep
the
paginated
amount
to
a
hundred
in
this
in
this
case,
or
was
it
500?
That's
what
you
originally
wanted?
Okay,
yeah!
It's
a
hundred.
C
A
B
B
Of
it's
definitely
good
that
you
have
examples
of
both
because
yeah
we
can
see
it
reduced
it
by
half
almost
yeah,
so
I
I
feel
like
if
you
put
limit
20
just
for
fun.
It's
gonna
be
very
close
to
that
50
000..
Let's.
C
A
C
A
That's
what
I'm
looking
for
I
think
let's
go
maximum
time.