►
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
Always
start
with
the
back
work
or
the
dashboard,
do
you
have
anything
else
to
discuss.
A
Upstream
issue
for
the
Azure
storage
CLI.
So
it's
still
pending
review.
B
Yeah
Reuben
thought
it
was
a
good
idea
to
let
other
people
look
at
this.
Yes
sure
I
know
I'm,
not
sure
why
Ram
would
check
this,
but
as
a
reviewer,
but.
A
Yeah
yeah,
let's
see
I,
will
leave
it
in
the
state
for
another
week.
Then,
if
there
is
no
progress,
we
can
discuss
it
next
week.
Okay,.
B
I'm
still
working,
so
this
is
working
when
I'm
not
working
on
I'm,
getting
the
acceptance
test
and
the
new
terraform
going
on
like
business
to
basically
get
watch
bootloader
up
to
date
and
get
it
fixed
again.
B
Probably
going
also
to
fix
that
you
can
run
it
again
from
our
Mac
OS
vectors.
A
B
We're
still
using
an
old
terraform,
basically
and
yeah.
We
need
to
run
Pump
It
Up
on
points,
but
why
this
happened
is
because
Packer
is
basically
it's
obsolete
and
it
cost
a
whole
lot
of
issues
to
build
it
locally
and
to
have
it
to
get
the
CI
working
every
time.
B
We
can
now
go
to
go
120
in
the
meantime,
but
yeah
so
just
just
need
to
review
from
people.
I
already
responded
on
Reuben's,
Ruben,
stuff.
A
B
A
Okay,
then,
this
is
yeah
also.
A
Yes,
yeah,
so
I
also
can
not
totally
judge
on
this,
so
I
will
leave
it.
B
A
A
Know
yeah,
so
this
should
be
pending
radio.
So
let's
yes,
move
it.
A
So
this
looks
like
something
relevant.
A
So
it
looks
like
the
indexes
has
to
be
rebuilt,
for
example
at
the
second
point
is
most
probably
relevant
for
everyone.
The
first
one
is
only
for.
B
B
A
Yeah,
okay!
Well
then,
yeah.
B
But
Reuben
is
already
in
there
and
Constantine
right
so.
B
I
think
we
just
we
had
news
to
re-index
I.
B
Mm-Hmm
yeah
I,
don't
know
what
the
files
are,
but
I
can
I
can
check
this
tomorrow
could
go
over
this
because.
A
Here
is
the
statement
is,
but
if
this
is
required,
it's
up
to
the
operator,
so
the
updates
in
this
commit
us
doing
it.
So
nothing
happens
automatically.
So
it
has
to
be
triggered
manually
if
it's
required.
A
Yes,
I
already
commented
here.
There
was
something
similar
in
the
pr
which
is
already
merged.
A
And
that
time
constantly
analyzed
what
the
situation
is,
I
think
it
will
be
nice
to
have
a
walk
into
this
delay.
Job
table,
which
represents
the
state.
What
has
been
executed
and
the
tasks
table
is
so
to
say
what
you
see
when
you
execute
CF
tasks
and
they
can
come
out
of
Zoom.
B
A
But
for
the
situation
which
is
described
in
this
issue,
the
pr
won't
help.
It
has
also
some
cleanup
orphan
tasks,
logic,
which
maybe
we'll
clean
up
the
tasks
which
you
see
here.
A
C
Yeah
two
days
ago,
I
merged
two
days
ago
so
and
we
should
check
it
on
on
staging.
A
Yeah
introduced
some
cleanup
Logic
for
the
orphan
tasks
and
some
retries
in
case
the
database
is
not
reachable
so
that
the
state
they
don't
get
out
of
sync.
C
B
But
I
because
the
worker
checks,
this
ID
check
this
things
and
we'll
just
run
it.
It's
not
that
it
it's
uses
its
own.
It
does
not.
Caching,
like
the
worker.
C
C
B
A
Is
a
comment
that
seems
to
be
exact
same
scenario:
I
checked
the
one:
that's
there
is
an
update.
That
seems
to
be
exactly.
B
Okay,
I
will
have.
B
C
A
A
B
Think
at
the
point
where
we
at
some
point
where
we
basically
a
process
within
Bosch
or
the
database
or
whatever
we
just
switch
something
and
in
the
pre
and
in
the
meantime
it
added
this
task,
and
then
it
basically
didn't
do
anything
with
it
and
it
just
stuck
there.
C
Okay,
so
the
issue
here
was
that
we
switched
to
a
new
to
our
credential
rotation
and
beforehand
we
had
one
user
and
afterwards
we
two
new
users
and
we
completely
invalidate
the
the
old
user,
and
during
this
step
we
saw
this
issue.
So
after
we
we
moved
to
the
new
credential
or
to
the
new
users.
C
We
still
had
this
very
old
tasks.
You
can
see
that
they
are
from
January,
and
only
this
operation
produced
this
Q
task.
We
don't
see
all
the
or
newer
Q
tasks.
It's
only
from
this
user
change.
A
So,
let's
check
so
it
those
tasks
are
finished,
but
the
update
into
the
tasks
table
wasn't
successful.
That's
why
they
are
there
and
the
pr.
This
PR
introduced
some
logic
to
delete
the
orphan
tasks,
but
what
I
suggest
is
to
check
in
your
case
whether
the
tasks
were
really
executed,
because
in
this
case,
when
the
connection
to
the
database
was
failing,
they
were
executed
just
to
update
to
the
topics
tasks
table
failed.
A
A
If
it's
the
case,
then
the
pr
here
Will
clean
up
those
and
everything
is
fine.
If
not,
then
we
maybe
have
to
do
something
else.
Additionally,.
A
A
Sure
why,
if
you,
if
you
do
the,
if
you
do
the
Json
output
to
update
there
good
question.
C
A
To
do
it,
okay,
I
think
we
have
now
minutes.
Time
is
too
short
to
get
an
understanding,
but.
A
A
Okay,
so
I
think
we
are
fine,
then
yeah
yeah.
If
there
is
nothing
else.
A
Then
I
wish
you
a
nice
evening,
yeah.
B
I
wish
it
was
a
nice
evening
and
see
you
next
week.
Yeah
I
do.