►
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
Okay,
let's
start.
A
C
B
B
B
Looking
into
that,
but
yeah,
why.
C
I
think
it
was
always
the
times
yeah
and
it's
I
don't
know
the.
D
Problem
is
Java
because
it
tries
to
it
tries
to
get
all
the
search
and
Implement
them
one
by
one
by
one
and
it's
because
they're
also
using
like
Java
5
or
something
really
old.
A
D
D
Yeah
I
thought
there
was
a
hard-coded
hard-coded
dependency
on
on
UAA
so
that
it
would
wait
for.
D
C
I
saw
it
now:
what
is
the
behavior?
It
doesn't
wait
and
fails
and
doesn't
retry.
B
C
D
This
is,
is
this
with
each
up?
Is
this
with
each
Bosch
update,
or
is
it
just
the
first
upgrade
when
we
go
to
the
new
Nets
2.0.
B
I
don't
test
this
so
with
the
first
deploy,
but
maybe
it's
the
general
issue.
We
should
check
that
just.
A
A
Interesting,
can
you
create
an
issue
so
that
we
can
at
least
have
the
discussion
somewhere
or
find
this
information
yeah.
B
I
found
it
some
some
minutes
ago,
so
I
would
create
an
issue.
D
Yeah
I'm
still
working
on
that
skip
it,
because
this
is
basic.
I
can
remove
this.
It's
basically
draft
I
didn't
yeah.
It
didn't
work.
A
Okay,
then
I
will
that's
right
up
there.
D
A
Yeah,
okay,
can
you
convert
it
to
the
draft?
Apparently
I
cannot.
A
This
one
yeah
still
waiting
for
our
Constantine
to
make
a
few
few
changes.
Connie
had
some
things,
so
it's
just
a
lot
of
work,
so
that
will
take
some
more
time
and
then
we
have
oh
wow.
This
looks
like
a
good
PR.
A
The
this
feature
is
basically
around
being
able
to
Reserve
all
the
memory
of
vsphere
I.
Don't
know
if
it's
relevant
to
you
all,
because
you
don't
use
fees
here,
but
I
mean
yeah.
It's
just
a
way
to
allow
you
to
reserve
all
the
memory
and
have
fill
if
you
have
multiple
clusters.
A
Try
the
next
cluster
if
it
fails
to
power
on
on
the
first
cluster
because
of
no
more
memory
right.
So
this
is
something
we
had
to
do
for
a
certain
customer.
So
that's.
Why
there's
a
bit
of
a
rush
to
get
this
through?
It's
currently
failing
on
CI.
Apparently
it
doesn't
work
on
an
old
version
of
vsphere.
So
that's
what
I'm
working
on
yeah!
A
That's
it
from
that
side.
We
are
currently
looking
into
what
is
it
we
had
issues
or
we
have
had
reports
of
people
that
experienced
slower,
deploys
and
then,
like
I,
don't
know
on
bigger,
deploys
things
take
a
bit
longer
and
that
I
remember
correctly,
is
since
we've
upgraded
to
Ruby
3.0,
probably,
and
it
seems
to
be.
We
also
have
reports
that
there's
a
lot
of
memory
or
more
memory,
consumption
on
with
higher
versions
of
Ruby
Ruby
3.0
on
jammy.
A
So
these
things
we
are
currently
investigating
to
figure
and
we're
blocking
a
release
on
that,
because
it's
yeah
too
many
separate
issues
that
all
have
to
do
with
performance.
So
we're
doing
a.
C
A
C
A
So
that
was
warm
right.
So
that's
the
event
machine
removal
thing.
So
that
was
one.
So
that's
what
we
tried
as
in
there,
there
was
one
way
to
get
the
of
refund
one
source
of
the
memory
consumption
going
up,
and
that
was
apparently
a
van
machine
and
event
machine.
We
are
on
a
version.
That's
still
not
released
right,
so
there's
a
3.0
compatible
event
machine
version,
but
that's
only
a
monster.
A
So
a
bear
event.
Machine
is
not
really
well
maintained
anymore.
So
that's
like
a
big
thing
that
we
eventually
should
remove
and
it
was
leaking
or
I,
don't
know
if
it's
leaking
memory,
but
was
not
efficient
anymore.
So
in
some
parts
of
the
code
we
actually
didn't
need
it
anymore,
because
we
already
moved
to
a
different
Nets
client
like
we
got
event
machine
in
because
of
the
asynchronous
nature
of
nats
I.
Think
the
early
versions
of
maps
were
also
using
event
machine
quite
heavily,
but
newer
versions
aren't
so
yeah.
A
That
was
just
a
a
cleanup
thing.
Basically
so
that
was
released
in
the
latest
director
release,
but
we
want
to
do
more.
It's
still
not
so
the
memory
consumption
is
still
higher
than
it
was
on
senior.
A
So
one
thing
that
we're
exploring
is
using
C
line
as
a
compiler
for
Ruby,
but
we
still
need
to
explore
that
more.
So
we
have
had
some
result
seen
some
results
where
the
memory
consumption,
when
we
use
a
ruby
compiled
with
sea
lion,
went
back
to
on
Jeremy,
went
back
to
ziniel
memory
consumption
levels,
but
we
have
to
do
more
testing.
A
A
Add
a
conditional
check
if
C
line
is
available
at
some
Flags
right,
so
that
we
can
make
it.
If,
if
it's
supported
by
the
stem
cell,
we
compile
it
c-line
but
yeah
more
testing
to
be
done
to
know
for
sure,
because
I
mean
maybe
there's
other
side
effects
that
we
don't
foresee.
One
promising
thing
that
I
saw
was-
or
one
thing
that
makes
a
worthwhile
effort-
is
that
I
saw
that
the
default
compiler
that
the
Upstream
Ruby
uses
is
c-line.
So
maybe
it
actually
makes
sense
to
to
move
through
that.
A
Yeah
I
mean
like,
but
if
we
change
the
compiler
for
Ruby
in
the
Bosch
packages,
repo,
that
could
be
a
thing
because
that
would
also
affect
all
the
other,
like
even
Cloud
controller
right.
So
we
need
to
be
really
certain
that
it
is
an
improvement.
C
A
D
But
sap
removes
way
more.
They
had
to
have
like
different
hardening
release
where
they
actually
so
we
remove
Bosch
removed
the
binary
itself.
The.
D
And
their
security
check
checks.
If
the
package
is
installed
by
apt,
so
they
use
the
package
they
check
basically
the
the
package
installer.
If
the
package
is
installed,
yes
or
no,
so
what
they're
doing
is
they
have
hardening
release
where
they're
also
purging
the
whole
package.
A
D
Had
this
discussion
with
so
we'll
go
there,
but
I
I
am
I,
have
been
mad.
I
have
been
sad,
I
have
been
every
every
emotion
there
is,
but
no
dice.
C
Yeah
but
the
ceiling
compiler
is
used
not
at
runtime,
so
it's
not
a
not
a
I
was
called
a
truck
compiler,
no
another
not
used
as
a
kind
of
Jude
compiler
right.
It's.
A
Used:
okay,
no,
no
Ruby
has
that
built
in
so
like
Ruby,
but
Ruby
itself
needs
to
be
compiled
right,
recompile,
Ruby
from
source
and
CLA,
and
that's
like
how
Bosch
releases
work
right.
You
bring
the
source
and
then
you
compile
it
in
the
compilation
stage,
and
for
that
we
use
the
compilers
available
on
the
stem
cell,
and
currently
we
have
GCC
and
clang
as
a
drop
in
replacement
for
GCC,
but
using
the
upset
LL
VM
or
like
the
the
Apple
stuff
right,
the
compilers
that
they
use,
but
yeah.
C
A
That's
the
background
on
that
work
that
might
be
coming,
but
yeah,
that's
gonna,
be
a
bigger
change.
It
at
least
involves
the
the
stem
cell
Builder
and
we
need
to
bump
something
in
the
Ruby
packages
and
then
bump
it
into
the
director
and
get
it
into
watch
deployment.
So
yeah
a
little
take
some
time.
D
D
A
D
D
I
heard
yeah
normally
like
an
Azure
on
Google
Ali
Cloud.
They
all
work,
except
for
now
you
need,
like
you,
need
to
tell
system,
D
and
R6
blah
blah
blah.
C
D
Is
different:
this
is
different.
We.
D
D
We
used,
we
used
just
apt
packages
and
then
we
set
some
system
the
unit
files,
because
we
cannot
use
the
normal
unit
files,
because
the
whole
problem
is
why
this
fails
is
the
bar
lock.
We
are
mounting
the
far
lock
to
the
ephemeral
disk,
which
is
maybe
later
for
AWS,
or
there
is
some
yeah
so.
A
D
A
D
C
D
Yeah
surface
fabric
is
the
one
that
has
a
lot
of
there's
an
own
kind
sets
of
problems.
Okay,.
C
C
D
C
C
C
D
As
you
also
still
needs
to
go
to,
I
have
done
that
bump
like
when
we
went
to
Ruby,
3.0
and
and
Azure
still
needs
to
go
through
their
new
libraries.
Well,
so.
D
A
A
Okay,
I
think
that's
it
is
there
anything
more
people
want
to
discuss.
A
Okay,
thanks
all
for
joining
and
see
y'all
next.