►
From YouTube: Meshery Development Meeting (Jan 26th, 2022)
Description
Meshery Development Meeting - January 26th, 2022
Agenda:
- Added flag to control browser behaviour. #4959
- Fix capture and handle expired token in performance page. #495
- Check for expired tokens/expired token error message #4989
- Demo of spinners
- Integration of MeshOpsv2 into Meshery UI v0.7 ← hot-pick
Opportunities: Refactoring Meshery UI in v0.7.0 (design proposal)
Branch | Meshery v0.7.0 Implementation Tracker | Contributor’s Guide
- Compatibility Matrix Demo
- Demo for navigation “pull tab” #4926
Join the community at https://layer5.io/community
Find Meshery on:
GitHub: https://github.com/meshery
Twitter: https://twitter.com/mesheryio
LinkedIn: https://www.linkedin.com/showcase/meshery/
Docker Hub: https://hub.docker.com/u/layer5/
A
A
Yes
awesome?
Would
you
like
to
talk
to
your
topic?
Okay,
the
first
one
that
is
the
added
flag
to
control
browser
behavior.
It
is
like
now
what
the
current
implementation
was,
that
whether
user
wants
or
not
the
browser
gets
open
when
we
run
my
system
start.
So
this
is
a
skip
flat,
minus
s
which
controls
whether
to
open
the
browser
or
not.
C
Did
by
the
way
so
there's
a
ux
kind
of
design
guide
for
measuring
cli
that
might
help
a
little
bit
with
this,
but
so
yeah
outside
of
the
dash
s.
Is
there
any
other
form
of
that
flag
skip
by
the
way?
Isn't
necessarily
well
understood
that
you
would
be
skipping
opening
the
browser
skip?
There
is
a
skip
update,
which
means
don't
update
the
system.
Just
start
just
do
the
deployment,
so
there
would
probably.
A
A
Here
in
the
auth
middleware,
we
were
checking
for
the
session
and
if
the
session
was
not
valid,
we
were
handling
the
login
handler
was
called
everywhere
handling
the
login,
but
this
was
giving
the
course
wildcard
origin
error,
so
what
it
so,
as
in
the
issue
track,
it
was
mentioned
that
we
we
should
handle
this
gracefully
by
displaying
the
messages
to
the
user,
that
your
session
has
expired
and
you
will
be
logged
into
the
provider
ui.
So
what
I
did
this
I
check
for
the
error.
What
was
given
by
the
get
session
function.
A
Right
here,
when
the
session
is
expired,
when
these
are
two
kind
of
when
the
user
first
comes
it,
he
will
not
have
the
cookie.
So
if,
if
this
is
the
case,
then
redirect
redirect
to
the
provider
ui
and
if
the
case
is
the
cookie
is
present,
but
the
session
has
expired,
so
I'm
sending
the
error
to
the
graphql
request,
saying
that
token
has
expired
and
I'm
handling
that
error
in
the
ui.
A
Right
here,
I'm
checking
for
the
error
is
present
and
then
pushing
to
the
provider
ui
and
I've
only
added
for
the
performance
page
right
now,
because
it
would
for
to
cover
all
the
end
points
it
would
require
to
decentralize
centralize
the
error
handling
and
the
I
tried
to
do
that.
But
in
the
machine
ui
restructuring
branch
it
is
already
kind
of
considered.
So
it
would
not
make
sense
to
again
do
in
this.
C
C
C
A
This
is
the
same
change,
but
I
tried
to
hand
handle
the
error
as
a
centralized
approach
that
you
can
see
in
the
another
pr
I
raised,
but
in
the
discussion
you
abhishek
mentioned
that,
instead
of
handling
centralizing
the
error
handling,
we
should
centralize
the
api
calls,
so
I
will
look
into
it.
I
will
talk
to
with
abhishek
on
how
to
approach
this.
What
will
the
better
approach?
C
E
C
Yeah
so
yeah
muhammad,
we
ideally
yeah.
Ideally,
the
approach
is,
is
a
bit
more
in
middleware
like
that,
there's
a
a
single
universal
way
to
handle
any
it's
both
like
on
when
a
back-end
call
is
received
with
a
token.
That's
expired
that
the
user
would
be
redirected
to
the
login
page,
which
I
is
that
that
3000
online
150
is
that
a
port
number
or
is
that
a
is
that
three
seconds.
C
Okay,
so
that's
good,
but
then
yeah
on
the
front
end
it's
ideal.
If
someone
walks
away
for
you
know
12
hours,
they
come
back,
they
sit
down
that
that
a
modal
would
be
present,
that
that,
on
the
client
side,
that
the
ui
would
understand,
even
without
a
back
end,
call
that
their
token
has
expired
and
that
they
would
have
been
redirected
to
log
in
that,
essentially
it
their
token
expires.
So
they're,
basically
logged
out
except
the
ui,
wouldn't
have
done
anything
and
it
would.
C
It
would
look
as
if
the
user
can
do
things
in
the
ui
they
might
try
to
click
around
and
they'll
have
errors
because
unbeknownst
to
them
their
token
is
expired.
So
instead
yeah,
if
in
javascript,
if
we're
auto
redirecting
to
the
login
page,
because
their
token
expired
and
is
no
longer
valid
and
they're
essentially
logged
out.
C
So
they
should
be
taken
to
the
log
out
page,
which
is
the
login
page
yeah,
that's
ideal
behavior
as
well,
but
as
you
implement
it,
that
we
wouldn't
like
part
of
what
concerns
me
is
that,
as
you
described
like
that,
the
fact
that
this
approach
is
handling
all
the
calls
on
the
performance
page,
it's
like
well
yeah
that
that's
good,
but
but
actually
the
approach
we
want
to
have
be
universal
and
centralized.
So
it
sounds
like
that's
part
of
the
feedback
that
you're
working
on
now.
A
Yes,
I
can
I'm
looking
I
discussed
with
abhishek,
and
I
mentioned
that
this
is
considered
in
you.
They
will
implement
with
axios
so
means
they
will
all
centralize
all
the
api
calls
at
one
place
and
they're.
Only
all
the
failures,
like
fetch,
call
fetch
failures,
error
from
the
server
or
authentication
error
will
be
handled
at
one
place,
so
this
function
here.
E
Can
I
make
a
suggestion
so
about
what
lee
suggested
so
in
order
for
the
front
and
to
be
able
to
know
that
the
token
is
expired
without
sending
any
requests?
Well,
we
could
use
a
timer
and
then
we'll
we
would
only
have
to
know
what
is
the
expiry
of
that
token.
So
it
could
be
retrieved
from
the
token
itself
what's
the
expiry
and
then
that
timer
could
could
be
started
to
a
minor
time.
E
Well,
yeah
and
the
time
yeah
well,
basically
the
timer
it
wouldn't
it
wouldn't
check
for
expiry
like
every
time
the
timer
runs.
Only
it
would
only
trigger
once
like
fire
is
close
to
to
be
happening
and
yeah
yeah.
Basically,
that's
it.
That's
the
approach
we're
using
in
in
a
project.
I
work
on
my
work.
So
that's
okay,
that
worked
very
good.
C
Yeah
right
that
both
both
back
end
and
front
end
should
be
the
back
end
should
be
the
front
end
handling.
It
is
for
user
experience
and
just
improving
that
to
so
that
people
aren't
sitting
there
wondering
what's
going
on
and
then
they
kind
of
click
around
they're
like
oh.
I
guess
I
guess
my
token
is
bad-
that
yeah
the
if
the
expiry
time
is
tracked
in
a
cookie
that
that
can
be
checked
with
some
some
regularity.
C
There
are
no
doubt
any
number
of
patterns
that
different
apps
use,
like
mario,
was
saying
about
a
timer
yeah.
The
use
of
a
cookie
and
probably
makes
some
sense
here
on
the
back
end.
Certainly
in
golang,
like
any
all
of
the
most
of
the
apis
are
protected
anyway,
and
they
won't
let
anyone
invoke
an
api
unless
there
is
a
valid
token,
that's
unexpired,
so
much
of
that
is
handled
already.
E
My
work
we
used
to
use
a
cookie,
but
we
we
saw
that
in
safari.
There
were
some
problems
because
of
like
the
restrictions,
like
certain
browsers,
restrict
like
cross-origin,
cookies
and
so
on,
and
then
so
it
happened
in
safari
and
we
we
researched
and
chrome
would
enable
that
kind
of
restriction
that
certain
cookies
wouldn't
be.
The
browser
wouldn't
allow
them
to
run
from
like
to
read
it
from
different
origin
than
on
the
front
end.
E
Even
though
we
have
a
cookie,
we
would
still
have
to
read
it
like
just
check
it
constantly
right
or
in
a
certain
interval,
so
we
would
still
have
either
a
set
timeout
or
for
a
timer,
like
the
mechanism
to
to
check
for
the
expire
on
the
front.
End
would
have
to
be
defined
clearly
like
what
do
we
want,
like
the
clearer,
the
better
so
that
you
know
we
can
have
at
least
requirements
of
how
it
should
behave,
and
then
maybe
the
mechanism
could
be
like
derived
based
on
exactly
what
we
want.
C
Yeah,
I
don't
know
if
that
was
clear
at
all,
but
the
muhammad,
the
implementation
inside
of
axios
centralized
for
the
front
end
sounds
great.
The
central
redirect
that
understands
when
the
user's
token
is
expired
and
yeah,
either
cookie
or
local
storage,
or
something
similar
and
yeah
watching
out
for
the
things
that
mario
just
mentioned.
C
B
A
F
F
C
They
are
two
different
clients,
so
there's
kind
of
three
areas
to
handle
expired
user
tokens.
One
is
in
mesh
reservoir
where,
which
is
you
know,
for
the
most
part,
receiving
api
requests?
Most
of
those
api
requests
that
come
from
mastery
cli
are
rest
based.
Api
requests
messages,
rest
based,
api
requests
to
mesh
reserver
measure,
server
uses
to
it
does
today,
but,
but
it
would
be,
it
does
today
check
for
valid
token,
and
if
it's
expired,
that's
one
way
that
it's
invalid
and
that
request
is
rejected
the
and
so
yeah
so
in
measure
ui.
C
We're
do
so
we're
protected
today.
The
system
and
the
app
is
intact
and
kind
of
protected.
Today,
the
what
we're
working
here
we're
working
on
here
is
ux
from
two
different
clients
of
measuring
services,
and
so
the
ux
here
is
all
you
know:
command
line
stuff.
So
the
response
that
and
so
for
most
commands
that
people
run
with
mastery
ctl
and
most
of
measuring
ct
yellow's
commands
require
a
valid
token.
Why?
Well,
because
most
of
measure
servers
apis
require
a
valid
token.
C
There's
like
one
or
two
apis
that
don't
it's
the
one
one
of
them
is
about
checking
the
version
of
mesh
ctl.
It's
a
naked
api
in
part
because
it
just
helps
with
understanding
his
mastery
up.
And
what
version
is
that?
And
can
I
tell
what
that
what
the
health
of
it
is
before
I
really
get
in
and
sign
in
and
that
type
of
information
yeah
people
can
use
it
to
help
gain
additional
knowledge
to
hack
the
system,
but
like
there's
some
so
anyway.
C
That's
why
that
one's
open,
so
the
rest
of
it
is
yeah
the
the
messages
that
we
were
giving
back
on
the
ui
on
the
cli
were
kind
of
inconsistent.
Sometimes
we
would
say
you
know.
Sometimes
we
would
just
give
them
gobbledygook,
like
you
know,
system
system,
failure,
nine
thousand
and
so
you're
working
on
improving.
C
We're
probably
99
sure
that
the
next
thing
that
they're
going
to
want
to
do
is
get
a
token,
so
that
then
they
can
run
the
command
again
like
what
were
they
trying
to
do
on
the
command.
What
what
prevented
them
of
all
the
things
that
were
possible,
the
thing
that
prevented
them
was
an
expired
token
or
an
invalid
token
or
a
token,
that's
not
present.
So
what
are
they
probably
going
to
do
now?
C
They're,
probably
going
to
want
to
run
message
ctl
system
login,
so
we
should
definitely
just
tell
them
explicitly
or
maybe
we
should
run
it
for
them
or
suggest
that
we
would
run
it
for
them.
We
would
take
it
a
step
further,
maybe
but,
but
certainly
starting
with
just
a
concise
set
of
english
words
that
says
you're
an
author,
like
you,
don't
have
a
good
token.
Here's
how
you
get
one
yeah,
that's
the
and
then.
F
That
makes
sense
yeah.
I
was
just
okay,
so
it's
basically
the
same
problem
but
two
different
clients
and
two
different.
You,
okay,
make
sense
well
yeah
kind
of
like
I
said
this
is
the
opposite
of
a
centralized
approach,
I'm
just
throwing
in
an
extra
check
for
these
commands
for
a
302
status
code,
and
then
I
created
a
a
new
error
that
was
like
a
little
more
informative.
F
F
C
It's
awesome.
I
look
at
I
mean
for
my
part,
like
that
language
is
looking
pretty
good.
It's
pretty
concise,
I
kind
of
as
a
separate
but
related
note.
I
kind
of
think
we're
over
pro
we're
over
we're
shoving
the
help
text
in
people's
faces.
Maybe
too
much
because
you
have
this
nice
message,
that's
exactly
what's
going
on,
expired
token,
here's
what
you
do
and
then
we
print
out
all
this
other
stuff.
It's
like!
Maybe
we
don't
need
to
do
that
and
that's
kind
of
a
set,
that's
sort
of
an
aside.
C
Examples
yeah,
I
mean
like
you
know,
because,
because
that
wasn't
quite
the
thing
in
this
case,
like
you
know
like
they
can
always
run
help
if
they
need
to
like.
We
need
to
expect
a
little
that
our
users
of
some
level
of
familiarity
with
cli
commands
and
if
they
want
help
they'll
ask
for
it
like
in
certain
areas.
We
I
think
that
we
should
shove
out
the
help,
tests
and
say,
like
hey,
you
know,
but
in
this
one
it's
like
no,
you
know
it's
not
that
they
typed
the
command
wrong.
C
C
That
would
ideally
only
be
written
once
in
the
code
and
that's
it
and
that
all
commands
that
require
authentication
flow
through
this
check
that
like,
and
so
when
you
just
like
what
I
was
saying
to
muhammad
is
muhammad
says:
well,
hey,
so
I've
got
this
for
the
performance,
calls
and
jared
says:
well,
hey
I've
got
this
perfect
performance.
Calls
it's
like!
Well,
that's
good,
but
it
also
sort
of
is
indicative
of
like
it's
not
as
central
as
it
would
ideally
be
like
you'd,
ideally
say
yeah.
F
Yeah
yeah,
that
was,
I
think
that
was
suggested
and,
to
be
honest,
I
just
kind
of
wanted
to
get
something
working
at
all
before
I
kind
of
went
on
so
yeah,
that's
definitely
kind
of
because
you
mentioned
a
few
different
other
commands.
That
required
token.
So
that's
definitely
something
I
can
kind
of
tackle.
Next
is
putting
it
all
in
a
neat
little
method
that
can
just
be
reused
everywhere,
but
is
this?
C
Took
the
words
out
of
my
mouth,
I
am
ignorant
there
that
that
would
be
ideal
right
because
you
kind
of
want
to
check
it
as
close
to
source
as
possible.
It's
like
hey,
don't
even
bother
with
the
call,
if
you
can
figure
out
that
it's
just
not
even
going
to
work
anyway,
let's
not
put
the
load
on
the
server.
Let's
not
do
that.
C
C
There's
another
thing
that
that
software
that
engineers
will
fall
into-
and
that
is
like
an
over
curation
of
like
over
extent
like
over
engineering
trying
to
get
the
best
experience.
Because
what
would
what
might
happen
like?
Let's
say
we
do
know
how
to
check
for
the
token
expiry
locally
before
we
ask
the
server
it's
like.
Okay.
Well,
in
some
respects,
it's
like
well,
hey,
whatever
the
server
is
doing
to
do
that.
C
C
Once
why?
Because
we
don't,
because
quality
and
consistency
is
driven
and
sustainability,
is
driven
through
a
single
implementation,
so
there's
always
in
any
aspect
of
software
engineering.
There's
always
these
like
this.
This
constant
trait
system
of
trade-offs
between
well
we're
going
for
the
best,
the
best
ux
at
all
costs.
To
like
you
know,
or
are
we
satisfied
with
this
round-trip
thing
that
might
happen
from
the
user's
perspective
they
couldn't
actually
tell.
C
If
there
was,
I
mean
most
people
on
the
cli
wouldn't
really
know
if,
like
the
call
went
out
or
not
so
it
wouldn't
really
it
wouldn't
it
wouldn't
really
improve
their
ux.
We
would
save
a
cycle,
but
we
would
make
it
harder
to
sustain
and
later
when
we
changed
how
the
authentic
token,
when
we
switch
token
types
or
something,
then
we've
got
to
go
re-implement
in
two
places
and
so
wow.
We
just
went
in
a
big
circle
and
said:
I
guess
that
that
it
wouldn't
be
advantageous
to
check
locally.
E
C
Yeah,
that's
a
good,
that's
a
good
one
like
I
think
it's
kind
of
it
you
know
like
it.
It
can
be
reasoned
like
it
can
be
justified
that
what
I
was
saying
before
is
pretty
much.
I
think
you
could
say
is
you
know
essentially
universally
true
that
someone
ran
a
command.
It
looks
correct.
We
tried
to
invoke
it.
The
response
back
from
the
server
was
you
know
that
you
know
you
have
an
expired
token
like.
C
Is
that
how
many
times
have
people
just
say?
Well,
I
have
to
have
a
real
token
yeah.
I
forget
it,
I'm
not
going
to
run
the
command
or
you
know
I'm
going
to
run
I'm
going
to
try
to
do
a
different
one
that
doesn't
require
it's
like.
No,
they
all
are
going
to
require
that
so
tomorrow's,
like
it
might
be
delightful.
C
We
do
want
to
do
some
delightful
things
to
people
for
people
to
say
to
to
not
make
it
arduous,
because
people
might
roll
their
eyes
if,
if
they
really
find
value
in
measuring
or
in
the
tool
they'll
roll,
they
might
roll
their
eyes
and
say:
okay,
fine
I'll
run
this
other
command
I'll
figure.
That
out
and
I'll
go
and
I'll
go
through
that
hassle,
but
some
people
might
hit
that
wall
and,
like
you
know
what
and
walk
away
so
yeah.
C
If
this
might
be
a
good,
if
we
can
tell
them
this,
we
could
also
then
say
log
you
in
or
like
please
log
in
with
this
log
in
now
run
you
know,
and
they
could
answer.
Yes,
no
do
we
do
there's
examples
of
prompting
the
user.
I
think
we're
using
a
library
called
prompt
ui.
I
think
just
not
prompt
ui,
but
something
else
prompt
if
other
people
have
an
opinion.
I
mean
like
the
yep.
This
comes
down
to,
I
say
we're
we're
creating
a
curated
experience,
we're
being
opinionated
about
how
that
behaves.
C
We
hope
that
we're
leaning
into
something
that's
delightful
and
what
the
user
would
expect.
Actually
we're
hoping
what
we
do
to
create
delight.
What
we're
hoping
we
do
is
do
this
slightly
unexpected,
like
they
sort
of
expected,
they
were
gonna,
have
to
deal
with
that
hassle
themselves,
do
what
they
want
to
do,
but
do
it
for
them
and
that
will.
F
C
Yeah
right,
it's
perfect
or
just
yeah
authentication
tokens,
expired,
login
or
or
just
or
run
the.
I
guess
it
depends
on
what
the
login
command
executes
and
whether
or
not
there
are
scenarios
in
which
someone
would
want
to
configure
meschery
before
they
run
system
login,
but
yeah
either
asking
them
or
just
invoking
it
on
their
behalf.
E
C
Here,
mario,
that's
a
perfect
for
my
part,
like
that's
a
perfect
suggestion,
let
me
come
back
to
you
because
my
last
I
recollect
the
system
that
we're
using
has
that
ability
we
just
didn't
get
far
far
enough
to
the
system.
Has
that
ability
we're
not
taking
advantage
of
it,
and
I
don't
think
that
we
got
far
enough
to
like
configure
it.
A
G
Yeah
sure
so
I
have
so.
I
am
currently
working
on
two
animation
part,
one
matching
and
one
spm
pattern
icon
and
the
spinner
one
is
not
fully
ready,
as
I
was
not
well
from
last
couple
of
days,
and
one
of
the
problem
I'm
facing
is
that
the
spinning
part
is
not
available
in
svg
artistic,
so
I'm
kind
of
stuck
that
how
to
spin
the
logo
and
the
second
missing
icon.
I
I
have
updated
the
click
up
and
I've
attached
the
screen,
recording
and
need
your
feedback.
G
F
B
G
H
F
F
F
A
C
B
C
What
an
embarrassment,
if
I,
if
I
don't
I
was
just
trying
to
get
her
some
questions.
Some
questions
answered:
oh
good,
here's,
here's
a
measuring
instance!
What
do
you
know?
I've
got
a
measuring
instance
running.
That's
all
right!
So
so
f,
those
that
have-
and
I
don't
think
I
have
kubernetes
running
so
that
I'm
getting
those
errors
all
right.
It's
no
secret.
C
We've
been
trying
to
get
meshi
v0.6
out
the
door
land
the
plane
put
the
pencil
down
finish
the
dang
thing,
all
the
euphemisms
I
can
throw
at
it
that
doesn't
doesn't
help
get
stuff,
get
it
out
the
door,
but
we're
almost
there
right.
We're
almost
ready
to
release
extremely
close.
We've
been
focusing
on
quality
and
quality
anyway,
once
dot.
Six
is
out.
There's
a
litany
of
there's
a
whole
lineup
of
what's
next
for
in
mesher's
roadmap.
C
Where
might
you
find
that
well,
two
places,
I'm
sure
as
well
a
bunch
of
places,
measures
roadmap,
but
specifically
all
the
things
about
dot.
Seven
is
in
the
mesry
architecture,
deck
which
isn't
necessarily
the
most
obvious
place.
So
that's
why
impart
is
put
out
here
so
that
people
can
discuss
it.
So
here's
the
proposed
seven
road
map
that's
been
out
there
for
a
little
while
there's
a
number
of
people
that
are
on
this
call,
who
are
identified
as
feature
champions
or
or
epic
champions.
C
However,
some
of
these
aren't
necessarily
features
as
much
as
they
are.
We
call
it.
Tech,
debt
or
just
internal
systems
doesn't
matter.
These
folks
are
identified
as
to
to
champion
these
areas.
There's
a
bunch
of
areas,
one
of
those
areas,
one
of
the
bigger
areas,
is
measure
ui,
so
since
I've
spent
some
time
contributing
to
mesherie
it's
okay
for
me
to
say
this:
it's
okay
to
call
our
baby
ugly
or
to
say
that
the
current
user
interface
uses
what
is
referred
to
as
mesh
ops
v1.
C
C
Those
those
operations
are,
you
know,
in
large
part,
statically
configured
like
there's
an
operation
in
the
linker
d
adapter
to
install
linker
d
and
it
it
might
accept
a
couple
of
configurations.
Now.
That
said,
is
it?
Does
that
mean
that
there's
just
a
couple
configurations
by
which
linker
d
is
run
oops
one?
Second,
I'm
gonna
bring
up.
C
C
There's
all
kinds
of
choices
about
what
you
might
want
to
do
point
is
we
need
to
we've,
that's
been
redesigned
and
there's
a
mesh
ops,
v2
now,
so
all
the
adapters,
all
of
them
are
capable
of
such
a
higher
degree
of
configurability
in
terms
of
the
operations
you
want
to
invoke.
So
if
you
want
to
install
traffic
mesh,
you
can
supply
hundreds
of
different
combinations
or
thousands
of
different
combinations
of
configurations
in
the
way
in
which
you
want
to
do
that
all
right.
C
Right
now
is
about
going
through
this
configurator
to
design
to
really
configure
all
the
things
you
might
want
to
do
for
a
given
mesh.
So
I
guess
long
story
short.
I
think
what
it
now,
I
think
what
aditi
was
asking
me
to
do
is
to
say
that,
as
we
lean
in
2.7,
which
is
it's
upon
us
now,
is
to
turn
away
from
this
static
way
of
interacting
and
redesign.
C
C
So
there's
thought
to
be
give
so
here's
here's
some
thought
as
to
how
it
is
that
that
user
experience
can
would
work.
So
you
navigate
through
the
hundreds
of
different
ways
in
which
you're
looking
to
configure
your
service
mesh,
build
it
out.
So
it's
a
configurator,
it's
kind
of
like
ordering
a
new
laptop
which
what
model
did
you
want
I'll?
Take
the
kuma
one
whoops
I'll,
take
the
the
kumo
one.
C
C
C
But
it's
also
about
the
frameworks
that
are
used
in
the
user
interface
in
dot7
there's
an
integration
of
redux
and
use
of
observables,
so
so
some
different
state
management
to
go
on
and
so
much
there's
an
overhaul
of
the
ui,
like,
essentially
all
the
components
rewritten,
there's
a
number
of
you
that
are
participating
in
this
already.
If
you're,
not
it's
an
open
opportunity
to
jump
in
on
the
ground
floor,
so
so
different
components
are
being
rewritten
or
in
the
progress
of
being
rewritten
and
they're
being
done
so
in
context
of
our
integration
of
redux.
C
A
A
Yeah
before
going
to
the
next
item,
this
lee
told
me
to
speak
about
the
machine
0.7,
so
yeah
that
is
like
that
is
a.
There
is
a
lot
of
work
and
there's
a
lot
of
new
opportunities
of
to
learn
like
other
best
practices
and
follow
those
and
are
there
are
already
notes
available
here
if
you
just
scroll
down
below
so
yeah,
where
the,
where
all
the
immersive
ui
contribution
guy
director,
yes
there.
So
please
do
check
out
and
yeah.
A
B
D
So
I
was
working
on
navigation
component
for
the
restructuring
ui.
Last
week
we
discussed
we
decided
to
change
the
collapse
and
expand
arrow.
This
is
the
demo
for
it.
The
thing
I'm
concerned
is
collapse.
The
state
the
button
isn't
quite
visible
as
leo
lee
and
I
talked
talked
and
really
just
suggested-
to
invert
the
color
and
flipping
it
it's
inside
the
menu
in
the
clap
state.
So
I
just
want
to
ask:
should
we
change
the
color
or
do
something
new.
A
F
A
Other
than
that,
if
that
icon
is
like
a
concern
like
which
is
looking
very
small,
then
you
can
use
a
play
item
like
we
use
in
one
of
the
configurations.
So
if
if
the
small
icon
is
a
problem,
otherwise
I
don't,
I
think
the
design
should
be
consistent
with
respect
to
opening
and
closing
the
drawer.
So
a
while
close
while
in
the
closed
it
should
be
the
same
as
while
in
the
open.
Just
our
inverted
arrow
like.
D
A
C
C
C
In
wap,
yeah,
okay,
all
right
the
reason,
so
the
reason
being
that
we
want
to
like
drop
this
opacity
we
want
so
obvious-
is
not
wrong
necessarily
or
onto
its
own.
Is
that
there's
a
another
drawer?
That's
gonna!
That
comes
out
here
in
the
extension
for
a
mesh
map,
and
if
this
is
laying
out
on
top
of
it
that
ain't
gonna
work
hobby,
which
I
I'm,
I
think,
if
you
think
about
a
little
bit
more
you'll
conclude
the
same
thing
that
so
with
the
arrows
that
were
all
we're.
C
C
C
Here's
a
tab,
here's
a
drawer,
it's
the
arrow,
is
pointing
that
way,
so
make
sure
it's
pointing
the
same
direction.
This
is
because,
oh
thank
you,
sir!
It's
you
click
it
and
it
goes
to
zero
pixels.
That's
not
ex!
So
that's
not
exact
and
it
flips
around
right,
not
exactly
what
we're
looking
to
do
because
we'll
always
have.
I
don't
know
what
is
it
three
year
so
rem
wide?
C
We
always
have
a
small
menu
right.
That
shows
you,
the
that
is
the
sidebar.
We'll
always
have
the
side.
It'll
collapse.
It
won't
totally
go
away.
So
it's
a
little
bit
different,
which
is
fortunate
for
us,
because
it
leaves
us
a
little
bit
of
room
to
get
this
button
out
of
the
way.
Why
do
we
need
it
out
of
the
way?
Oh
because
we
have
multiple
levels
of
sidebars,
and
if
this
is
hanging
out
here,
this
will
hang
out
on
top
of
other
elements,
that
people
won't
be
able
to
click
and
so
cool.
C
C
C
C
I
don't
I
don't
know
I
like
yeah,
it's
probably
probably
not
because
it's
not
it's
inconsistent
with
the
way
that
we're
using
the
chevrons
everywhere,
where
else
which
is
which
is
we're
teaching
the
user
to
quick,
a
chevron
to
expand
and
collapse
stuff
so,
which
is
the
same
thing
they're
going
to
be
doing
here.
This
one
is,
it
looks
slightly
different,
but
it's
the
same
function
that
the
user
is
performing,
so
we
should
probably
stick
with
the
same
chevron.
C
B
C
Like,
like,
you
could
say
like
well
technically,
like
you're
flipping
it
around
like
this
one
yeah,
it
expands
and
collapse,
but
like
it's
flipping
around
too
it's
going
to
like
move
on
the
user,
and
so
it's
a
little
bit
different.
So
maybe
you
want
to
indicate
you
know
like
they're,
both
arrows,
but
this
one's
slightly
different
and
it's
behaving
slightly
different
and
then
we
would
take
it
offline
and
we
would
probably
just
let
ya
sue
betty
do
his
thing,
so
everybody
can
get
out
of
here
on
time.
Aditya.
Please
take
it
away.
B
So
the
this
is
the
compilation
matrix
that
I
worked
on
the
now.
The
pages
show
the
latest
results
according
to
the
short
of
each
service
mesh.
So
I
was
just
going
to
ask
like.
Is
this
the
desired
state
like,
and
I
have
also
implemented
to
see
past
it
just
click
here,
tab
which,
when
we
click
it,
we
go
to
all
the
results
of
the
past
of
history,
say:
you're,
sharing
your
vs
code.
B
A
B
Yeah
all
right
so
yeah,
so
this
is
the
implementation
that
I
did,
the
all
the
latest
tests.
According
to
the
service
mesh
shown
in
the
compatibility
metrics
page,
and
when
we
click
on
one
of
them,
we
see
we
can
go.
We
can
click
here
to
see
all
the
past
results
at
the
service
mesh
that
has
been
done
on
the
selfishness.
B
B
Yeah
yeah
and
yeah
there's
yeah,
so
we
are
sorting
through
the
date
and
the
time,
but
I
think
there
is
an
issue
with
the
sort
because,
because
of
the
way
we
are
storing
the
timestamp,
we
are
storing
the
timestamp
in
this
format.
So
when
we
sort
sort
now
the
sorting
happens
on
the
basis
of
alpha,
particularly
on
the
day.
So
if
so,
as
you
can
see,
if
tuesday
january
6,
the
test
was
done,
but
still
we
will
get
your
national
general
five
as
the
latest
results.
I
I
Edge
you'll
have
the
version
of
that
particular
component,
like
the
version
of
that
is
theo
adapter
release.
So
I'm
saying
that
if
the
latest
system
adapter
is
let's
say
five
point
something
point
something
then
it
should
be
like
one
row
says
edge.
The
other
one
says
five
point
something
point
something
so
yeah.
So
one
sort
you
can
do
on
the
basis
of
date.
Another
you
can
do
on
the
basis
of
version,
so
the
latest
one
and
other
than
that
the
edge
edge
one.
So
if
you,
if
you
get
what
I'm
saying.
I
So,
basically,
so
for
basically
first
you
think
in
terms
of
edge,
so
you
sort
for
all
the
edges
for
for
all
the
edge
type
of
version
and
there
you
will
do
sorting
just
like
you're
doing
right
now
on
the
pieces
of
time.
Nothing
changes
there.
The
only
thing,
the
only
one
that
I'm
trying
to
then
that
I'm
asking
you
to
add
is
in
that
row.
I
You
would
use
two
parameters
to
sort
one,
the
date
and
also
the
the
version
so
for
the
steam
for
the
first
you'll
find
the
latest
latest
version.
Actually
there
you
would
not
even
need
the
date,
you
just
need
the
latest
version.
What
is
the
latest
version
so,
for
example,
if
the
latest
version
is
weave
something
point
something
point
something
you
would
show
that
result
in
and
for
edge.
You
will
just
do
simple.
Your
time
based
sorting.
B
B
I
I
Okay,
for
me,
I
think
it
works,
even
if
it
doesn't
say
wednesday,
jan
something
something
because
people
are
not
living
in
utc,
so
it
doesn't
matter
so
you
can.
I
mean
if
no
one
has
any
problem
with
it.
I
think
this
the
last
row,
the
the
pattern
last
row
works
with
me,
so
we
can
work
with
that.
Other.
I
The
above.
The
above
format
would
be
there
like
wednesday,
jan
5..
So
if
you
get
time
you
can
update
it
to
the
last
to
the
you
know,
to
the
format
that
you're
saying
or
you
can
create
an
issue,
and
someone
else
will
pick
it
up.
It's
pretty
straightforward
issue.
So
if
someone
wants
to
change
this
thing,
you
will
need
to
go
in,
you
can
go
in
any
of
the
adapters
go
inside
of
the
github
workflows.