►
From YouTube: Community Meeting, December 13, 2022
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
everybody
today
is
December
13th,
and
this
is
the
last
kcp
community
meeting
of
2022..
So
welcome
and
thank
you
Stefan
for
creating
our
agenda
issue.
He
just
created
it
so
there's
nothing
in
here.
At
the
moment,
I
will
start
off
by
saying
that
we
have
one
pull
request
left,
that's
in
the
merge
queue
and
once
that
merges
I
will
begin
the
process
of
releasing
0.10
and
after
0.10
is
released.
We
will
start
to
well.
A
We
will
be
ready
to
merge
the
large
refactoring
that
Stefan
and
lukash
have
been
working
on
for
refactoring
workspaces
and
how
how
about
all
functions.
So
this
is
pretty
exciting,
I'm
glad
that
we're
getting
the
release
out
this
week
and
that
we
can
move
forward
with
the
workspace,
refactoring
and
other
things
as
well.
A
So
does
anyone
have
any
topics
for
today.
A
All
right
well,
while
you're
thinking
I,
will
bring
up
one
thing
which
is
around
flakes,
so
we
have
some
issues
that
are
impacting
CI
and
mainly
we're
seeing
this
test
integration.
Multiple
connections
happen
where
something
goes
wrong
and
we
get
an
eof
I'm
tempted
to
open
up
a
PR
to
disable
this
test
until
somebody
has
some
time
to
look
into
it.
A
Normally,
we
would
not
disable
flaking
tests,
but
this
one
is
for
functionality
that
is
behind
a
feature
gate
and
is
not
properly
authorized
yet
in
terms
of
doing
like
pod
logs
and
is
exact
and
whatnot,
so
I
feel
comfortable,
taking
this
one
and
skipping
it
and
giving
time
for
folks
to
look
into
it.
A
It's
that
that's
one,
but
if
folks
are
available
and
have
some
time
they're.
These
are
the
flakes
that
are
out
there,
there's
also
another
one
that
I
think
must
not
have
labeled.
This
is
flake.
A
And
Steve
did
how
to
have
a
suggestion
for
how
to
amend
our
ede
framework
to
try
and
gather
some
more
information.
So
if
somebody
is
looking
for
some
really
useful
work
to
do,
you
could
take
this
one
on
go
ahead.
Sergius.
B
A
C
So
we
are
sorry
if
you,
if
you
come
back
to
to
the
list,
there
are
two
related
to
thinker
or
virtual
thinker,
which
I
assume
were
fixed
when
I
made
some
big
cleaning
in
the
in
in
the
end-to-end
test,
and
also
the
virtual
thinker,
I
mean
the
single
picture.
I
was
not
sure.
I
mean
I'm
I.
Just
wanted
to
give
some
time
to.
You
know
confirm
that
everything
was
effectively
fixed
because
it
was
a
mix
of
a
number
of
of
root
cause.
C
B
A
Yeah
I
would
say
like
if
you
refactor
the
code
to
where
you
know
whatever
was
flaking
before
can't
flake
anymore
because
of
structural
changes,
it's
totally
fine
to
to
link
to
the
pr
and
close
it
out.
If
you
think
that
you've
fixed
it,
it's
totally
fine
to
leave
it
open
for
a
week
or
two
and
then
close.
It
just
remember
to
come.
C
D
Yeah
I
just
wanted
to
raise
a
concern
about
the
documentation.
If
there's
a
major
fact,
refactoring
being
merged,
I
was
wondering
if
the
documentation
has
a
way
of
talking
about
both.
You
know
the
old
and
the
new
I
see
it
does
have
a
concept
of
releases
and
currently
there's
only
one
main.
A
I
will
fill
this
in
I
won't
make
you
oh
watch
me,
do
it,
but
I
will
file
it
all
right.
Thank.
D
A
Okay,
any.
B
A
A
All
right,
I'm
I'm
gonna
go
with
no,
so
we
do
have
just
a
few
that
are
not
triaged
yet
and
first
one
is
that
hyperlinks
in
the
main
docs
site
are
broken.
A
Let's
see
yep
I
would
say,
they're
definitely
broken.
I
I
have
a
feeling.
I
know
what
the
issue
is
here,
but
we
should
fix.
This.
I
will
take
this
one.
A
File
system
in
here
ends
up
being
read
only
and
it
has
some
trouble
installing
I,
don't
know
Docker
or
something
so
I
did
assign
this
to
the
contributor
who
initially
added
this,
but
for
right
now,
I've
disabled
this
workflow,
so
that
on
new
pull
requests,
you
won't
see
this
failing
anymore.
It
was
not
a
release
blocker
before
and
I.
Think
it's
not
great
to
see
something.
That's
in
permafail
on
all
your
PRS.
So
if
folks
want
to
look
at
that,
that'd
be
awesome
and
I
don't
know
Andy
or
Mike.
A
If
you
have
any
communication
with
the
folks
that
did
the
ppc64
CI
there,
but
if
you
could
let
them
know
if
you
do
that
it's
having
some
issues,
that'd
be
awesome.
A
Thanks:
okay!
Well,
that's
it
for
issues
to
triage,
so
last
call
for
topics,
if
not
very
short
meeting,
and
we
will
see
everybody
in
the
New
Year.
Hopefully,.
A
All
right,
happy
holidays,
everybody
see
you
around.