►
From YouTube: Meshery Development Meeting (Dec 15th, 2021)
Description
Meshery Development Meeting - December 15th, 2021
Join the community at https://layer5.io/community
Find Layer5 on:
GitHub: https://github.com/layer5io
Twitter: https://twitter.com/layer5
LinkedIn: https://www.linkedin.com/company/layer5
Docker Hub: https://hub.docker.com/u/layer5/
A
All
right
so
welcome
everyone
to
the
measure
redevelopment
meeting
today
is
the
15th
of
december,
and
we
have.
The
topics
for
today
are
mostly
related
to
improving
the
quality
of
measuring.
So
this
is
something
that
we
have
been
discussing
for
a
couple
of
for
a
couple
of
weeks
now
so
mushri
is
at
v0.6,
so
it
is
important
that
we
focus
more
on
the
quality
of
things
and
focus
on
writing
some
writing
some
automated
tests
and
and
that
sort
of
thing
so
yep.
A
So
we
are
focusing
this
meeting,
particularly
on
those
initiatives,
and
we
have
had
a
lot
of
work
being
done
here
in
the
past
couple
of
weeks
and
yep.
So,
let's
get
started
with
today's
topic,
so
mario
is
with
us.
So
mario,
could
you
kick
us
off
with
your
updates.
B
Actually,
just
started
to
interrupt
really
briefly
nikhil
135.
nice
to
have
you
have
you
been
on
this
call
before.
B
Nikhil
nikki,
if
you
don't
just
message
in
the
the
chat,
if
you
would
take
a
moment
to
introduce
yourself
it'd
be
nice
to
let
everybody
get
to
know
you.
C
B
Cool
awesome-
and
I
always
whenever
someone
says
that
hey
I'm
looking
forward
to
contributing
to
one
of
the
projects
here,
I
always
just
want
to
like
throw
up
the
the
muscle
emoji
and
then
I
realized,
like
it's
been
a
while,
since
I've
been
in
the
gym,
so
it
it
doesn't
really
work
out,
but
but
I'm
excited
about
it
anyway.
So
great
hey,
what
was
the
focus
of
your
g
sock,
internship.
B
Gotcha
that
sounds
extraordinarily
generic
yeah
like
yes,
every
back
every
back
end
should
do
that
for
the
front
end.
Moreover,
every
front
end
should
do
it
for
itself
quick
question
for
you,
but
I'm
just
by
the
way
nikhil
there's
a
bunch
of
sarcasm
that
floats
around
in
the
community.
So
if
you
are
the
recipient
of
any
sarcasm,
then
you
know
you
are
being
loved
on
so
quick
question
for
you.
B
Is
there
any
reason
for
the
front
end
for
front
ends
in
general
to
do
their
own
validation
and
not
rely
on
the
back
end,
and
if
the
back
end
is
doing
validation?
Should
the
front
end
even
bother.
C
Okay,
so
the
front
end
validation
is
kind
of
faster
like
because
we
can
validate
in
client
side
as
well.
So
so
it
is
so.
It
saves
kind
of
cost
for
like
transferring
the
data
into
the
api,
then
checking
the
back
end
call
and
we
we
put
the
back
end
validation
like
we.
We
always
want
to
be
in
the
safe
side
of
the
community.
Right,
like
no
data
in
the
data
store
will
get
ever
corrupted.
So
that's.
C
B
B
If
you
would
I'd
be
curious
to
hear
your
thoughts
later
like
in
accordance
with
what
you
just
said
is
like
well,
if,
if
the
purpose
of
doing
another
front
end
is
really
to
like
speed
things
up
kind
of
save
some
cycles
on
the
back
end
and
you
should
be
doing
on
the
back
end
for
data
integrity,
you
mentioned
kind
of
secure
in
there
which,
like
there's
absolutely
a
component
of
that
that
you're
not
touching
on
yet
but
data
integrity.
B
Then
I
wonder
like
in
accordance
with
that
logic,
it
would
be
like
well.
Why
would
you,
if
you're
doing
it
in
the
back
end
anyway,
then?
Why
do
it
in
the
front
end
because
you're
just
doing
double
duty,
so
something
to
think
about,
there's
probably
more
to
it
than
that
so
but
nice
to
get
to
know
you
thanks
for
letting
me
ask
you
a
couple
questions.
That's
great!
It's
a
actually
really
important
focus
for
any
front-end
and
back-end
system
like
that
area
of
work.
D
All
right
well
hi
everyone.
This
is
mario,
yes
on
the
cypress
testing,
so
not
much
progress
on
the
configuration,
a
filtered
integration
test,
but
I'm
picking
that
up.
He
received
some
feedback
from
rodolfo.
He
said
you
know
it
was.
It
was
great
that
the
mocking
the
way
it
was
the
third
was
written
was
was
good.
I
think
I
can
take
further
steps
based
on
that
draftful
request.
D
D
Maybe
passing
the
function
we
like
I'm
sorry
the
like
the
path
to
in
you
know,
since
this
is
using
an
action.
This
is,
you
know
just
for
anyone.
That's
not
familiar.
So
cyprus
is
written
in
javascript.
D
The
tool
allows
us
to
do
integration
tests
so
and
so
we're
mocking
the
backhand
response
and
responses.
So
for
now
I'm
just
covering
the
upload.
It
wasn't
like
a
big
challenge
by
itself
and
now
that
that's
done,
I
would
be
going
over
a
what
would
be
probably
deploying
that
filter
modifying
it
deleting
it
and
so
on,
and
so
so
yeah.
I
did
continue
working
on
that.
I
did
ask
some
questions
about.
D
You
know
how
to
work
on
like
because,
because
abby
was
suggesting
like
like
he
wanted
to
contribute
like
to
this
specific
pr,
but
since
the
the
branch
is
in
in
my
fork,
I
don't
know
I
was
just
like
asking
about
like
how
to
contribute
like
and
now
I
think
navendu
shared
about,
like
the
approach
which
is
to
like
you.
D
Functionality
so
we
should
be
able
to
like
have
separate
vrs
and
then
like
umbrella
issues,
and
then
you
know,
child
issues
were
this
could
be
like.
Specific
scenarios
could
be
worked
on
and
then
again
I
think
I
should
be
updating
like.
I
got
like
an
ask
from
from
navendu
to
update
the
spreadsheet,
and
I
I
think
that's
a
great
idea.
I
did
took
a
look.
I
was
just
wondering
if,
if
we're
doing
integration
tests,
but
then
again,
some
scenarios
might
overlap
between
cyprus,
integration
tests
and
cyprus
end-to-end
tests.
D
My
question
would
be
how
how
should
that
reflect
on
on
the
spreadsheet,
because,
because
you
know
we
could
we
could
have
like
a
lot
of
similarities
between
like
an
integration
test
on
cyprus
and
then
again
an
end-to-end
test.
So
should
there
be
two
rows
to
account
for
each
of
them
and
just
specify
that
or
should
there
be
like
a
new
column?
D
That
would
be
just
to
account
for
that
like
okay,
this
is
a
certain
scenario
and
then
one
row
would
would
be
automated
and
then
just
like
that
will
be
split
into
integration.
Yes,
no
with
cypress
and
then
end
to
end.
Yes,
no
with
cyprus.
I
know
there
is
a
column
for
automated,
but
it's
not
that
binary.
In
this
case
you
know.
B
Yep
right
so
is
the
proposal
just
to
have
a
column
for
for
cyprus
and
then
yes,
no
for
whether
or
not
it's
covered
currently
covered
by
a
cypress
test
and
then
maybe
color
coding
for
whether
or
not
it's
passing
or
failing
currently.
D
Maybe
just
a
new
column
and
then
it
should
it
might
not
be
applicable
for
every
for
every
you
know
kind
of
test,
but
then
again
the
the
value
for
that
would
be
integration
or
integration
or
none,
but
it
would
be
specific
for
cyprus
because
you
know
when
I
start
scripting
it's
a
matter
of
you
know
I
have
to
go
into
the
full
application.
D
Then
I
inspect
you
know
it's.
I
don't
know
it's
a
weird
process
because
you
know
in
order
to
mock
something
up,
some
requests
you
need
to.
You
need
to
understand.
What's
the
actual
request,
and
then
you
know
you,
you
know
so
so
yeah,
I
think
they'll.
These
two
kind
of
tests
for
cyprus
will
overlap
a
lot
so
yeah.
What
do
you
guys
think
should?
Is
it
okay,
like
like
a
new
role
or
maybe
just
I'm
sorry,
not
a
new
row.
D
For
that,
and
so
it
could
be
like
cypress
test
and
then
just
in
that
cell,
just
specify
which
test
or
test
are
written
kind
of
test
or
none
at
all.
A
D
B
F
I
think
you're
going
to
by
the
way
for
the
yeah,
hello.
E
So
super
collaborating
on
the
you
know.
Cypress
testing,
like
one
way
we
can
do,
is
like,
since
you
have
opened
up
yeah
like
draft
pia.
E
So
if
you
allow
someone
else
to,
you
know
open
appear
against
your
work,
so
that
is
one
way
to
you
know
collaborate
within
the
same
yeah
or
we
can
create
a
new
branch
that
will
be
like
set
for
the
site
testing
and
that
will
only
holds
that
will
take
frequents
like
when,
whenever
someone
opens
up
here
and
that's
good,
so
it
can
push
to
that
branch
without
like
much
review
and
then
since
since
that
branch
like
are
regularly
updated,
then
anyone
else
can
collaborate
too.
E
So
after
after
some
functional
things
have
been
done,
then
that
branch
can
be
burned
merged
into
master
the
same.
This
is.
D
You
know
recycling
yeah
in
this
case,
since
this
is
not
function,
you
know
we're
not
we're
not
in
the
risk
of
breaking
like
actual
functionality.
Would
it
make
sense
if
we,
whenever
we
see
there's
something
like
for
cyprus?
Maybe
we
could
just
split
the
issue
into
one
or
more
issues,
and
but
but
of
course
you
know
at
least
for
the
specific
one
we're
talking
about.
D
I
think
I
can
check
offline
with
abby
just
so
that
we
can,
you
know,
discuss
a
bit
because
you
know
I
don't
know
at
least
because
I'm
I'm
so
new
to
the
project
just
a
couple
of
months.
It
just
feels
a
bit
overwhelming,
but
then
again
you
know
starting
like
from
like
with
a
fresh
mind.
D
It's
like
okay,
maybe
maybe
you
want
to
test
too
much,
so
the
idea
would
be
just
to
look
for
the
like
valid
scenarios
and-
and
I
was
taking
a
look
at
the
spreadsheet
and
it's
very
simple-
it's
just
importing
us
a
file
deploying
it
editing
it
deleting
it.
It's
very
simple.
You
know,
even
though
there's
three
different
components
or
pages
we're
talking
about.
D
I
think
we
should
try
not
to
like
over
complicate
it
because
we'll
end
up
having
like
okay,
there
will
be
one
issue
and
then
now
there's
three
and
then
now
serious
corrupt
operations.
So
that's
four
type
of
operations
we'll
have
three
times
four
twelve
different
issues
just
to
complete,
like
you
know
those
tests
and
then,
as
more
people
contribute,
you
know
they'll
be
like.
D
I
think,
that's
fine,
but
if
we
try
to
reduce
the
scope,
you
know
we
can
iterate
upon
adding
the
simplest
as
we
can
that
have
the
most
value
that
require
less
maintenance
to
iterate
upon
that.
So
so
again,
so
I
I
think
I
appreciate
like
abby
wanted
to
jump
in,
so
I
think
let's
try
to
to
so.
I'm
gonna
try
to
to
make
that
pr
like
complete.
D
You
know
at
least
a
scrub
for
for
a
single
page,
and
then
we
can
see
what's
if
we
split
that
into
another
story
or
I'm
sorry,
another
another
issue
or
not,
but
but
I'm
very
confident
that
we
can
reduce
a
lot
of
code
for
the
three
pages.
You
know
because
we're
at
least
on
the
integration
side,
we're
really
focused
on
on
the
front
and
behaving
as
it
should
showing
the
right.
D
I
don't
know
the
right
information
to
the
user
depending
on
the
backend
response,
so
I
think
that
that's,
I
would
say
it's
quite
simple.
The
most
effort
would
be
like
just
going
over
each
scenario
and
getting
together
like
specific
json
responses
to
to
to
mark
and
and
yeah.
I
think
we
could.
We
could
do
that
and
then
maybe
maybe
we
can
split
the
the
I'm
sorry
yeah
yeah
sure.
Maybe
we
can
split
the
the
issue
into
two
one
for
the
integration
test
and
another
one
for
the
end-to-end
test.
D
I
think
that
makes
sense,
because-
and
and
I
think
this
is
a
very
bad
point-
what
I'm
about
to
say
is
that
when
we're,
when
we
start
doing
end-to-end
tests,
we
start
messing
around
with
kind
of
like
state.
So
that's
a
point
where
different
tests
could
do
certain
things.
That
are
item
fault,
item
potent.
So
then
you
know
it
gets
complicated
once
we
start
touching
the
actual
back
end.
D
But
for
that
for
the
a2
test,
I
think
it's
very
manageable
and
once
we
have
those
tests
in
place,
we
can
based
on
like
some
of
at
least
have
that
as
an
inspiration
for
the
end-to-end
test
looking
around
for
any
test
data
that
needs
to
be
injected
or
so
on,
but
yeah
yeah
once
we've
touched
the
server
it's
more
complex.
So
so
would
it
make
sense
if
we
just
split
the
issue
into
two
one
for
integration
test
and
then
one
for
the
e2
test.
D
Yeah
good
good,
good
question,
actually
in
the
issue
itself
in
the
pr
itself,
a
rodolfo,
that's
the
third!
You
go
to
the
third
tab
yep,
so
that
will
share
like
a
really
really
good
blog.
It's
not
the
last
one
that
that
link
is
it's
a
cancer
dots,
blog
blog
article
about
the.
B
D
That
the
difference
for
us
the
difference
that
it's
based
on
like
a
lot
of
what
that
article
says,
is
that
when
we
do
integration
tests
with
cyprus,
we're
mocking
the
backend.
You
know
we're
we're
using
we're
letting
cyprus
tell
the
browser.
You.
B
That
answers
my
question,
mario.
Actually,
I
would
suggest
that
probably
we
don't
really
miss,
I'm
sorry
to
interrupt
but
like,
but
actually
we've
been
on
the
topic
for
a
little
while
and
and
so
yes,
we
should
create
a
new
column
in
the
spreadsheet.
That
would
be
great.
We
should
create
like
it
it's
nice
when
things
are
organized
in
github.
You
know
in
terms
of
like
epics
and
child
issues.
There's
labels
in
there
github
doesn't
really
facilitate
for
linking
them
up
very
well.
B
D
B
A
little
bit
but
like
one
epic
per
like
four
filters,
one
epic
four
applications,
one
epic
for
patterns
that
might
kind
of
work
in
terms
of
like
integration,
testing
and
the
difference
between
integration,
testing
and
ed
testing
like
I
would
suggest
that
to
get
the
biggest
bang
for
our
buck
initially
and
to
move
the
to
move
along
pretty
briskly
is
that
we
would
forgo
the
mocking,
which
actually
probably
just
makes
some
things
brittle
and
there's.
B
If
we
get
to
e
to
e
first
we're
going
to
get
the
biggest
bang
for
our
buck
and
we're
going
to
be
actually
testing
much
of
the
code,
and
so
by
the
time
that
we
made
it
to
the
end
of
e2e
for
all
those
test
cases
in
the
sheet
which,
by
the
way,
are
I'm
not
sure
if
they
cover
a
tenth
of
the
functionality
of
measuring,
I'm
not
sure
like
they'd
like
and
it's
a
long
spreadsheet
already
and
so
yeah.
So
it
makes
me
anxious
that,
like
oh
boy,
we
should
jump
to
ue.
F
D
Actually,
that's
that's
a
good
approach,
at
least
for,
like
just
us
as
we
make
progress
like
you're
right,
yeah,
end-to-end
test
give
more
benefit
because
they
exercise,
you
know
more
code
and
we
don't
have
to
maintain
the
mod
responses.
If
there's
a
change
in
the
front
and
that's
the
server
we'd
have
to
go
and
update
every
marked
response
json,
you
know
it'll
be
like
yeah.
I
agree
with
you
especially
for
this,
for
this
specific
functionality.
D
So
let's
go
with
the
e3
test.
First,
I
like
that
and
sure
about
splitting
by
different.
You
know
by
different
page.
Are
we
sure
about
that?
Because,
basically,
if
we
do
that,
we
might
end
up,
you
know
having
less
well,
I
think
that's
fine
yeah,
because
I
wanted
to
like
reuse
a
lot
of
code
like
it's
simpler.
If
you
do
do
the
three
features
like
the
functionality
together,
you
know,
but
then
again
it
might
not
be
that
easy
to
understand.
D
It
in
three
yeah
for
now
I
think:
that's,
that's
fine,
so
I'll
I'll,
create
those
issues
and
I'll
just
update
the
details
on
the
pr.
If
that's
okay,.
B
Yeah,
it
sounds
good
yeah.
You
know
it's
something.
It's
the
thing
that
you're
battling
with
right
now
with
respect
to
like
how
to
make
things,
as
least
fragile
as
possible,
get
as
much
reuse
as
possible.
B
Also,
while
maintaining
that
it's
like
easy
to
understand,
it's
like
and
your
perspective
might
change
over
time
too,
and
so
yeah
yeah,
it's
not
a
it's
a
predicament,
and
so
by
the
way,
just
in
terms
of
tactical
tactical
consideration
for
you
and
for
everyone
else
on
the
call
that
engages
there's,
it's
not
obvious
for
sure,
with
respect
to
how
to
contribute
to
the
same
branch,
especially
if
that
branch
was
originated
from
another
user's
branch
like
there's
a
difference
between
a
branch,
that's
created
and
kind
of
published
in
and
is
available
for
all
to
come
and
participate
in
versus
a
branch
that's
created
in
a
personal
repo
like
in
mario's
case,
just
which
is
the
same
for
every
pull
request.
B
You
fork
the
project
you
create
your
own
feature
or
bug
branch
or
whatever
you're
working
on
and
then,
as
you
you,
you
open
that
pull
request
you're
requesting
to
merge
from
your
private
branch,
which
you
know
in
concept.
No
one
has
none
of
the
other
contributors
have
access
to
write
to
well
the
way
that
github
works,
and
this
has
got
this-
has
improved
over
the
last
year.
B
The
tooling
around
this
is
that,
for
those
that
are
part
of
the
meshery
project
that
are
maintainers,
part
of
being
a
maintainer
means
a
bunch
of
things,
but
one
of
the
things
that
it
means
is
having
right
access
to
the
repository
and
with
the
way
that
github
works.
If
you're
a
maintainer,
you
have
that
right.
Access
you're
then
able
to
participate
in
someone's,
open
pr,
and
I
had
said,
like
you,
you,
this
was
possible
in
git
for
a
long
long
time.
The
tooling
improved.
B
By
way
of,
I
guess,
if
navendrew,
if
you're,
sharing
or
mario,
if
you're
sharing,
can
you
go
to
the
top
and
just
show
everybody
gh,
real,
quick,
just
the
fact
that
if
you're
not
familiar
with
g,
so
the
upper
right
hand
corner
under
code.
B
Is
it
invented
sharing
so
yeah
there
you
go
and
yeah,
and
so
there's
a
cli
tool
called
gh,
which
is
specific
to
github.
All
it
mostly
does
well
whatever
it
anyway.
It
makes
some
of
this
interaction
a
little
bit
easier,
so
navendu,
if
you
please,
don't
show
this
as
much
as
you
would
go
back
to
the
pr.
B
D
B
You
like
yep,
so
here
the
command
is
prghpr
checkout
and
you
give
it
the
name
of
the
the
identifier
of
the
pr.
Unfortunately,
right
now,
this
only
works
something
works
for
maintainers,
which
is
somewhat
appropriate.
Actually,
if
there's
a
contributor
that
comes
by
and
they're
contributing
and
maintainer
wants
to
jump
in
and
kind
of
help
and
assist,
and
that
that's
at
least
one
way
to
go
about
it.
E
Actually,
it
does
work
for
everyone.
If
someone
is
not
maintainer
that
actually
works,
the
problem
is
with
pushing
so
someone.
If,
if
someone
has
done
the
changes.
B
You
know
pulling.
E
D
Request
requester,
like
the
original
one
to
like
integrate
those
changes
because
I
cuz
abby
did
share
something.
Then
I
saw
the
option
and
then
it
wasn't
like
integrated
in
the
end,
because
there
was
some
clarification
made,
but
but
I
think
my
concern
regarding
that
was
that
I
thought
that
abby
abby
was
not
able
to
get
the
branch
locally
and
run
it
which,
for
cyprus,
that's
really
relevant.
D
B
With
being
able
to
use
gh
cells
yeah,
but
not
all,
and
so
it
might
be
that
as
you
guys
are
going
through
it,
it
might
be
that
you
find
having
a
long-lived
branch
for
cyprus
testing
or
something
might
be
helpful,
although
the
that's
we
want
to
avoid
it,
if
possible,
like
we
want
to
get
things
into.
D
Yeah,
I
think
we
have
to
avoid
it,
because
we
need
to
make
the
scope
as
simple
as
possible
so
that
we
can
like
merge
continuously-
and
you
know,
have
shorter
feedback
cycles
right
totally.
D
Because
then,
you
will
have
to
like
a
new
branch
to
like.
Oh,
there
will
be
like
a
lot
of
merch
conflicts
and
then
all
this
is
not
up
to
date
with
master.
I
don't
know
for
me,
it
takes
a
lot
of
time
because
I'm
not
that
avid
with
github.
Yet
I
use
more
azure
repos
and
azure
devops.
So
it
takes
a
lot
of
effort.
I'd.
D
Very
good,
all
right,
just
sorry,
just
just
about
the
spreadsheet,
would
it
make
sense
to
split
it
into
multiple
sheets
with.
I
don't
know
with
a
certain
thing
that
can
help
us
like
not
have
that
long
list
to
go
over
like
200
300
500
things
just
to
find.
You
know
what
you
want
to
focus
on
and
instead
like
divide
it
up
into
different
sheets
in
that
same
spreadsheet,.
B
Yeah
do
sure
I
it
it
is
hard
to
answer
it's
like
the
same
answer
about
like
where's
the
right.
How
do
you
discern
where
to
reuse
and
where
not
to
it's
like
it
just
kind
of
depends
on
like?
Should
we
should
people
create
filters
based
on
the
the
master
data
set?
Should
we
break
out
it?
We
used
to
have
each
individual
tab
sheet
inside
the
spreadsheet
was
dedicated
to
a
component,
and
it
was
like
oh,
but
then
you
couldn't
really
tell
what
was
going
on
in
a
single
sheet.
B
B
So
next
up
is
speaking
of
testing.
Is
test
coverage
p
used?
You
want
to
talk
about
unit
test
coverage
and
integration
tests
in
mastery
ctl.
A
Okay,
so
we
are
talking
about
code
covering
message
ctl,
we
use
quad
core
to
check
out
how
much
percentage
of
the
code
we
are
actually
covering
right
now.
So
this
is
here
mercedes,
it's
around
33.
A
It
was
33
before,
but
we
are
adding
more
and
more
code
continuously,
so
it's
decreasing
and
that's
what
we
need
to
what
should
I
say,
stop
and
increase
it.
There
are
some
issues
opened
in
this
area.
I
like
one
is
regarding
improvement,
ctl
integration
testing.
A
Let's
say
this
is
the
this
is
one
of
the
pr's
I
opened
very
recently
and
if
you
go
down
in
the
github
workflows,
there
are
two
workflows
that
are
acting
up,
which
is
unit
test
and
the
other
is
integration
test.
This
one
is
failing
and
it's
it
is
not
like.
It
is
not
supposed
to
fail
and
that's
where
these
tests
come
in,
like
these
tests
make
sure
that
messy
sequel
is
robust,
each
function
is
going
to
work
as
supposed
each
messenger
command
is
going
to.
A
Be
as
accurate
as
it
would
okay,
so
there
is
one
for
improving
ctl
right
now.
Integration
tests
occur
like
they
just
trigger
one
sub
command,
like
system
start,
and
then
we
run
another
system
stop
vrn
system
logs.
We
run
systems
restart,
but
what
we
are
not
doing
is
checking
if
mexico
will,
like
measure,
actually
started
after
running
the
start
command.
A
A
So
there
is
one
more
one
more
test,
one
more
issue
that
is
to
increase.
A
I'm
so
sorry,
okay
yeah,
so
there
is
one
more
issue
that
actually
asked
us
to
cover
the
utils
package
in
mexico,
so
how
to
figure
out
what
exact
files
and
functions
we
are
talking
about.
You
can
go
to
this
particular
link
that
will
be
shared
in
the
chat
very
soon.
You
can
go
to
these
folders
and
check.
Only
12
percent
of
the
code
in
config,
config
folder
is
covered,
and
if
you
go
to
the
files,
this
is
going
to
show
what
exact
lines
are
being
covered
or
not.
A
A
You
can
just
ask
to
assign
one
of
these,
these
issues
to
you
and
go
to
code
coverage
website
to
figure
out
what
are
the
lines
where
you
can
write
the
test
for
like.
If
you
want
to
discover
this
function,
you
can
write
one
test
to
cover
this
particular
function
and
that
will
increase
the
code
coverage
by
some
percentage.
B
A
Okay,
okay,
the
minimum
require,
like
the
minimum
thing
that
you
should
know
to
contribute
to
this
test,
is
what
should
I
say:
golang
golang
is
the
thing
you
should.
You
should
know
to
contribute
to
these
tests.
There
is
a
guide
written
exclusively
for
learning.
How
are
we
actually
writing
these
tests?
How
do
we
test
these
now
when
we're
showing
that
right
now
we
write
unit
tests
unit
tests
are
supposed
to
mock
the
maximum
back-end
from
misery
measurey,
and
we
check
what
will
print
like
message
data.
A
What
will
be
the
console
output
of
message
ctl
if
the
backend
of
measuring
that
is
measure
is
working
properly,
so
we
test
those
as
unit
tests
and
there
are
some
behaviors
that
cannot
be
test
or
cannot
be
mocked.
So
we
run
those
sub
commands
as
integration
test
like
necessary
systems
start
we
cannot
mock
something
that
is
measuring.
So
we
run
those
sub
commands
as
integration
test
and
they
try
to
make
sure
that
system
start
is
working
with
each
and
the
release
of
message.
Gtl.
A
B
Yeah
is
there
anybody,
that's
looking
to
jump
in
here
now,
so
there's
a
couple
of
folks
that
come
to
mind
so
vishal
mr
denure,
potentially
mr
wick,
mr
gupta,
as
you
guys
dig
further
into
golang,
or
there
might
be
others
like
this-
is
a
it's
an
impactful
area
to
jump
into
it's
the
writing.
Some
of
these
tests
are
one.
The
code
will
get
used
like
non-stop.
B
The
code
gets
in
that
you
write
will
be
invoked
every
single
time
that
someone
does
a
pull
request
every
single
time
that
someone
adds
a
commit
to
a
pull
request
every
single
time
we
do
a
release
like
it
becomes
really
important.
It
gets
highly
used.
So
it's
pretty
important.
It's
actually
a
large
part
of
the
point
of
today's
meeting
itself.
Navendu.
Let
us
open
it
up
with
we're
trying
to
make
a
release.
B
We
need
to
get
quality
into
a
good
position,
and
so
mario
is
here
talking
about
all
the
ways
in
which
he
and
others
are
trying
to
push
forth
on
integration
and
end-to-end.
Testing
push
is
talking
about
unit
testing,
maybe
even
some
static
testing
in
there
there's
a
golden
template,
a
thing
that
he
refers
to
as
the
golden
template.
What
is
that?
How
does
that
work?
There's
a
lot
of
intriguing
things.
It's
a
good
way
to
make
your
mark
on
the
project.
A
A
Okay,
so
some
of
you
might
find
a
writing
test
really
a
big
task
like
in
every
issue.
I
am
asking
you
to
cover
a
whole
file,
so
that's
not
what
I
like.
I
don't
want
to
intimidate
you
with
writing
these
mistakes.
These
much
tests
you
can
like
raise
a
pr
just
with
one
test
for
one
function
in
messaging,
and
that
will
that
that
is
going
to
boost
the
code
coverage
with
really
high
amount
of
percentage
over
the
period
of
time.
A
So
don't
get
intimidated
by
that
fact
that
you
have
to
cover
one
file.
Just
one
function
would
be
enough
to
raise
appear.
A
Awesome
thank
you
for
mentioning
that,
and
so
I
think
a
couple
of
folks
have
already
signed
up,
so
they
can
reach
to
you
in
slack
and
open
up
issues
and
make
prs
moving
on
to
a
different
item
for
the
v0.6
release.
I'm
saying
like
would
you
like
to
give
a
quick
overview
of
the
recent
changes
you
made.
A
E
I
just
wanted
to
share
this
one
screen,
but
it
won't
be
so
yeah,
so
my
firefox
screen
is
visible,
I
hope
going
through
it.
So
this
is
the
previous
screen
that
we
had,
like
all
things
clustered
up
and
out
so
yeah.
We
are
back
to
the
our
original
style
that
we
just
made
after
a
lot
of
efforts
and
that's
what
we
have
right
now.
E
That's
integrated
like
like
I
have
talked
about
like
two
three
different
things,
one
of
which
is
utkarsh
pr
and
two
other
more
like
my
own
to
other
peers.
But
unfortunately
it's
not
like
this,
though
all
these
changes
are
on
different,
different
branches.
That's
why
I
could
not
show
it
at
the
same
time,
maybe
on
the
next
call.
I
will
you
know,
unite
everything
and
show
it
to
you
once
now
when
moving
to
it.
E
So
we
have
changed
the
archer
arches
of
form,
styles,
that
you
can
see
here
and
another
thing
is
like
enlarging
the
tooltip
and
changing
the
color
for
the
better
visibility.
So
I
just
I
want
to
get
the
feedback
of
lee
over
here.
If
it
is
fine.
B
You
know
it's
not
worth
talking
about
until
we
get
a
design
yeah
because,
like
it
looks
fine
except
no
right
there,
except
no,
it
doesn't
look
fine,
because
that
same
style
is
not
used
anywhere
else
and
quality.
It's
all
about
consistency.
E
Okay,
sure,
okay,
now
so
so
so
so
that
is,
the
you
know,
are
just
form
styling,
so
it
needs
further.
Some
more
changes
like
you
can
see
here,
so
I
am
on
to
it
right
now
other
than
that
other
than
that
we
can
just
change
the
name
from
the
toolbar
here
like
this
is
untitled
design.
We
can
click
on
it
and
change
the
name
of
the
pattern
file
as
well
as
do
the
reverse
operation
here.
E
So
so,
as
you
can
see,
the
changes
in
the
address
of
form
styles,
I
just
want
to
quickly
discuss
the
utkash
vr
also,
that
is
so.
He
had
added
the
edit
the
feature
to
add
new
pattern
files
from
the
console
like
from
the
ui
itself,
and
we
had
fixed
a
lot
of
things
to
like
the
problems
with
the
id
generator
problems.
With
the
you
know,
the
ui
crashes,
when
there
are
empty
ml
files,
so
which
is
not
crashing
right
now.
E
So
all
these
are
all
the
things
like
all
the
updates.
We
have
right
now
on
the
patented.
B
Questions,
some
of
you
are
jumping
into
a
refactoring,
that's
going
on.
Actually,
I
guess
we'll
talk
about
refactoring
in
a
bit,
but
yeah
avi.
This
is
great,
so
abi
and
mario,
both
in
the
critical
path
to
the
upcoming
release.
Both
of
these
gentlemen,
are
feeling
very
easy
in
their
seats.
Right
now,.
B
Cool
this
is
great.
It's
super
exciting.
This
will
eventually
replace
the
life
cycle,
the
life
cycle
uis.
This
will
put
them
to
shame:
okay,
who's,
who's.
Next.
A
Next
up,
we
have
a
weekly
update
on
the
ui
refactoring
initiative,
so
sayanten
is
on
the
call
scientist
like.
Could
you
give
us
an
update
on
the
progress.
H
So
yeah,
so
I
think
this
was
the
pr
updating
the
node
notice
stack
version,
so
prakar
actually
created
this
pr
six
days
ago
and
it
is
already
been
merged.
The
other
one
was
the
adding
of
the
big
number
component.
Make
up,
magna
actually
completed
this
pr,
and
this
is
also
being
matched
so,
and
this
is
the
tracker
so
right
now
these
are
the
pr's
we
like
these
are
the
columns
which
are
already
being
completed,
but
there
are
lots
of
back
and
base
places.
H
So
I
think
richard
is
working
on
a
globally
reusable
calendar
component
and
we
also
need
one
custom.
Loading
spinner,
like
a
loading
spinner,
which
will
actually
have
the
logo
in
between,
like
the
may
sync
logo,
or
something
that
will
spin
up
when
there
is
a
particular
component,
is
being
spinning
up
so
yeah
that
that
is
the
custom
loading
spinner
we
want.
H
Actually,
there
is
one
custom
loading
spinner
which
I
have
already
written,
but
that
was
the
copy
of
the
machine
measure
is
right
now,
so
we
need
a
different
one
and
we
need
a
reusable,
auto,
complete
component
using
this
downshift.
I
think
nitish
was
working
on
this,
but
he
has
changed
his
name,
so
this
is
blank.
Now
anyone
can
take
up
this
one
for
the
data
table.
H
There
is
also
one
reusable
component
I
have
written,
but
that
is
not
so
robust
like
we
need
one
so
that
we
can
do
all
type
of
changes
like
we
most
probably
will
we
will
be
using
the
mui
data
tables,
and
this
is
also
right
now.
Blank
and
mega
has,
I
think,
completed
both
of
this
and
yeah.
So
I
think
that's
that's
a
bit
of
an
update.
E
Yeah
so
so
such
as
you
just
talked
about
like
creating
components,
so
have
you
also
like
shown
progress
in
our
creating
or
replicating
pages
just
questions.
H
Actually-
and
it
is
told
I
mean
this
is
told
me-
that
we
just
right
now-
need
this
globally
usable
components,
because
in
measures
ui,
I
think
the
ui
would
also
go
under
some
new
designs,
so
it
is
to
look
more
into
the
completed
global
components.
This
will
not
go
into
any
design.
This
will
be
a
globally
visible
component,
so.
B
Rika
sharma
has
a
proposal
a
proposed
calendar
library
to
use
that's
an
kind
of
discussion,
that's
happening
for
those
that
this
area
interests,
I
think
that's
discussion
is
happening
in
slack
at
the
moment.
We
might
want
to
bubble
that
up
into
this
this
sheet
and
sort
of
so
so
for
those
that
are
focused
here.
B
Speaking
of
those
that
are
focused
here,
so
some
of
the
work
of
prakar
prakar
prakar,
there
that's
correct,
prakar,
sorry,
just
practicing
your
name,
it
was
just
shown
and
megana
and
deepayon
do
you
any
of
you
have
other
items
to
any
any
other
updates
you
might
want
to
share.
Just
you
know,
thoughts
on
upcoming
answer,
the.
I
Thing
is,
I
just
said
it
set
the
machine
project
up
on
my
system.
As
I
told
you
before,
that
I
was
having
some
issues
on
the
discussion
thread.
I
discussed
that
and
I
am
looking
into
the
code
base
a
bit
and
I
will
take
something
up
with
the
within
the
next
two
days
or,
if,
like
the
folks
working
on
it,
might
suggest
something
to
begin
with.
I
can
take
that
up
also
so
yeah.
That's
all
I
have
to
say
I
haven't
started
like
contributing
to
it,
but
yeah.
B
How
how
dare
you,
how
like
it
is,
I
I
just
that
sounds
terrible
or
actually
I
probably
don't,
have
a
good
sarcastic
joke
on
this
other
than
to
say,
like
yeah.
That
sounds
wonderful,
like
some
of
us
have
a
lot
of
stuff
going
on
in
like
the
rest
of
our
lives,
and
some
of
us
don't
have
a
life.
So
we
spend
a
lot
of
time
here
and
so
yeah.
Any
amount
of
engagement
is
like
warmly
welcomed
for
some
of
you,
you'll
find
yourself
you'll
find
in
hopefully
a
nice.
B
What's
the
right
term
virtuous
cycle
of
like
contributing
keep
learning
something
being
recognized
for
it.
Seeing
people
use
it
getting
feedback,
contributing,
learning
something
more
and
then
and
it
gets
into
a
nice
cycle,
and
then
you
end
up
with
a
resume
a
mile,
long
and
recruiters
that
won't
stop
pounding
you
and
whatever,
whatever
your
goals
are
like
whatever
you're
doing
like
yeah
anyway,
suffice
to
say,
yeah
dp
on
that
sounds
great.
B
I'm
pleased
to
hear
that
you're
able
to
that
your
environment
is
set
up
like
there's
a
lot
of
folks
who
come
by,
who
don't
make
it
past
that
bit
like
it's,
not
always
easy,
dp
on
by
the
way.
What
os
are
you
using.
B
Gotcha,
okay,
very
good
kind
of
nice
to
keep
a
mental
inventory.
It
helps
a
little
bit
with
respect
to
as
we
get
into
testing.
Sometimes
you
know
compatibility
and
and
but
then
also
just
the
browser
that
you
you
know
in
your
case.
Like
you
know,
browser
is
also
part
of
that
consideration.
What
what's
your
go-to
browser
chrome
got?
You
anybody,
yeah,
okay,
out
of
curiosity,
anybody
using
edge
anybody,
that's
on
windows
using
edge
occasionally
or
most
of
the
time.
B
Okay,
cool:
well,
that's
that
okay,
that's
not
bothered
with
edge
then,
and
I
say
that
you
know
mostly
jokingly,
but
there's
certainly
public-facing
many
public-facing
statistics
about
which
browsers
on
what
types
of
devices
and
etc
are
the
most
popular
there's
a
certain.
You
know
universe.
B
You
know
across
across
the
world
in
general,
there's
also
a
market
segment
of
users
that
are
going
to
be
interested
in
measuring
they're
going
to
be,
they
may
or
may
not
be
representative
of
those
same
numbers,
and
so
we
just
for
what
it's
worth
for
those
that
are
like
focused
here.
It
is
the
compa
we
are
desirous
of
spending
time
and
helping
guarantee
compatibility
between
chrome,
safari
firefox
if
brave
and
opera
and
like
an
edge
and
all
the
that
would
be
wonderful.
B
If
there's
you
know
full
compatibility,
mario,
who
has
nothing,
you
know
who
doesn't
have
anything
else
on
his
plate.
Might
at
some
point
and
those
that
are
jumping
into
cyprus
might
talk
to
us
at
some
point
about
cyprus's
ability
to
mimic
different.
You
know
help
with
some
browser
compatibility
testing.
So
that's
a
that's
a
topic
good
it
also
just
as
we
go
to.
B
I
think
we're
like
this
is,
I
think,
one
of
our
last
topics
I
think,
and
we've
got
and
and
we
wanna
we're
about
ready
to
get
the
dot
six
release
out
the
darn
door
landing.
This
plane
is
kind
of
hard.
It's
always
that
last,
like
five
percent.
B
It's
a
reason
why
the
issues
that
are
like
postponed
and
postponed
get
postponed
because
they're
hard
and
so
the
last
five
percent's
always
like
hard
to
close,
but
we're
pretty
darn
close.
So
as
we
lean
into
like
what's
next
and
as
a
number
of
you
dig
into
this
refactoring
mesh
ui,
it
is
incumbent
upon
all
of
us
to.
B
Whatever
other
adjectives
you
can
throw
at
it
that
we
wanted
to
be
consistent
of
high
quality,
feel
good,
be
a
little
serious,
not
very
comical,
we're
not
into
3d
things
here,
just
yet
we're
still
sort
of
following
the
flat
style
we're
using
material
ui
we're
using
like
a
roboto
font
right
now,
like
a
lot
of
you
know
all
of
this
kind
of
comes
into
question
as
something
to
potentially
change
or
not,
and
these
will
be
ongoing
reflections
for
us.
We
do
want
to
get
off
on
the
right
foot
with
custom
themes
in
material
ui.
B
Five.
We
have
long
suffered
with
like
without
being
able
to
use
a
theme
properly,
and
so,
as
we
go
to
react,
17
material,
ui5,
graphql
through
and
through
subscriptions
real-time
data,
some
web
sockets.
As
we
go
to
reuse
those
same
connections,
we
go
to
manage
our
graphql
subscriptions
like
there's
a
lot
that
comes
in
here.
We
we
will
eventually
get
to
a
place
where
speaking
of
like
when,
when
when
nikhil
aggarwal-
and
I
were
talking
about
front-end
validation
and
back-end
validation-
certainly
that's
part
and
parcel
to
this.
B
To
how
the
front
end
ui
will
work
and
should
work,
there's
a
particular
technology
that
our
library
is
the
right
yeah,
a
library
called
react,
react
json,
schema
form.
B
B
And
that
makes
measurey
super
powerful.
There
are
some
other
popular
open
source
projects
that
meshri
will
ultimately
well
like.
I
don't
compete
with
and
that's
not
because
mesri
as
a
project
is
trying
to
compete
with
them.
It's
just
there'll
be
some
similar
functionality,
so
one
of
those
projects
is
crossplane.
B
Crossplane.Io
mastery
will
have
some
similar
capabilities,
we're
using
some
of
the
same
tech.
Another
project
is
kiali
kiali.io
for
those
of
you
who
have
been
contributing
to
mesh
map.
You
are.
You
are
already
familiar
with
that
right,
but,
okay
as
we
go
to
wrap
up,
I
just
wanted
to
get
just
a
quick
mental
list
of
those
that
are
interested
in
this
effort
and
the
refactoring
of
the
ui
effort.
So
far.
B
These
are
the
names
that
I'm
that,
for
my
part,
I'm
tracking
and
we
might
want
to
write
down
on
paper
and
we
might
want
to
publish
somewhere
publicly
as
well
so
megana
is
with
us.
Prakar
is
with
us
or
is
focus
here.
B
B
B
There's
time
think
about
it,
just
you
know
be
vocal
in
slack
or
on
discus
to
discuss
form
and
we're
gonna
try
to
get.
You
know
fairly
organized,
as
this
goes
forth
the
painful
bit.
This
is
the
last
thing
I'll
say
and
then
I'll
I'll
stop
haranguing
everyone,
and
that's
that
the
painful
part
about
this
refactoring
of
the
ui
is
that,
unlike
what
mario
was
talking
about
earlier,
where
he
can,
he
and
others
can
deliver.
B
Cypress
tests
like
in
an
incomplete
way.
He
can
deliver
a
point
test
here
and
one
over
there
and
one
over
there
and
and
that's
all
good
measure.
We
can
still
build
and
release
measuring
for
this
ui
refactoring.
It's
not
it's
like
you're,
either
running
the
current
ui
or
you're
running
the
new
ui,
and
so
it's
it's
an
uncomfortable
full
swap,
that's
gonna
be
painful
for
us,
so
we
have
two
release
channels
today,.
B
Maybe
we
need
a
third
or
maybe
we
need
to
change
the
way
that
those
work
a
little
bit
so
that
we
can
start
to
get
that
new
ui
into
people's
hands,
or
maybe
we
just
need
a
flag
in
the
ui,
the
current
ui
that
says,
there's
a
new
one
coming.
Do
you
want
to
try
the
new
one
and
then
so?
We
just
have
a
cookie
or
something
else
that
loads
up
the
alternative
ui,
something
for
you
all
to
think
about.
A
A
And
before
we
before
we
went
up,
I
just
wanted
to
make
a
note
that
the
cubecon
ucfp
closes
this
week.
So
we
are,
we
are.
We
are
writing
some
proposals
for
talks.
So
add
your
proposals
in
as
well
like
if
you
are
interested
in
giving
a
talk
at
cubecon,
all
right,
everyone
nice
to
meet
all
the
newcomers
and
thank
you
for
joining
see
you
bye,
bye,
bye,
bye,
bye,
everyone.