►
From YouTube: 2022-03-23 Workspace meeting
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
A
I
hope
it's
alexandra
will
join
as
he's
like
the
as
I
would
like
to
say:
congratulations
in
person
or
in
zoom
at
least
somebody.
We
can
wait
a
minute
she's
going
to
join.
A
Okay,
so
alexander's
not
trying,
so
maybe
I
will
update
you
real
quick,
so
the
big
migration,
the
migration
that
we
were
working
on
for
a
long
time-
and
it
was
like
the
huge
chunk
of
work
for
phase
one-
ran
on
production
about
any
bigger
hiccups
so
far,
but
we
hope
it's
about
any
bigger
hiccups
and
I
just
want
to
say
like
congratulate
to
the
whole
team,
as
this
is
a
huge
milestone
and
we're
working
on
this
for
many
months
with
many
counterparts
engaged
in
this
in
this
work.
A
So
this
is
congratulations
and
thank
you
for
all
all
people
involved,
including
people
from
plan
team
that
were
also
working
on
this
in
the
previous
milestones.
A
Okay,
we
have,
we
had
some
failed
jobs
on
the
initial
run,
but
it
was
probably
due
to
the
due
to
the
pots
restarting,
but
I
think
there
were.
There
are
fixed
on
the
retry.
We
only
have
like
600
projects
that
are
not
migrated
because
of
the
unique
constraint
failure,
but
we
will
work
also
with
project
managers
on
identifying
a
way
out
of
this,
probably
ins
like
surprise.
Migration
will
update
the
the
ones
that
are
failed
in
the
first
run,.
A
Okay,
so
I
the
next
question
that
I
had
was:
oh
okay,
hello,
hi
alexandra.
I
just
basically
verbalized
your
points
from
the
first
from
the
first
five,
but
I
would
like
to
say
once
again
that
a
huge,
huge
congratulations
on
on
the
successful
run
of
the
of
the
big
migration.
A
A
I
also
mentioned
our
the
problem
with
the
namespaces
that
projects
that
were
not
like
the
specific
or
not
created
because
of
the
name
clash.
Do
I
understand
correctly.
B
B
Do
we
want
to
append
like
the
id
or
something
to
the
end
of
the
name
and
path
or
whatever
way
we
want
to
fix
that,
so
that
it
becomes
unique
so
that
we
can
so
basically,
what
we
need
is
have
the
same
name
and
path
in
both
project
and
the
namespace
version,
because
what
we
do
we
want
to
keep
that
those
things
in
sync
to
have
them
like
be
the
same,
so
that
when
we
decide
to
move
away
from
projects
we
don't
we
don't
get
any
unexpected
behavior
for
the
user
when
they
start
seeing
a
different
name
or
a
different
path.
B
So
yeah,
that's
what
like
it's
a
tiny
amount
compared
to
the
overall
number
of
projects,
but
it's
still,
I
think
it's
somewhat
a
blocker
just
because
you
cannot
fully
rely
that
everything
in
the
like
every
project
has
a
a
project
name
space.
So
from
like
from
engineer
perspective
from
code
perspective,
you
always
need
to
like
have
those
checks
versus
if
we
fix
that
and
we
introduce
the
the
constraint
the
project
namespace
id
can
no
longer
be
null.
Then
you
basically
have
that
guaranteed.
B
So
yeah.
That's
that's
that,
with
the
with
the
fix.
A
B
Projects
how
to
handle
them
yeah
I
was
looking
to.
I
was
trying
to
look
actually
for
the
root
cause.
I
could
not
understand
where
that
is
coming
from
I
mean
on
the
projects
table.
We
don't
have
a
constraint
so
that's
possible,
but
but
on
the
product
side
like
on
in
the
application,
we
do
some
validations,
which
is
not
bulletproof,
obviously,
but
then
in
the
routes.
B
Maybe
it's
something
that
is
legacy
somehow.
It
was
migrated
because
there
were
conflicts
on
the
routes.
I
think
I
have
no
idea
but
yeah,
regardless
of
the
root
cause
we
can.
We
can.
I
I'll
start
writing
a
migration
to
to
kind
of
update,
because
I
think
that's
the
only
basically
way
is
to
to
change
other
than
deleting
the
project.
B
The
only
way
is
they
like
to
update
the
payment
and
the
path
so
I'll
start
on
a
on
a
migration
in
that
regard,
and
then
we
can
decide
if
we
want
to
appeal
the
id,
whether
it
be
a
sequential
number
or
something
along
those
lines.
A
What
about
you
mentioned,
keeping
name
of
the
project
in
sync
between
namespace
and
project,
namespace
and
project.
We
should
also
address
that
probably
urgently.
A
Okay-
okay,
great
so
amazing,
okay,
so
I
will.
I
will
write
the
issue
for
that
and
engage
with
a
product
as
soon
as
possible
to
make
decisions.
So
we
can
address
this
problem
quickly.
B
B
So
I
I
like,
in
my
in
my
mind,
will
will
fix
these
fewer
records
and
then
run
the
migrations,
but
I
I
don't
think
there
is
a
strong,
no
goal
like
we
can
run
the
migrations
as
they
are,
and
then
I'm
just
not
sure
if
it
will
not
create
a
bigger
mess
later
on,
like
where
you
need
to
like
look
through
a
lot
of
these
records.
Maybe
we
find
something
else
and
then
you
need
to
have
yet
another
regulation
like
that.
I
don't
exactly
know
so.
I'd
rather
have
this
back
feeling
of
the
project
basis.
B
Finalized
verify
make
sure
that,
like
we,
we
don't
have
any
other
kind
of
bugs
in
the
code
where
we
allow
for
that,
introduce
that
that
constraint
on
the
project,
namespace
id
and
then
move
on
with
the
backfilling
of
of
other
stuff.
A
Okay,
that
makes
sense
for
me
so,
like
maybe
finalizing
first
thing
and
then.
B
Yeah,
I'm
thinking
right
now.
Actually
I
think
we
can
start.
We
can
actually
add,
probably
the
not
no
constraint
which
can
be
a
not
valid
constraint,
which
will
act
on
any
new
project
namespaces
basically,
but
we'll
have
those
like.
So
the
problem
with
introducing
the
constraint
now
is
that
these
600
something
projects
whenever
user
would
try
to.
B
I
don't
know
if,
when
they
try
to
update
it,
they
will
fail
or
not,
maybe
not.
Actually,
I
would
need
to
check
so
yeah.
Maybe
maybe
the
next
thing
is
to
actually
introduce
this
not
null
constrained,
and
then
this
kind
of
unblocks,
the
backfilling
of
everything
else,
except
for
these
few
projects
that
that
we
can
backfill
afterwards,
because
it's
just
so
so
few
of
them.
B
B
Either
way
to
just
make
sure
that
we
don't
because
once
we
have
the
constraint,
we
will
see
exceptions
if,
somewhere
in
the
code
we
are
trying
to
to
set
up
the
namespace
id
to
know.
We
will
get
exceptions
so
that
we
can.
We
can
fix
that
code
path
because
it's
obviously
some
sort
of
an
edge
case
somewhere
that
we
didn't
check,
so
it
should
not
be
happening
anymore.
B
B
A
Okay,
if
there's
there's
nothing
else
I'll
give
you
your
15
minutes
back
and
thank
you
so
much
for
today
and
once
again
huge
congrats.
I
think
it's
it's
worth
to
say
it
out
loud
as
many
times
as
possible.
I
think
we
were
waiting
for
those
moments
for
so
long,
so
we
should
celebrate.