►
From YouTube: Meshery Dev Meeting (Oct. 12th, 2022)
Description
Meshery Development Meeting (September 28th, 2022)
Agenda:
[Nithish] Help Wanted: Static list of components
Components are a way of exposing the capabilities of the underlying platform. In case of application development, Components are entities that are created/registered by the platform engineers and used by the operators.
[Pranav]
Meshery DB upgrade discussion #6367
[Cyrine]
Curating the Troubleshooting Toolkit.
dev/user guide
[Lee Calcote] Messaging Framework and Notification Center
Purpose: instill confidence and offer a high degree of feedback on the status of operations requested, including suggestions on how to fix failed operations.
Transparency in what is actually happening behind the scenes with Meshery’s automation.
[Ashish] Moving to postgres
[Antonette] Go1.19 upgrade is complete.
Updates from Adapter spreadsheet
Chasing down vulnerabilities and security grades
[Nishant] Collaboration Phase 1
[Ruturaj] [Server] Backend for catalog for local provider
For publishing the applications publicly the user’s public design can be linked to their member profile.
[Ruturaj] Fix mesheryctl config#6374, Non issue#6334
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
B
Hi
guys,
my
name
is
Michael
Franklin,
and
this
is
my
first
time
in
the
call
so
yeah
I,
think
I
I
joined
mystery
about
three
three
weeks
ago
and
I
actually
did
my
first
contribution.
Yesterday
you
see
an
open
PR,
it's
now,
it's
close
so
still
working
on
it
so
yeah,
that's
it
hope.
Everyone
can
hear
me.
A
B
Hi
everyone,
my
name,
is
Abdullah
Rafi
I'm
a
third
year
student
at
nitk
Karnataka
in
India
and
yeah
I've
joined
my
Shri
about
I.
Think
it's
been
two
weeks
now
since
I've
joined
the
slack
Channel
I
made
my
first
PR
to
leadfi's
website
and
since
then,
I've
been
studying
about
service
measures
to
contribute
to
my
city.
Hopefully.
A
A
Sure,
thank
you
so
yeah.
If
I
miss
anyone
feel
free
to
unmute
yourself
and
say
hi.
So
I
s
so
before
we
start
so
I
am
sharing
the
meeting.
Medicine
chat,
make
sure
you
write
down
your
names
in
attendees
list.
So
with
that,
let's
start
with
our
first
meeting
agenda,
which
is
by
nitish.
So
please
with
us
today.
A
C
So
my
agenda
item
is
about
a
recent
issue
which
were
discovered
in
which
new
components
were
not
being
saved
into
the
machine
database,
and
we
were
seeing
these
errors
this
recent.
Let
me
tell
you
first
what
what's
happening
actually
measly
whenever
Mr
discovers
kubernetes
cluster
it?
It
saves
the
components
in
the
cluster
into
the
local
database,
and
then
it
shows
them
onto
your
dashboards,
based
on
what
you
have
in
your
cluster.
C
So
recently,
I
updated
the
mystery
database
schema
in
which
I
added
few
new
constraints
so
that
we
don't
duplicate
the
data
which
we
stored,
just
for
so
that
we
have
a
performance,
Improvement
and
based
on
that,
since
the
old
I
have
explained
it,
since
the
older
databases
which
are
carved
from
the
older
schema
would
wouldn't
allow
saving
new
data
which
are
which
is
being
saved
while
referring
to
the
new
schema.
So
this
was
the
error,
and
this
will
get
solved
known
as
you
get
you.
C
You
said
you
purchase
your
database
as
soon
as
you
do
this.
It
will
get
solved
because
your
database
will
all
your
tables
would
be
truncated
and
it
would
then
regenerate
the
tables
with
new
schema.
So
though
this
shouldn't
be
the
case
we
should
we
should
handle
this
more
more.
We
should
handle
this
in
much
better
way
in
which
we
should
show
that
there
is
a
new
Banner
in.
C
There
is
a
new
ask
for
a
banner
in
mystery
UI,
so
that
whenever
there
is
an
update
to
measury
database,
then
the
banner
should
come
over
here
and
should
ask
we
should
yell
at
user
so
that
they
should
upgrade
their
schema.
They
should
upgrade
their
machine
database.
So
that's
the
thing
on
which
I
would
be
working
on
next.
So
if
in
case
you
see
this
error,
then
you
probably
need
to
reset
your
database
and
then
it
will
get
solved.
So
this
is
just
observed
by
recent
or
existing
user.
D
The
measury
docs,
which
is
where
the
upgrade
guide
lives,
is
those
docs
are
versioned
based
on
minor
release,
so
I
think
we
snapshot
it
at
a
v0.4
and
we
snapshotted
the
docs
again
at
a
v0.5
and
then
we're
currently
iterating
on
v0.6.
And
so
what
I
mean
to
say
is
if
there
became
a
long
history
of
like
upgrading
from
dot
four
to
top
4.5
to
like.
If
it
got
really
long,
it
would
only
be
so
long
as
intra
minor
release
so
yeah
anyway,
we
just
gotta.
B
B
D
C
Yeah,
so
currently
we
are
thinking
currently
there's
an
ask
to
add
a
banner
so
that
whenever
a
certain
release
is
there
which
which
could
lead
to
a
breaking
change,
so
this
Banner
will
show
that
there
is
a
requirement
of
your
upgrade
upgradation
of
your
database
and
with
that
we
can
handle
this
change
more
in
much
better
way.
So
I'll
this,
we
need
to
look
into
the
MI
material
UI,
one
so
I'll
be
looking
into
that
mode.
B
A
D
Oh
okay,
yeah
well
I'll,
try
to
be
a
bit
brief
about
this.
This
has
been
an
ongoing
piece
of
functionality
or
or
many
pieces
of
functionality,
so
for
those
that
so-
and
this
is
something
that
it's
time
to
advance,
so
it's
been
in
the
plan
on
the
roadmap
for
a
long
time,
probably
about
a
year
and
a
half
that
we've
had
the
roadmap
planned
out
for
from
like
dot,
4.5.6.7.8.9
1.0
and
we're.
So
now
is
the
time
that
we
get
to
come
and
focus
on
this
particular
set
of
functionality.
D
So
gaurav,
if
you
don't
mind,
if
you're
able
to
share
this
for
a
moment
that,
for
most
of
us,
are
quite
familiar
with
the
fact
that
meshri
as
an
application
is
distributed
in
nature
and
not
every
mesh
redeployment
looks
the
same,
which
is
to
say
that
you're
able
to
deploy
certain
adapters
or
not
other
adapters
or
turn
off
various
components
and
turn
on
various
components
of
meshery
and
the
further
the
project
goes
along
likely.
The
I
mean
we
will
only
continue
with
that
plug-in
model.
D
D
Not
all
of
the
communication
happens
that
way,
but
a
lot
and
yeah.
So
in
order
for
so,
we
want
to
have
a
common
message:
format
to
be
able
to
as
individual
as
you
know,
there's
I
don't
know,
350
something
people
who've
contributed
to
just
messery
server,
just
the
main
repo,
not
all
the
other
repos.
So
there's
a
lot
of
people
that
come
and
go
and
as
they
as
we
go,
we
want
to
be
consistent
with
how
these
different
individual
components,
exchange
messages
and
notifications,
and
that
has
there's
an
initial
implementation
of
this.
D
That's
been
done
and
has
been
done
for
quite
some
time.
There's
a
messaging
format
that
occurs
when
an
operation
is
invoked.
So
when
a
user
says
that
they'd
like
to
deploy
a
service
mesh
that
they'd
like
to
deploy
a
Helm
chart,
they'd
like
to
you
know,
they
request
meshery
to
do
an
operation
like
that.
Well,
there's
a
set
of
information,
that's
exchanged
between
generally
between,
like
Mastery
server
and
one
of
the
adapters,
and
it
goes
off
and
does
work
and
comes
back
and
there's
some
communication.
That
happens
well.
D
D
Air
utility
that's
been
built
into
mesh
kit,
which
is
a
common
Library
used
in
each
of
meshery's
components.
Really
pretty
neat,
there's
some
golang
language
instrumentation,
that's
done
in
use
of
that
and
that's
a
whole
separate
topic
about,
but
anyway
the
point
is
Mastery.
Has
these
this
cusp?
These
custom
error
messages
that
will
be
sent
when
an
error
does
occur
and
it
uses
this
messaging
framework
to
exchange
information
about
the
status
of
an
operation.
D
It
is
not
confidence
inspiring
for
a
user
to
sit
in
front
of
meshri's
UI
to
click
on
an
operational
request,
and
you
know
on
one
hand
it
feels
good
to
have
the
little
leprechauns
and
the
magic
sprinkles
go
off
and
like
automate
some
infrastructure
and
do
some
things,
but
unless
you're
really
comfortable
with
what
meshri
is
doing
under
the
hood,
you
as
a
user,
you
would
really
like
to
know
what's
going
on
specifically.
What
is
it
doing?
Moreover,
where
is
it
at
in
that
operation?
D
D
I
think
there
were
going
to
be
some
other
message:
types
that
that
maybe
some
about
policy
policy
being
violated
if
people
are
defining
policy
and
how
they
want
their
infrastructure
to
run,
to
measure
detects
a
violation
that
it
would
send
a
notification
about
that.
Those
are
kind
of
three
examples
of
message
message
formats
and
by
that
I
just
mean
the
way
in
which
you
mark
up
the
message.
The
way
in
which
you
would
expect
what
information
you
would
expect
to
receive
and
have
interchange
between
components
great.
D
But
what
about
the
mechanism
by
which
you
exchange
the
message?
Over
The
Wire?
That
would
be
something
like
HTTP
2
or
you
know,
grpc
protobuf
dolang.
Those
are
tools
that
can
be
you
that
we're
using
today
to
exchange
messages,
we're
also
using
Nats
Nats
as
a
modern,
distributed
Enterprise
message:
bus,
we're
using
maps
in
certain
areas
to
exchange
messages,
and
so
it
is
time
to
light
up
mesheries
user
interface
with
an
enhanced,
well
you'll,
hear
me
probably
interchangeably,
say
Notification,
Center
or
Operation
Center
Cara.
D
Do
you
mind
clicking
on
the
the
link
there?
Is
this
full?
It's
right
above
architecture
diagram
where
your
cursor
is.
It
says
full
see,
Cisco
intersight
for
see
where
it
says
full-sized
image.
So
your
cursor
right
now
on
the
dock
is
on
notification
center
inside
the
dock
itself,
not
in
the
outline
yeah.
If
you
go
yep,
this
is
just
a
screenshot
of
different
management
software.
Some
of
you
have
been
around
this
place.
D
Long
enough
are
like
have
heard
me
talk
about
this
topic
before
and
you're
probably
checked
out
at
the
moment,
because
you're
like
tired
of
hearing
about
it,
but
it's
it's
something
that
I
think
that
we're
finally
ready
to
do.
We
have
a
lot
of
the
tools.
The
the
functionality
in
place
to
get
garv
is
zooming
in
on
the
right
section.
It's
this
right
hand,
side
in
this
case
this
particular
piece
of
software.
D
It's
a
management
tool
that
focuses
on
Cisco's
hardware,
and
it
has
a
notification
center
I,
don't
even
know
what
they
call
these
things,
but
it
has
about
three
centers.
If
you
will
this
one's
for
alarms,
critical
alarms,
warning
severity,
alarms
all
alarms
info
about
what
it
is
it,
the
likely
you
can
click
the
Deep
link
into
the
particular
piece
of
infrastructure
that
you're
managing
and
see
the
alarm
on
the
in
the
dashboard.
D
D
That's
not
something
that
we're
necessarily
trying
to
address.
This
is
why
that
other
doc,
the
messaging
framework
and
notification
center
design
spec.
It
needs
to
be
probably
broken
down
into
a
couple
of
specs,
because
there's
a
difference
between
showing
that
information
to
the
user
and
then
subsequently,
following
it
up
with
the
actions
that
I
just
mentioned,
retry
cancel
rollback.
D
That'll
require
a
workflow
engine,
and
so
yeah
I
wanted
to
bring
this
up.
Let's,
let's
revive
this:
let's
break
it
down
into
manageable
chunks,
Ashish
and
root.
Raj
or
uzair,
rather
have
recently
enhanced
the
meshery
adapters
to
send
back
a
lot
more
Telemetry
about
operations
and
their
status,
and
so
for
those
of
you
who've
been
using
metro.
You
might
have
noticed
a
bit
more
feedback
is
occurring
real
time
and
that's
great.
That
needs
to
be
continued.
We
need
to
continue
to
enhance
that.
B
E
B
F
Okay,
so
one
thing
that
was
on
the
roadmap
was
the
migration
from
sqlite
database
to
postgres.
Right
now
we
use
sqlite
because
it's
lightweight
and
it's
kind
of
an
embedded
database,
and
we
don't.
We
don't
have
that.
We
didn't
have
that
many
requirements
from
the
database,
so
we
didn't
move
to
postgres,
but,
as
Lisa
said,
we
would
be
incorporating
a
workflow
engine
and
all
those
things
and
a
choice
that
can
be
made.
A
potential
choice
is
temporal
and
temporal
requires
postgres
as
a
default
database.
F
So
now
we
are
on
a
stage
where
we
require
more
from
our
database
where
things
like
retries
and
all
those
all
the
states
would
be
all
the
states
of
your
operations
would
be
stored
and
all
so
there
is
a
recent
PR
that
was
made
because
we
used
Gom
as
a
orm
library.
The
changes
were
very
minimal
and
this
is
still
on
a
testing
phase.
Right
now,
most
of
the
things
have
been
tested
and
pranav
has
and
pranav
in
Serene
have
helped
testing
this
PR.
F
F
Some
things
are
functions
that
postage
doesn't
support
other
than
that
the
gocom
pretty
much
hides
all
the
sophisticated
stuff.
So
if
we
use
all
the
goms
helper
functions,
we
can
just
on
the
Fly
replace
the
core
engine
that
was
previously
sqlite
and
now
it
would
be
postgres
and
few
things
I
have
left
out
here
that
are
currently
in
my
local
branch.
I
haven't
committed
and
I
will
commit
them
after
merging
this
PR,
which
would
be
fixing
so
just
I.
Have
a
small
question
to
this.
F
I
I
mean
I,
didn't
get
around
validating
this
thing,
so
I'll
ask
for
now
because
he
was
testing
this.
So
now
is
the
next
thing,
change
that
that's
been
made
here.
You
were
testing
it,
so
is
this
backwards
compatible
with
the
current
sqlite
database
or
the
this
Gom
tag
is
like
required
for
C
polite
right
now,.
C
F
After
this
PR
is
most
right
now.
Also
most
things
would
work.
There
is
just
one
error
that
you'll
get
and
that
error
will
be
solved
by
this
PR,
so
yeah.
Hopefully
we
can
get
this
done
by
by
the
end
of
this
week,
so
we
we
can
come
completely
migrate
from
completely
migrate
to
postgres
I
mean
we
started
out
from
bitcast
and
last
year
around
this
time
we
moved
migrated
to
sqlite
and
because
there
was
a
soft
migration,
not
many
things,
not
many
changes
required.
F
D
D
D
There
are
a
couple
of
go
maps
running
around
yet
this
particular
slide.
Not
only
is
a
roadmap
slide
pointing
to
a
future
release,
but
it
also
is
hopefully
helpful
to
everyone
to
understand
what
data
is
being
stored
where
I'm
just
seeing
I
think
I
think
this.
This
line
needs
to
be
updated,
probably
just
to
say
sqlite
or
something,
but
not
big
cask
but
yep.
So
that's
it
sorry.
I
dropped
the
link
to
this
in
the
zoom
chat,
comments
or
questions.
B
D
Nice
but
it's
an
area
of
potential
interest
for
Franklin.
So
that's
that's
good,
yeah,
yeah
sure
I
have
a
I
have
a
couple
of
questions,
but
maybe
a
request
before
the
questions
ensue,
which
is,
could
we
get
a
diagram
of
what
a
deployment
might
look
like
and
if
there
are
different
supported
deployments
with
postgres
that'd?
Be
nice.
B
A
E
Yes,
hello
again,
so
this
document
is
meant
to
be
a
sent,
a
kind
of
a
guide
that
has
all
the
needed
information
that
a
new
user
from
Mastery
or
a
new
developer.
That's
joining
Mastery
could
use
to
kind
of
understand
the
big
parts
that
make
up
Mastery
and
how
to
deploy
certain
components
and
how
to
troubleshoot
the
most
known
errors,
so
kind
of
started
off
by
talking
about
the
possible
measure
deployment
scenarios
and
for
for
user,
and
then
the
operator
investing
and
broker
to
go
then
into
troubleshooting.
E
One
thing
that
I
think
could
be
used
to
that
could
be
added
to
this
document
are
the
hours
that
already
exist
for
the
ones
that
have
codes
that
were
created
using
a
mesh
kit
for
the
broker
and
messing
I,
saw
I.
Think
I
left
a
comment
for
that.
I
saw
that
there
already
existed
quite
a
few
that
are
not
really
used,
especially
for
the
you,
the
UI,
for
example,
when
there
is
a
an
issue
with
a
broker
kind
of
get
a
message
as
a
toast,
but
not
really
something
in
the
notification
notification
bar.
E
Yes,
so
Nick
I
tried
to
kind
of
dig
into
the
code
and
see
what
statuses
existed
and
found
that
there
are
quite
a
few
in
the
UI
and
then
the
back
end
that
are
different,
for
example,
for
Mass
sync
in
the
UI
and
messing
in
the
back
end
India.
It
has
way
more
statuses
and
connected,
for
example,
in
the
back
end,
only
the
broker
has
that
status,
so
I'm
kind
of.
E
If
someone
could
maybe
look
into
this
with
me-
and
maybe
we
can
even
try
to
make
like
an
example
of
how
we
could
minimize
these
statuses
and
keep
them
the
same
on
the
back
end
and
UI
and
I.
Think
that
would
make
it
much
easier
to
understand
the
code
and
answer
to
then
maintain
it
and
and
make
it
cleaner.
E
There's
also
a
few
statuses
that
I
couldn't
really
figure
out
what
they,
what
they
were
used
for,
like
for
the
controllers,
enabled
running
connected
unknown,
that
I
found
that
they
were
defined,
but
I
couldn't
really
figure
out
what
the
condition
was
for
them
to
be
applied
to
the
controllers.
So
if
anyone
knows
the
answer
to
these
that
it
would
really
be
helpful
if
they
could
maybe
leave
a
comment
on
the
document
or
or
maybe
just
send
me
a
message
or
I'd.
Send
them
a
message
and
figured.
We
figured
out.
F
So
each
of
these
things
operator
matching
and
broker
all
these
three
things
are
considered
as
machine
controllers
and
each
controller
has
the
same
set
of
States,
so
whatever
state
one
has
and
you
can
find
these
states
inside
of
mesh
kit
instead
of
models,
I'll
drop
a
link,
and
there
is
the
enum
and
UI
should
refer
to
that
in
and
because
and
I
mean
those
enums,
they
they're
a
DOT
string
method
on
them.
So,
of
course,
when
you
get
the
response
back,
you
can
find
out
the
actual
value
of
it,
so
I
think
use.
F
D
D
F
Some
State
from
here
is
being
translated
as
active,
because
backend
never
sends
the
active
state
so
ABI.
What
is
the
dip
is
deployed
active
with
which
one
of
these
states
is
translated,
as
active,
so
I
think
enabled
or
running
like
anything
other
than
disabled
or
not
connected?
Is
you
know,
perceived
as
active
state.
D
F
Controller
status
right
now,
like
most
of
the
time,
just
keep
disabled
or
enabled
or
unknown
so
yeah
I.
Think,
basically
you
can.
No
you
don't
you
shouldn't,
have
any
hardcoding
on
the
UI
just
take
whatever
value
is
here
and
then
translate
that
on
the
UI
like
send
that
by
translate
I
mean
just
said
that
there's
a
one
to
one:
there
should
be
a
one
to
one
yep
yeah,
that's
not
being
done
at
least
now
so
probably
yeah.
Actually,
this
needs
a
bit
of
change.
E
D
E
E
I
also
tried
to
kind
of
add
the
parts
for
build
meshery
operator
and
build
measuring
sync
and
other
other
stuff
that
could
be
used
for
that
could
be
useful
for
a
developer
and
one
question
that
I
had
when
writing
this
guide
was
that,
from
a
user's
point
of
view
in
the
guides
for
users,
section
of
the
first
one
for
possible
Mastery
deployment
scenario
that
doesn't
really
seem
to
be
any
other
way
to
deploy
Mastery
without
the
operator
and
controllers
other
than
using
the
helm
charts.
Is
that
I
thought?
D
It's
is
that
what
you
were
asking
like
you
know,
so
they
can
go
direct
to
helm.
They
could
you
can
use
Mastery
CTL
as
a
client
that
will
directly
talk
to
kubernetes
and
under
the
covers,
use
common
functions
inside
of
mesh
kit.
So
hopefully
these
right
here
and
then
so
too,
will
Mastery
server,
use
the
same
common
functions
from
mesh
kit.
You
know
these
right
here
to
ultimately
use
the
helm,
charts
to
deploy
itself
or
its
components.
E
So
I
was
wondering
if
there
was,
if
that
would
also
existed,
using
mesh
resettle,
maybe
using
a
tag
or
something
that
could
mean
that
you
are
trying
to
to
have
magic
without
the
operator.
Maybe
that
was
something
that
I
haven't
seen
or
that
wasn't
very
clear
in
the
documentation
and
I
could
then
add
it
in
here.
D
D
So
it
sounds
like
a
a
good
feature
request,
a
fairly
simple
flag,
actually
on
Mastery
CTL
and
the
thing
is,
is
like
well
to
the
extent
that
one
client,
Mastery
CTL,
might
have
a
flag
for
that
type
of
custom
deployment.
That
so
too
then
could
measure
UI
as
a
different
client
potentially
also
have
a
check,
mark
or
flag.
That
says
that
that
controls
the
same
behavior.
E
E
D
F
Okay,
so
like
yeah,
we
can
have
that
plug-in
measuring,
CTL
and
other
than
that
other
way
of
doing.
That
would
be
manually,
which
would
be
Helm
repo,
and
if
someone
is
doing
that,
of
course,
because
the
operator
and
machine
charts
have
recently
been
spread
out,
so
they
can
just
do
help
install
just
machinery,
and
that
will
only
install
mostly,
but
if
they
have
installed
just
as
a
machine
and
if
they
come
to
the
they
come
to
the
dashboard.
F
E
D
D
D
Good
thanks
for
putting
together
that
doc,
so
everybody
serene's
looking
for
feedback.
What
she's
attempting
to
do
is
we'll
close
the
gap
between
the
loads
of
functionality
and
different
possibilities
that
you
can
do
with
the
software
and
the
Delta
between
what's
described
in
mesh
redox,
so
she's
trying
to
make
that
make
there
not
be
a
difference
so
for
anyone
who's
new
to
the
project,
it's
actually
a
good
place
for
you
to
go
or
to
go.
D
G
G
Okay
so
most
everything
on
the
list
has
already
been
updated
to
1.19
and
as
I
mentioned,
there
are
two,
but
one
is
defecated,
so
it
shouldn't
be
any
activity.
I
will
be
sending
a
a
PR
to
make
a
note
that
this
project
is
not
to
be
used,
and
can
anyone
explain
to
me
about
VMware
Town
Jew?
Is
it
just
still?
D
D
D
So
but
yeah
when
the
when
that,
so
that
adapter
is
in
Alpha
and
when
it
was
initiated
as
a
repo
and
kind
of
the
initial
scaffolding
put
into
the
adapter
tanzu
had
yet
to
be
made,
GA
and
and
it
since
has
been,
and
then
but
there's
licensing,
Associated
and
so
I.
Think
Hussein
is
pointing
out
that
oh,
there
might
be
a
Community
Edition
that
we
can
work
with
to
develop
the
adapter
so
so
yeah.
So
it.
D
G
Okay,
so
that
does
make
sense.
I
I
was
looking
at
the
offering
and
I
did
read
that
VMware
had
took
over
octane
invited
into
town,
zoo
and
then
I
thought
I
remember,
reading
somewhere.
That
Andrew
also
had
the
Community
Edition,
so
yeah.
However,
we
do
it.
I
mean
I
can
do
the
initial
parts
and
make
sure
that
nothing
breaks,
and
then
we
can
just
go
from
there.
D
One
thing
that
tangential
to
this
is
the
notion
that
each
of
the
make
files
for
the
different
components
it
I
think
it
throws
a
warning.
If
the
contributor
doesn't
have
the
binary
go
one
right
and
it
we
might
be
able
to
relax
that
a
little
bit
so
that
it's
not
necessarily
go
one,
nine
one
dot
19.1.
Maybe
it
could
just
stop
at
119
or
an
Antoinette,
you
might
know
better.
D
G
So
I
will
say
from
from
what
I've
been
doing
as
long
as
you're,
not
using
as
long
as
the
project
is
not
set
at
1.17
and
you
have
118
and
119,
then
it
will
complain.
It
will
ask
you
if
you
want
to
do
a
compatible
or
not,
but
if
you
have
the
project,
the
the
module
at
1.18
or
19
or
above
you
should
be
fine,
so
we
can
relax
it,
but
we
can
also
just
make
a
note
hey.
G
G
There's
a
session
in
the
make
file
that
it
will
download
a
particular
binary
for
you.
So
I
was
thinking
about
adding
that
and
some
of
the
make
files
for
the
for
the
the
goaling
CI
lint.
So
that
would
just
help
to
make
a
uniform
make
sure
that
we're
working
on
the
same
version,
but
you
know
you're
not
forced
to
have
to
download
it
on
your
own
PC.
D
Yeah
yeah,
it
makes
a
lot
of
sense.
There's
I
dropped
another
suggestion
into
the
zoom
chat
about
how
to
potentially
keep
the
requirements
but
relax
the
Grease
the
wheels
of
contribution.
Sometimes
the
people
just
have
a
single
version
of
go
installed.
Maybe
it's
go
119
that
I
think
the
test
in
the
make
file
today
looks
yeah.
Anyway,
you
can
read
the
comment
but
yeah
yeah.
B
G
B
G
G
A
G
Oh
yeah,
so
the
update
from
the
adapter,
let's
see
I,
haven't
made
the
update,
yet
actually
I
do
need
to
go
back
and
check
through
them.
There
was
one
or
two
that
I
found.
It
was
lacking
a
little
bit
on
the
feedback.
When
you
try
to
run
the
adapter
I
did
I
believe
I
did
submit
one
for
celium
because
it
was
what
would.
G
I
think
I
submitted
one
yesterday.
Oh
yes,
so
I
submitted
one
yesterday
to
upgrade
the
two
adapters
of
the
meth
kit
and
the
library,
but
I
also
noted
the
there
were
because
the
adapter
Library
have
to
be
updated.
There
were
some
certain
features
that
were
not
there
before,
but
there
are
now
so
they
have
been
updated.
They
run
just
like
how
it
is
from
the
SEO,
but
the
rest
of
them,
the
one
that
haven't
really
been
updated.
G
They
may
need
to
come
close
to
it
so
that
we
can
get
a
little
bit
more
feedback
on
what
are
the
adapting
to
update
the
new
component.
If
you
need
to
you
know
log
any
errors,
but
the
other
one
is
the
vulnerabilities
and
the
security
grade.
So
I
am
going
back
to
each
of
the
libraries
and
the
each
of
the
adapters
to
make
sure
that
they
are
uniform
in
the
the
base
images
as
well
as
if
they
are
using
the
same
version
or,
if
they're,
using
an
earlier
version.