►
From YouTube: Kubernetes SIG CLI 20200624 - bug scrub
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
The
font
is
pretty
small
I'll
blow
it
up.
So
this
is
triage
party.
It's
a
open-source
project
under
Google's,
open
source,
goetaborg
they're
using
it
for
mini
cube
and
cig
release
and
a
bunch
of
other
SIG's
and
groups
and
working
groups
and,
like
I,
said
it's
basically
just
runs
a
bunch
of
github
API
queries
against
a
yeah
mole
filter
file
and
it
lets
you
pull
in
and
categorize.
Things
like
here
are
unpriced
in
seven
days
and
they
have
SLA
x'
with
resolution
paths
forward
that
they
use
we're
like.
A
Okay,
if
you
add
a
priority
or
a
label,
it'll
pull
it
out
of
this
queue
and
so
the
way
that
they
were
working
through
the
their
backlog
and
their
queue
is
they
broke
it
out
into
different
tasks
for
like
weekly
and
daily
and
quarterly,
and
all
this
is
configurable
and
tweakable
moshae
seemed
to
be
pretty
interested
in
it.
So
I've
been
working
on
getting
it
set
up.
A
I'm
gonna
figure
out
how
to
finish
the
filters
I'm
working
with
Thomas
to
get
those
kyudo
and
then
we'll
get
this
deployed
somewhere,
and
hopefully
this
would
allow
us
to
easily
peek
at
things
that
need
to
get
done.
I
don't
know
if
anyone
has
any
kind
of
personal
tools
they're
using
to
to
look
at
open
issues.
Besides
just
what
github
provides,
but
I
thought
this
was
a
good
thing
for
us
to
give
a
shot
at
anyone
have
any
thoughts
or
anything
on
that.
B
Like
one
of
the
things
I
struggled
with
especially
early
on
is
understanding
what
in
the
issue
list,
is
actually
wanted
versus
just
something.
That's
somebody,
an
idea
that
somebody
had
and
posted
there
and
like
I
mean
I
realized
that
we
could,
you
know,
submit
a
full
request
and
then
have
it
decided
then,
but
it
would
be
nice
to
have
some
sort
of
and
I
mean.
Maybe
this
provides
us,
but
some
sort
of
triage.
That
says
this
is,
if
you
do
a
four
bus
for
this,
it
has
a
chance
of
being
accepted.
A
That's
cool
I
think
we
can
use
like
help
a
lot
of
labels.
For
that
too.
The
other
real
nice
thing
is
this
allows
you
to
pull
in
multiple
repos
on
the
same
view,
and
so
we
can
actually
pull
in
all
of
our
cube.
Ctl
tagged
issues
from
the
kubernetes
main
repo
and
get
them
all
displayed
on
the
same
page.
So
I
thought
that
was
pretty
neat
cool.
A
A
C
A
That's
great,
should
we
so
one
of
the
things
that
they
were
heavily
relying
on
when
using
this
was,
if
it's
not
prioritized
it
shows
up
in
here
or
if
it's
not
marked
triage,
we
generally
prioritize
them
some
stuff,
but
we
leave
a
lot
of
things
on
prioritized.
Is
that
something
we
want
to
start
doing
a
bit
more
I,
don't
know
Shawn.
You
have
more
experience
with
that.
C
Gets
Eli
area,
COO
cuddle
and
then
there's
the
difference
between
the
features,
the
kind
feature
and
the
kind
of
bug.
To
be
honest,
the
features
are
what
we
doesn't
appear.
That's
what
we
focus
on
it's
more.
Is
there
something
wrong?
Is
there
a
bug
and
then
there
also
is
a
priority
label
zero
through
four.
C
And
so
do
you
guys
agree
that
maybe
the
bugs
are
what
we
should
focus
on
since
features
and
features
that
seem
important.
We
could
bring
up
to
the
to
the
meeting
to
see
whether
or
not
those
should
be
it
feels
like
those
aren't.
It's
pretty
uncommon
that
those
are
actually
even
accepted,
and
so
well,
what
do
you
guys?
Think
of
the
the
I
mean
calling
the
bug
Scrabble
that
we,
you
know,
focus
on
the
bugs,
as
opposed
to
the
features
so.
A
B
C
C
A
C
B
It
there,
but
no
I
I,
was
just
looking
at
into
the
PR
and
the
PR
I
actually
went
on
another
journey
and
got
some
comments
from
Ben
the
elder
and
I'm
not
sure
where
it's
actually
on
right
now.
But
it's
either
going
to
pass
all
the
arguments
or
get
a
warning,
give
them
a
funny
or
a
message
or
something
but
definitely
somebody's
already
working
on
this
cool.
A
C
C
A
C
A
C
P1
meeting
into
it
pretty
soon
and
t0
meeting
stopped.
Everything
was
not
working
right.
C
A
A
A
B
B
One
of
the
things
that
came
from
another
issue
is
that
since
we've,
since
we've
upgraded
to
Cobra,
1.0
Cobra
has
so
right.
Now
we
have
a
lot
of
custom
code
in
in
you.
Cuddle
that
handles
completions
and
Cobra
has.
Has
that
basically
lets
you
do
dynamic
completions
using
using
go
instead
of
custom
map
scripts,
and
so
the
idea
was
that
we
could
convert
our
dynamic
kernel
or
Tanya
lesions
from
bash
to
go
and
that
that
would
somehow
enable
us
to
then
get
rid
of
all
the
custom
translation
layer.
B
So
the
idea
was
that
that,
because
we
were
at
over
1.0
now
that
we
could
do
that,
and
it
would
kind
of
get
rid
of
a
lot
of
ugly
code
and
enable
more
completions,
but
having
some
discussions
with
a
guy
who
did
it
for
hell
that
the
seashell
completions
provided
by
Cobra
are
not
quite
ready
yet
so
I,
don't
think
it's
it's
kind
of
one
of
those
jigsaw
puzzle
things
where
or
maybe
it's
more
like
a
lack
of
all
or
whatever.
But
you
can't
like
get
everything.
B
A
A
B
B
Probably
a
little
priority,
I,
don't
yeah
I
mean
it
really
does
kind
of
stand
out
of
the
request
for
this
complete,
which
I
thought
at
first
I
thought.
Well,
it's
gonna
be
an
easy
one,
because
Kober
one
supports
fish.
All
we
do
is
plug
it
in
and
use
it,
but
but
it's
not
it's
not
an
easy
one.
So
what
I'm
always
saying?
Maybe
there
should
just
be
closed
or
closed
for
now,
at
least
or
like
reopen
later,
but
I
wasn't
sure
so
I'm
glad
we're
having
a
chance
to
talk
about
this
I.
B
Don't
think
I'm
going
to
work
on
this
at
this
in
the
foreseeable
future
and
I.
Don't
know
that
I
don't
know
it's
probably
not
a
good
first
issue
either
so
I'm
almost
think
I,
don't
know
what
I
don't
want
to
like
break
protocol
about
just
closing
something
create
something
enclosing
it.
But
what
do
you
guys
think
it.
A
C
C
F
C
C
A
C
C
C
A
C
A
A
A
A
C
E
A
A
C
A
B
B
A
B
A
A
A
B
A
A
B
A
C
C
A
Issue
for
this,
one
is
actually
the
chunk
size
if
you
give
a
massive
chunk
size
it
completed
in
five
seconds,
but
if
you
had
the
default
chunk
of
500,
it
took
42
seconds
and
that's
because
it
had
to
make
whatever
you
know.
Whatever
the
division
is
200
200
requests
to
get
that
200
round-trips.
It
just
took
a
long
time.
B
A
C
A
A
A
B
C
A
A
A
A
C
A
C
A
A
A
E
C
A
B
C
C
C
A
A
But
I
do
like
this
I
do
if
we
can
figure
out
our
handbook
for
it,
you
know
how
often
we
want
to
go
through
here
know.
This
is
an
easy
thing
that
we
can
pop
open.
Once
it's
deployed
somewhere
and
see,
you
know
what
needs
attention,
what
hasn't
been
touched
in
like
a
week
or
so
I
do
I.
Do
like
this
tool
a
lot.
Actually,
anyone
have
any
other
thoughts.
A
Will
be,
this
is
running
on
my
local
dev
machine,
which
I
planned
on
using
n
graph
to
like
expose,
but
apparently
Amazon
blocks
and
got
completely
so
I
can't
do
that
so
I'll
get
it
deployed
for
next
time.