►
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
D
B
E
A
B
B
B
That's
nice
yeah!
That's
a
good
one!.
C
At
the
beginning,
we
decided
to
not
support
it
because
there
was
some
rate
limiting
on
our
AWS
side
for
Native,
discrete
size
yeah,
but
I
was
probably
hard
to
place
the
rate
limit
in
six
hours,
I
think
every
six
hours
secondary
and
discrete
size.
D
I
think
we
even
have
the
when
the
rate
limit
is
hit,
it
will
do
the
it
will
fall
back
to
the
previous.
F
D
D
A
Okay,
but
there's
no
linked
issue.
Oh
there
is
this
one
right,
yeah
that
makes
sense.
Would
it
make
sense
to
add
a
test.
F
D
C
B
E
B
B
A
I
mean
I
have
never
met
any
of
you
in
person.
That's
not
true,
so
you
all
are
just
internet
people
right.
So
you
cannot
trust
internet
people.
I,
don't
know
with
with
AI
you
don't
even
I,
don't
even
know
if
you
are
real
right.
E
D
For
this,
no
not
really
so
there
is.
There
are
two
when
the
criteration
set
instance
type
set.
Vm
instance
metadata
is
where
the
function
is
called
for.
Save
labels.
E
D
Want
to
be
thorough,
I
know
why
I
found
a
commit
where
that
in
the
commit
message
where
they
said
because
Bosch
when
Bosch
created
some
metadata
tags,
it
had
like
colons
into
it
in
it
and
yeah
Google
CPI
of
the
Google
API
didn't
like
that.
B
A
Want
to
oh
yeah,
but
but
it
will
be
a
breaking
change
as
in
like
people
that
have
labels
that
start
with
a
number
and
have
now
an
n
paper.
A
A
A
Like
if
you,
if
you're
gonna
change
this
all
the
labels,
are
gonna
change
for
the
people
like,
so
it
could
also
be
that
people
have
just
been
okay
with
this
like
they
and
they
have
adopted
their
like
reporting
or
adapted
their
reporting
to
cope
with
that.
D
Yeah,
it's
it's
the
it's
just
weird
because
now
between
the
attacks
with
the,
if
you
have
like
for
multiple
ISS
like
for
AWS-
and
they
are
already
not
consistent,
but
this
makes
it
more
inconsistent.
A
I
mean
yeah
I'm
I'm,
not
yeah,
I,
don't
like
introducing
a
breaking
change
like
this,
because
people
do
rely
on
these
stacks
for
like
billing
purposes
right.
So
this
would
be
a
difficult
I
mean
sure.
Without
the
end,
it's
probably
more
correct,
but
it
yeah
it
will
break
billing
for
some
people.
A
D
A
D
F
D
A
Lots
of
there's
lots
of
those
mistakes
in
her
that
that
were
made
in
the
past
I.
B
A
C
Data
approach
could
be
to
check
whether
there
is
already
a
label
or
existing
with
n
in
front.
If,
yes,
then,
don't
do
anything
but
I
don't
know
how
expensive
we
could
be
such
a
check.
B
D
B
Check
the
mileage
again
yeah.
A
D
That
that
fit
thing
was
introduced
again,
so
I
needed
to
revert
this
in
the
commits
with
stocks.
But
it's
way
more
work
for
me
to
get
all
these
things
in
again,
to
create
a
new
branch
and
to
fix
this.
D
E
D
To
add
those
okay,
this
is
the
and
that's
the
first
and
the
last
commit
yeah.
That's.
B
My
mistake
that
just
sucks.
B
E
D
And
all
the
other
ones
are.
This
is
basically
all
terraforming
to
be
compatible
with
with
the
newest
terraform.
D
F
A
D
D
A
E
D
After
that,
we
can
iterate
pretty
new
things.
Yeah.
B
E
B
A
B
B
G
Yeah
they
had
a
lot
of
progress
on
this
ticket
yeah
and,
unfortunately,
finally
finds
the
issue
which
is
related
to
the
Bosch
agent
or
stemsia,
and
we
also
based
on
issue
our
Landscapes,
because
the
issue
is
actually
caused
by
both
agent
restarts.
So
after
the
restart
of
the
boss
agents,
some
mounting
operations
will
fail.
Onset,
VM
and
currently
there
is
a
new
release
on
zip
Jaime
stem
cell
very.
D
B
D
Because
if
you
do
remount,
if
you
use
the
remount
option
for
Mount,
then
you
don't
have
this
problem
yeah.
So
this
would
like
be
it
to
a
two-step.
Basically,
the
the
new
stem
cell
already
has
their
fix
in
it
that
released
yesterday.
A
Tracked
the
problem
down
to
Rooney
crony
again.
A
D
G
And
it's
and
it's
a
beauty
option
from
the
month
comment.
Instead
of
we
do
the
U
Mark
and
month
into
steps.
A
D
G
So
in
our
scenario
we
see
we
have
an
upgrade
of
the
stem
cell
from
1.83
to
8.9
1.93
and
we
have
our
certificate
rotation
in
the
settings.json
file
of
the
Bosch
agent,
so
which
means
there
is
a
system
update
and
also
the
changes
of
the
settings.json
file
Loop
to
the
restart
of
the
watch
agent.
Then
the
problem
occurs.
So
it
could
be
that
some
of
the
commits
in
between
the
1.83
and
1.93
durable
to
this
problem
so.
G
G
It
works
now
because
we
have
two
problems.
One
problem
is
okay
occasionally
occur.
When
is
we
can
reproduce
it
so
yeah?
We
just
use.
We
just
upgrade
system
cell
to
1.95
today
and
the
of
the
permanent
issue
or
the
reproducible
issue
is
resolved
and
occasional
issue
doesn't
occur
again,
so
we
assume
that
is
also
resolved.
Yeah.
A
Yeah
the
intermittent
issue
you
want
to,
but
for
that
to
you
want
actually
some
more
time,
probably
to
really
call
that
fixed
yeah
exactly
okay.
Maybe
it
makes
sense
to
keep
it
open
for
another
week
and
then
you
all
can
like
give
an
update.
If
the
intermission
intermission
intermittent
issue
has
also
been
resolved,
and
then
we
can
like
I
mean
this
issue
is
basically
done.
Then
it's
more.
We
there
could
be
further
improvements
with
the
integration
test
right.
D
Yeah
we
will
see
after
yeah.
Let's,
let's
see
what
happens.
B
A
C
D
We
can
do
it
in
the
same
deployment
like
deploy
this
and
then
also
upgrade
VM
type
in
this
size.
So
we
don't
have
to
add
an
extra
test.
I
think
we
should
just.
A
And
this
also
had
to
do
with
the
foreign
yeah,
the
restarting
of
the
agent
right.
So
this
is
the
short-lived
credential.
A
F
A
Okay,
what
else
do
we
have.
A
D
F
D
Because
everyone
I
know
who's
using
Azure
can
use
it
at
the
latest:
stem
cells
bionic
or
any
things
that
don't
have
any
problems.
So
I
think
it's
specifically
to
that
task
that
he
is
executing.
So
it's
not
a
deployment,
but
he's
he's
doing,
create
release
or
something
I
think
wait.
D
D
C
I
was
thinking
whether
he
needs
to
downgrade
at
all
or
just
under
the
commit
that
commit
and
try
it,
but
most
probably
he
needs
also
to
downgrade
the.
D
F
D
A
F
A
D
D
Any
agent
idea
that
was
the
whole
the
whole
problem
right
yeah
out
of
this
space
of
out
of
memory,
could
also
cause
like
weight
at.
C
Some
point
he
mentioned
something
that
the
discourse
to
they
required
larger
root
file.
D
D
F
C
D
F
D
D
Because
Germany
is
a
whole
lot
bigger,
but
he
also
has
it
with
bionic
and
it
changed
from
one
point
to
another.
F
D
A
B
A
B
C
F
A
It's
based
on
like
the
time
the
the
number
of
files
changed,
so
it
needs
to
have
at
least
10
files
that
were
changed
and
it
needs
to
be
reviewed
for
a
longer
period
of
time,
because
I
found
that,
like
things
that
change
a
lot
of
files,
but
are
like,
say
automated
stuff,
like
dependency,
bumps
or
stuff
right,
those
typically
got
merged
pretty
quickly.
So
like
the
more
the
more
complex
features,
typically
sit
and
review
for
at
least
more
than
a
week,
and
they
have
more
than
10
files
got
changed.
So.
E
A
C
But
the
idea
is
great:
yeah
I
think
it's.