►
From YouTube: wasmCloud Community Meeting - 1 March 2023
Description
Welcome to the wasmCloud community! Tune in live where we discuss the latest developments in the wasmCloud ecosystem, WebAssembly standards, and break out sweet demos.
Agendas for wasmCloud community meetings can be found at: https://wasmcloud.com/community
A
All
right,
hello:
everyone
welcome
to
the
waslam
cloud
community
meeting,
Wednesday
March
1st
new
month
wow
that
happened
pretty
quick.
We
got
a
a
pretty
nice
agenda
today
and
what
we're
actually
going
to
start
off
with
we
have
a
new
Community
member
Frank.
Would
you
like
to
do
an
introduction,
really,
quick?
You
know
what
you,
what
you
do
anything
that
you
feel
like
sharing
sure.
B
B
It's
not
my
day-to-day
job,
but
I'm
I
want
to
start
playing
around
with
this
and
see.
How
far
can
I
go
I'm,
mostly
interested
on
the
back-end
side
of
things,
so
I
want
to
see
anything
from
the
point
of
your
orchestration
and
really
scalability
of
applications
within
that
space.
A
So
today
what
we've
got
on
schedule,
we're
going
to
talk
a
little
bit
about
cargo
next
test
the
tool
and
wash
integration
test
and
then
I'll
be
doing
a
really
short
demo
kind
of
on
behalf
someone
one
of
the
one
of
the
people
at
cosmonic
who
contributed
something
to
the
Watson
Cloud
dashboard
and
then
going
to
hand
off
to
Taylor
to
talk
a
little
bit
more
about
the
wadham
RFC.
A
You
know,
there's
been
some
comments
and
activity
on
that
RFC,
so
love
to
kind
of
just
get
a
little
update
and
call
for
another
round
of
feedback
as
we
go
into
finalizing
that
proposal
and
without
further
Ado
Matt
I'll
go
ahead
and
hand
off
to
you
to
talk
about
cargo
next
test.
D
C
All
right
so
Sarah
dust
off,
I
guess,
follow
these
videos.
Okay,
So
today
we're
talking
about
cargo
next
test,
which
is
a
new
test
runner
for
rust
tests.
That
has
a
carries.
A
number
of
kind
of
benefits
which
you
can
list
off
here,
probably
the
most
interesting
ones,
is
that
it
it's
a
lot
faster
because
of
a
different
architecture
they
use
for
executing
the
tests.
C
It
can
help
you
identify
slow
and
leaky
tests,
there's
a
whole
bunch
of
like
configuration
options
that
make
it
a
lot
more
kind
of
customizable
than
just
you
know,
running
cargo
tests
as
we
do
currently-
and
you
know
you
do
by
default
and
rust,
but
the
the
most
important
one
at
least
that
I've
identified
is
that
in
the
wash
project
we
have
a
number
of
integration
tests
that
and
that
rely
heavily
on
network
calls
and
I
O,
which
makes
them
and
kind
of
inherently
no
matter
what
we
do.
C
They're
going
to
flake,
sometimes
and
cargo
next
test
lets
you
automatically
retry
these
tests
and
specify
kind
of
how
many
times
you
want
to
retry
them,
and
if
you
want
to
do
kind
of
a
back
off
or
or
kind
of
what
the
algorithm
you
want
to
use
to
retry
them,
which
makes
it
a
lot
easier
on
our
side
when
the
these
flakes
do
happen,
you
know
the
the
test,
Runner
just
retries
the
tests
and
makes
it
so
we
don't
have
to
deal
with
it
basically,
so
this
is
kind
of
something
I
proposed
and
I
opened
a
PR
on
the
wash
repo
to
add
next
test
as
a
test
printer
for
all
of
our
tests.
C
The
kind
of
drawbacks
to
this,
which
we
discussed
kind
of
down
here,
is
that
Nexus
is
another
tool
and
it's
a
tool.
You
need
to
install
running
a
either
by
you
know,
running
cargo,
install
next
test
or
downloading
the
binary,
and
it
just
adds
that
kind
of
extra
level
of
churn
of
like
you
want
to
contribute
to
wash.
C
I
totally
get
that
so
it's
kind
of
a
discussion
point
they
want
to
bring
up
a
meeting
of
of
you
know.
Is
it
worth
it
to
switch
to
next
test
and
support
that
test
Runner
and
ask
everyone
who
begins
maintaining,
wash
or
contributing
to
wash
to
install
the
test
Runner?
C
Or
is
it
preferable
to
just
stick
with
cargo
test
and
kind
of
deal
with
these
flakes
as
they
come
along,
and
you
know
figure
out
a
way
to
just
retry
the
tests
on
GitHub
and
they
fail,
and
that
kind
of
thing
I
think
that
especially
the
past
week,
when
we've
kind
of
added
these
depend
about
things
thanks
to
Roman
for
for
working
on
those
We've
noticed
a
lot
more
flakes
I
think
you
know
the
number
of
PRS,
as
the
number
of
CI
runs
increases.
C
We've
just
been
flaking
a
lot
more
in
these
integration
tests.
So
I
think
this
is
becoming
kind
of
more
of
a
problem.
I
mean
continue
will
become
more
of
a
problem.
So
it's
kind
of
you
know
a
question
of.
C
Do
we
want
to
have
people
install
this
tool
and
kind
of
deal
with
the
kind
of
one
more
tool
turn
of
that,
or
do
we
want
to
stick
with
what
we've
got
and
just
kind
of
make
do
with
the
flaky
tests
so
yeah,
that's
kind
of
the
question
to
the
to
the
to
the
general
community
and
something
that
I
was
discussing
with
Taylor
on
here
and
Brooks.
So
if
Brooks
wants
a
step
venture.
A
Yeah
I
just
had
a
I've,
got
a
a
quick
question,
just
pretty
high
level
so
with
cargo
next
test,
I
saw
in
the
pr
there's
like
kind
of
like
a
manifest
or
something
that
you
set
up
for
like
settings
for
the
test
runs.
A
Does
this,
but
does
this
actually
change
anything
about
the
way
that
we
write
tests
like?
Do
we
just
write
cargo
tests,
like
kind
of
the
same
way
like
unit
and
integration
tests,
the
way
that
we
did
before
or
do
we
have
to
do
something
different.
C
Yes,
there's
one
small
difference:
I
actually
pointed
on
that
PR,
which
is
that
next
test
doesn't
run
serial
tests
in
the
same
way
that
we
kind
of
do
currently
with
a
cargo
test.
So
you'll
see
here
actually
in
this
PR
I
removed
the
used
serial
the
serial
test
macro-
and
you
know,
remove
this
from
all
of
the
tests,
because
these
don't
work
on
on
X
test
and
access
doesn't
doesn't
listen
to
this
and
just
runs
them
all
together.
C
Even
if
you
have
these
these
annotations,
and
so
we
need
to
do
a
next
test
is
if
we
scroll
down.
E
C
And
yeah
so
there's
this
definition
of
the
test
groups.
So
you
define
a
test
group
that
you
then
tell
it
how
many
threads
you
want
to
run
those
tests
on,
and
then
you
specify
a
filter
for
what
tests
should
be
in
that
group.
So
for
here
right
now,
it's
just
the
the
build
tests
and
the
up
tests,
which
are
generally
the
ones
that
we're
using
the
serial
macros
on
right
now.
But
we
need
to
continue
to
add
to
this.
C
If
say,
we
create
another
test
file
that
has
serial
tests,
that
we
need
to
specify
or
need
to
be
added
here.
I
think
the
kind
of
one
of
the
question
marks
we
had
is
that
stuff
like
this
makes
it
super
hard
to
be
able
to
support
both
cargo
test
and
next
test.
C
So
it's
kind
of
of
my
opinion
that
we
really
shouldn't
support
both
test
Runners,
because
something
like
this
could
happen,
and
it
also
could
be
small
differences
between
the
two
test
Runners,
but
that's
kind
of
that's
kind
of
where
I'm
coming
from,
where
I
really
would
prefer
not
to
support
both
and
if
kind
of
we
we
do
think
that
the
pain
of
churning
to
a
second
tool
is
too
much.
Then
you
know
figuring
out
ways
to
to
make
cargo
tests.
C
F
D
F
But
in
general
I'm
in
favor,
of
having
a
nice
test
as
the
test
Runner
but
I
think.
Ideally,
there
should
be
limited
just
to
CI
right
to
speed
up
CI,
but
developers
should
be
still
able
to
use
the
tools
they
used
to
be
using.
So
there
should
be
the
ability
to
just
do
a
cardinal
test,
but
in
any
case
I
think
maybe
it's
worth
taking
a
little
step
back
here
and
then
see
if,
like
so,
if
you're
trying
to
fix
the
flakes,
it's
changing
the
test.
F
Runner
the
right
way
to
do
it
right.
It
shouldn't
be
just
fix
the
flakes
right
in
some
way
and
like,
for
example
like
if
you
talk
about
like
one
thing
that
I
could
think
about,
is
that
it
seems
like
we
would
want
to
not
require
serial
testing
at
all
right
so
to
make
the
test
actually
self-contained
and
isolated.
F
So
in
that
case,
then,
if
there
is
no
need
for
serial
created
at
all
in
general,
then
it
doesn't
really
matter
if
the
person
uses
cargo
tests
or
cargo
next
test
right
and
then
step
after
that
could
be
that
figuring
out
how
we
could
yeah
the
issues
to
display
key
tests.
So
maybe
there's
a
way
how
we
could,
like
you
know.
F
Sometimes
you
use
these
kind
of
golden
files,
and
things
like
that
so,
like
maybe
there's
a
way
to
like
record
what
Network
requests
should
be
looking
at
kind
of
stop
it
out
in
a
way.
So
we
wouldn't
need
to
actually
do
the
actual
request
at
runtime.
That's
the.
C
Yeah
I
definitely
agree
to
some
extent
that
we
want
people
to
use
the
tools
that
they
are
used
to
using
I.
Think
it's
just
kind
of
a
hard
problem
here,
where
integration
tests
almost
always
are
going
to
flake,
sometimes
from
experience
I've
had
I
it's
it's
just
kind
of
the
nature
of
dealing
with
network
I
o
and
IO,
and
everything,
and
so
that
there
just
kind
of
needs
to
be
a
way
to
retry
these
tests
automatically
in
order
for
them
not
to
consistently
flake
on
us.
C
You
know
if
they
flake
and
then
the
next
try
runs.
Just
because
you
know
the
the
I
o
took
a
bit
too
long
and
the
timeout
happened,
then
that's
fine,
but
if
the
flake
is
constantly
causing
you
know
a
maintainer
or
the
pr
author
to
go
and
have
to
click
the
retry
button
that
just
gets
super
churning
over
time
and
I.
Think
that's
something
we've
experienced
with
the
kind
of
the
number
of
PRS
we
opened
recently.
C
Is
that
there's
a
whole
bunch
of
flakes
all
the
time
and
so
kind
of
having
something
that
generally
reduces.
The
number
of
flakes
is
I
think
important,
but
kind
of
on
the
using
two
tools.
Side,
I
think
that
it's
even
more
painful
if
someone
uses
one
tool
locally
and
then
pushes
up
to
the
pr
and
there's
a
small
difference.
There's
a
small
you
know
change
between
how
cargo
test
runs
a
test
versus
how
next
test
runs
the
test,
and
it
fails
because
of
that.
C
That
is
a
re
that
is
for
someone
who
doesn't
know
what's
going
on
with
test
Runners
doesn't
know,
you
know
our
testing
architecture
or
anything.
That's
a
super
painful
moment
where
you
know
I
I
can
see
a
new
contributor
being
like
this
is
too
much
I'm
just
going
to
close
the
pr
I,
don't
really
care
so
so
to
me.
I
think
that
yes,
there's
an
arguments
made
for
having
developers
use
which
tools
they
want
to
use,
but
I
think
there's
also
an
arguments
made
to
we
have
this
kind
of
testing
infrastructure.
C
We
have
these
requirements,
we
want
to
meet
and
we're
asking
the
maintainers
and
contributors
who
work
on
this
project
to
use
this
test
Runner.
It's
basically
money
kind
of
take
on
that
I
guess,
but
Brooks
had
it
his
hand
up.
A
Yeah
I
have
my
hand
up,
but
I
think
Frank
actually
beat
me
in
the
comments
Matt.
Do
you
want
to
read
that
one
out
loud
because
I
don't
think
it
propagates
everywhere
and
then
go
for
that?
One.
C
Yeah
sure
so
how
common
is
Nexus
usage
and
other
communities
projects
I
personally
haven't
seen
major
products
to
use
next
test
before,
however,
access
is
a
pretty
well-supported
project
from
what
I
can
tell
on
the
repo-
and
it's
been
around
for
quite
a
long
time
now.
C
C
C
Obviously
we
can't
you
know,
prescribe
you
know
infinite
usage
towards,
but
at
least
helps
us
kind
of
have
more
confidence
in
it.
A
So
my
hand
was
that
or
the
the
quick
thing
I
wanted
to
comment
on,
because
I
initially
had
an
idea.
I
was
like
you
know.
Maybe
we
use
regular
cargo
tests
for
unit
tests,
because
that
doesn't
really
change
much.
It's
quick
little
functionality
checks
and
then
we
use
next
tests
for
like
integration
things.
A
That's
in
CI,
it's
a
little
bit
more
involved,
but
I
definitely
understand
the
idea
that
having
two
different
things
like
may
make
one
use
case
a
little
bit
simpler,
but
still
when
you're
contributing
something,
if
you're
adding
a
unit
test,
then
you
have
to
go
down
that
boundary.
Anyways
I,
think
the
key
thing
from
from
my
perspective
is
anyone
who's
developing
wash
or
adding
a
adding
a
feature
to
wash
is
going
to
have
a
cargo
tool
chain
installed?
They
have
to
so
the
barrier
of
hey
run.
A
This
one
command
to
add
next
test
is
actually
not
not
as
huge
as
saying
like.
Oh,
by
the
way
we
depend
on
Java
to
run
our
test
like
make
sure
that
you
have
that
installed
and
I
I
think
the
key
with
with
whatever
tool
that
I'm
not
not
advocating
any
way
here,
just
so
that
we
can
keep
going
with
the
questions
and
everything
is
whatever
we
use.
A
If
we
have
a
make
test
Runner
or
something
similar,
let's
make
sure
to
keep
it
in
a
way
that
it's
really
easy
for
somebody
to
run
the
test
like
if
you're
running,
make
tests
in
the
wash
repo
for
the
first
time
we
require
next
test.
We
could
have
a
little
check
that
says:
oh
hey
next
test
is
an
installed
like.
Would
you
like
to
install
it
with
cargo
install
and
then
yes,
no,
and
then
they
can
just
continue
on
on
the
path
so.
C
C
This
is
the
the
command
to
install
the
install
the
runner
and
it
seems
to
work
fine,
at
least
on
my
machine.
So
sorry,
yeah
does
any
have
any
other
kind
of
thoughts
on
that.
G
If
anyone
feels
like
if
they
were
coming
to
this
project,
this
would
discourage
them
from
from
contributing
that's
what
I
really
want
to
know
like
I
I,
think
the
installation
of
everything's,
simple
enough,
but
I
just
want
to
know
if,
if
anyone
feels
that
way,
let
us
know,
but
if
not
I,
if
no
one
feels
that
way.
Right
here
and
I
think
this
is
a
safe
enough
thing.
G
F
F
Write
a
question
of
how
difficult
will
it
be
to
remove
the
need
for
serial
testing
because,
like
we
could
have?
If
this
is
typical
of
the
file
system,
then
it
could
have
you
know
per
test
a
temporary
directory,
maybe
with
some
environment
variables
because
specify
whatever?
What
is
it?
What
why
is
serial
tests
required?
Because
that's
that's
actually
the
only
thing
which
prevents
cargo
next.
C
As
the
cargo
test
to
coexist
correct,
it's
it's
one
of
the
problems.
It's
the
most
obvious
problem,
at
least
for
our
use
case.
I
haven't
identified
another
problem
yet,
but
I
would
say
that
you
know
there
are
two
different
test:
Runners
I
I
think
there
there
would
be
another
problem
and
I
can't.
We
can't
be
sure
if
it's
not
so
that's
kind
of
my
argument,
but
on
the
on
the
kind
of
how
to
disable
the
serial
test.
I
think
that's
that's
something
I,
don't
I!
C
Don't
I'd
have
to
look
at
the
code,
smart
and
figure
out
exactly
why
we
added
those
serial
tests
in
the
first
place,
my
guess
it's
with,
especially
with
the
up
tests
it's
to
do
with
running
the
binary
and
and
adding
it
to
that
port
on
the
machine.
C
So
we'd
have,
to
kind
of
you
know,
split
each
test
into
like
a
darker
container,
Actually
I,
don't
even
know
if
that
would
work
it
might,
but
yeah
there's
there's
some
ideas
of
how
we
might
be
able
to
split
them
up,
but
it
would
require
a
pretty
heavy
segmentation
of
each
test
into
kind
of
a
Docker
container
or
another
machine
or
something
to
stop
them
from
like
overlapping.
On
the
same
floor,
it's
that
kind
of
thing.
F
Okay,
well,
I
have,
from
my
experience,
I've
run
next
test
very
successfully
in
CI,
alongside
cargo
tests,
without
any
issues.
So
one
problem,
for
example,
was
requiring
carbon
next
test,
for
example,
would
be,
let's
say,
packaging
of
wash
rest.
So
if
any
kind
of
package
spec
recipe,
you
would
want
to
also
run
tests.
On
the
back
of
here,
we
install
this
custom
next
test
and
then
customize
their
testing
procedure
of
the
package
and
I
say
that's
not
ideal.
F
A
Yeah
I
don't
mean
to
don't
mean
to
cut
you
off
there,
but
that's
a
good
thing
to
that's
another
thing:
good
thing
to
keep
in
mind:
dang
it
I
had
a
oh
all,
I
was
gonna,
say,
is
I
I,
think
identifying
that
serial
tests
are
run
differently
and
that
we
only
have
a
few
of
them.
A
You
know
is
that's
that's
one
piece
and
it
you
know
it
works
differently
between
cargo
and
next
test,
but
I
agree
with
I
think
the
sentiment
from
Matt
and
Roman
that
we
should
kind
of
take
a
look
at
some
of
these
tests
that
we're
running
differently
and
see
if
we
can
actually
just
improve
the
test
themselves,
because,
no
matter
what
we're,
what
tool
we're
using
it
would
be
great
to
be
able
to
run
them
in
in
parallel.
That
would
speed
things
up.
A
It
probably,
and
you
know,
I
I
wrote
some
of
the
integration
tests
for
up
I,
think
you're,
probably
right,
Matt
that
it's
just
like.
We
tried
downloading
a
couple
of
binaries
and
we
may
just
be
using
the
pre-assumed
path
or
something
like
that,
like
those
things
would
be
great,
like
Fast
follow
tasks
for
any
kind
of
changes
for
for
our
testing
Suite.
H
And
it
sounds
like
we're
all
okay
with
requiring
next
test.
Now
now
it's
also
like
hey.
Can
we
also
fix
some
of
these
other
issues,
too?
Is
that's
kind
of
what
I'm
hearing
it's
it's
a
it's
a.
Why
not
both
and
can
we
iterate
and
make
it
better
question.
A
Yeah,
my
my
vote
would
be
that
adding
a
utility
tool
to
make
tests
better
as
long
as
it
doesn't.
You
know
that
that's
not
something
that
we
have
to
include
in
the
wash
final
binary
or
anything
I'm
interested
Roman.
Maybe
we
can
take
the
thread
offline
or
something
into
the
Watson
Cloud
slack
about
different
package
managers
running
the
tests
as
well,
because
I
would
want
to
keep
itself
contained
to
something
that
that
we
do
but
yeah.
My
my
vote
would
be
to
proceed
with
with
this.
F
Say
if
you
had
to
run
cargo
Miri,
then,
when
you're
a
Miri,
you
basically
get
this
thing,
which
you
can
specify
we
could
match
upon
right
and
whether
enable
serial
or
not
so
couldn't
be
just
the
same
way
detected
cargo.
Next,
we're
running
with
div
card
with
next
test,
environment
and
cargo.
Next
test
environment.
Do
not
not
at
the
serial
directive
but
outside
cargo.
Next
environment
do
add
the
cereal
is
there
something
I
mean.
C
Yeah
I
mean
I'm
not
totally
for
Mary
is
to
be
honest,
but
I
I
do
I
would
be
pretty
kind
of
like
worried,
I
guess
about
kind
of
adding
in
code
definitions,
kind
of
in,
like
a
in
a
code.
Gen
manner
like
that.
I
just
think
that
the
the
pain
of
a
cause,
if
it
does
break,
is
kind
of
is
higher
than
the
the
the
benefit
we
get.
C
But
that
again
that's
that's
just
my
kind
of
you
know:
I'm
I'm,
someone
who's
super
hesitant
to
use
macros,
I
I,
really
don't
like
when
code
doesn't
tell
me
what
it
does,
but
if,
if
that
is
something
that
you
know
kind
of
the
community
and
agrees
on
that,
that's
the
best
way
to
go,
then
I'm
I'm
game
for
it.
A
Sounds
good
well
and
Matt.
Thank
you
so
much
for
doing
the
the
demo
of
putting
up
the
pr-
and
you
know
to
walking
us
through
this
stuff,
I
think
we've
got
maybe
one
or
two
follow-ups,
but
I'll
go
back
in
and
drop
a
review.
Actually
do
you
want
to
show
it
working
I,
don't
even
know
if
you
do
that
earlier,
yeah.
C
C
A
All
right,
thank
you
very
much.
I'm
gonna,
I'm
gonna
share
I'm
gonna
share
my
screen
here,
just
a
second,
so
the
next
thing
that
I
wanted
to
talk
about
I'm,
actually
kind
of
doing
a
a
slight
demo
as
a
stand-in
for
one
of
the
new
contributors
that
we
had.
Victor
Victor
works
at
victorworks
at
cosmonic,
but
he
has
been
putting
in
a
couple
things
into
wasmcloud
and
and
wash
over
the
last
few
days
and
I
actually
didn't
ask
him.
A
If
I
can
do
this
or
if
I
should
do
this
so
ask
for
for
forgiveness,
I
guess:
thanks
Victor
I
I
just
wanted
to
show
off
one
of
the
one
of
the
cooler
things:
that's
really
great:
quality
of
life
Improvement
to
the
watsonpot
dashboard.
So
there
are
a
couple
things
in
the
actual
dashboard
like
when
you,
when
you
go
through
the
happy
path
of
of
starting
an
actor
Everything
feels
kind
of
nice
like
we
we're
downloading
actor
bites.
Okay,.
A
Thanks
Matt
talk
to
you
later
so
there's
following
the
happy
path.
Things
are
things
are
pretty
great.
You
go
through
operations,
you
can
you
can
change
your
scaling
up,
webassembly
modules,
all
that
stuff.
However,
there
are
some,
let's
say,
room
for
improvement,
around
error
handling
in
the
washboard.
A
So
if
you
come
in
and
you
actually
type
in
like
a
bogus
oci
reference
to
download
onto
your
host,
that
kind
of
goes
through
the
same
path
as
the
happy
path,
but
obviously
that's
not
going
to
be
an
oci
reference
that
it
can
download
from
and
if
you
come
to,
the
actual
logs
of
the
of
the
Watson
host
I
know
red
on
black
can
be
kind
of
hard
to
read
on
screen
share,
but
you'll
see
the
actual
issue
here
in
the
console
and
now
what
would
be
really
nice
from
a
dashboard
management
perspective
is
to
actually
either
see
those
logs
or
get
the
immediate
feedback,
and
that's
something
that
Victor
actually
went
through
on
starting
a
provider
from
a
file
so
another
similar
case.
A
You
can't
just
upload
like
a
500
gigabyte
file
into
wasmcloud
and
if
I
show
you
I'm
just
going
to
actually
show
you
something
like
I
I,
compress
something
into
like
a
500
Meg
archive,
which
is
above
our
limit
and
what
Victor
actually
added
here
is
as
soon
as
you
do
this,
we
pop
up
a
little
error,
a
little
error,
not
toast,
but
I'm,
forgetting
like
the
UI
word,
pop-up,
whatever
and-
and
it
actually
lets
you
know
what's
going
wrong
and
I
know
that
this
kind
of
seems
like
table
Stakes
for
a
dashboard
and
I
just
really
appreciate
Victor
for
coming
in
and
seeing
this
friction
while
he
was
doing
some
developing
and
then
adding
this
to
the
dashboard,
so
I
think
there's
a
good
bit
of
quality
of
life.
A
A
Also
consider
doing
things
like
having
actual
logs
in
the
in
the
UI
here
as
a
tab,
but
having
that
right
in
the
modal
is
actually
probably
one
of
the
better
experiences
just
for
from
the
immediate
feedback
perspective
I
saw
I
saw
we
had
a
chat,
oh
okay,
this
was
from
the
stream
I'll
stop
I'll,
stop
sharing
I'm
happy
to
take
any
actually.
Why
don't
I
get
to
that
in
a
second?
Does
anybody
have
any
questions
on
the
on
the
dashboard
error,
handling
that
I'm
showing
off
on
behalf
of
Victor.
A
Okay,
great,
that
was
just
meant
to
be
a
quick
demo,
a
little
preview
of
what
we
have
coming
in
a
couple
other
places
as
well,
but
Bailey.
Thank
you
for
actually
keeping
an
eye
on
one
of
the
other
live
streams.
We
had
a
question
on
Twitch
about.
Why
not
run
then
I
assume
the
like
the
integration
tests
on
random,
separate
ports
via
Auto
determination
and
that's
a
that's
a
great
idea.
We
actually
do
in
some
of
our
integration
tests.
We
we
pick
different
ports
like
for
Nats
connections
and
Blossom.
A
Cloud
dashboard,
listen,
ports,
things
like
that
to
to
not
conflict
on
ports.
We
certainly
have
the
ability
to
do
that,
and
it's
a
great
thing
to
to
keep
in
mind.
If
we
have
anything,
that's
it's
poor
contention
in
terms
of
running
those
tests
in
an
async
or
a
parallel
manner.
We
certainly
take
a
look
at
that.
A
A
Please
throw
a
few
more
in
if
you,
if
you've
got
them
all
right
well,
moving
on
from
the
the
demo
section
I
think
I
would
actually
like
to
transition
over
to
transition
over
to
Taylor
Taylor
wrote
up
a
great
Autumn
RFC
and
that
we
talked
about
in
the
community
call
last
week
and
there's
been
some
questions
and
comments
and
feedback
on
that
PR
I
would
love
to
just
kind
of
give
us
some
time
to
discuss
that
and,
furthermore,
kind
of
do
another
call
out
that
this
RFC
is
open
for
anybody's
feedback
from
the
community.
A
You
don't
have
to
be:
don't
have
to
be
someone
who's
contributed
before
any
any
experience
is
appreciated.
A
Taylor.
Would
you
like
to
go
ahead
and
take
a
look
at
your
your
wadham
RFC
yeah.
G
So
bricks,
if
you
go
ahead
and
Link
that
in
the
chat
and
then
send
it
out
to
Bailey
for
the
other,
chats
Bailey
also
had
a
question
that
she
put
in
there
from
one
of
the
channels,
I
think
and
I'm,
going
to
answer
that
real
quick
about
integrating
I'm
assuming
the
question
was
any
plans,
slash
needs
for
integration
with
grafana
tempo
for
the
otel
tracing,
and
then
they
said
they
were
assuming
that
it's
meant
to
be
separate
by
Design
use
case.
Thought
I,
thought
I'd
ask
the
answer.
G
That
question
is
yes,
we
already
actually
have
if
you
look
in
the
hotel
folder,
just
a
quick
like
Docker,
compose
file
to
quickly
spin
Up
Tempo
and
all
that
and
run
it
alongside
your
running
host.
So
that's
there.
G
But
yes,
they
are
supposed
to
be
separate
by
Design,
so
you
can
hook
it
up
to
anything
you
want,
but
yeah.
There
is
something
basic
included
using
grafana
and
Tempo,
so
you
can
just
get
an
essential
the
essentials
view
of
what
you
need
so
good
question
from
from
YouTube
there.
Okay.
So
we
have
this
RFC,
which
I
talked
a
little
bit
about
last
week.
I'm
not
going
to
go
into
depth
about
it,
but
there's
been
some
additional
discussion
around
how
we
should
build
the
the
Locking
and
distributing
the
work.
G
There's
a
nice
diagram
right
there.
Thank
you.
Bricks
from
Kevin
and
I
I
had
a
little
bit
of
offline
conversation
with
Kevin
to
kind
of
discuss
over
some
things.
I
was
going
to
summarize
it
here.
I
haven't
done
it
yet
I'm
I'm
working
through
a
backlog
of
stuff
this
morning,
but
essentially
what
I'm
going
to
propose
we
do
is
we're
going
to
start
with
a
spike
to
see
how
easy
this
is.
G
What
what
Kevin
and
I
were
talking
about
was
trying
to
make
sure
we
avoid
any
like
too
much
complexity
up
front,
and
when
we
talked
about
it,
we
decided
it'd
be
good
to
at
least
try
this
as
like
the
the
straw
man
type
of
things
that
just
start
up
with
something
that's
passing
through
events.
It
doesn't
have
to
actually
do
anything
with
the
logic
just
seeing
how
it
works
and
how
it
works
in
parallel
to
use
it
with
this.
G
So
that's
something
we
can
do
as
a
quick
Spike
and
if
it
looks
like
it's
just
going
to
be
over
the
top
complex
or
just
too
much
to
try
to
do
as
a
first
pass,
we'll
we'll
revert
back
to
a
slightly
modified
version
of
what
I
proposed
of
having
just
a
single
leader,
election,
lock
and
but
it
will
use
an
incoming,
durable,
Stream
So
that
way,
you're
always
making
sure
we
have
a
constant
state
and
state
stored
in
a
durable
store
as
well.
G
So
that's
the
only
thing
that's
changed
here,
but
I
really
want
to
make
sure
that
if
there's
any
other
thoughts
on
not
just
this
stuff,
but
everything
else
in
the
RFC
that
people
have
time
to
look
at
it.
I'm
hoping
to
try
to
get
this
merged
and
approved
or
I
should
say
approved
by
the
end
of
the
end
of
the
week.
G
It'll
stay
open
until
we
actually
like
Implement
everything,
or
at
least
I,
get
everything
into
the
GitHub
projects
and
stuff
that
we
want
to
do
so
that
we
can
keep
track
of
the
work.
But
I
want
to
just
call
that
out
one
more
time.
So
people
can
come
back
and
and
add
any
more
comments
they
they
want
to
do
so.
Yeah,
there's
the
comments
kind
of
like
stopped
towards
the
end
of
the
week,
so
these
are
more
yeah.
We
just
had
a
few
more
comments
on
there
and
whatnot.
G
So
anyway,
we're
going
to
go
ahead
and
just
look
for
any
more
additional
feedback.
If
people
have
it
and
then
we'll
try
to
get
started
on
this
as
soon
as
we
can,
that's
all
I
had.
A
H
Well,
there's
a
lot
of
discussion
there,
and
so
are
you
saying
Taylor
that
in
the
the
body
of
the
original
proposal,
that's
the
one
that
you
were
gonna
Spike
on
first
to
see
how
difficult
it
is
to
implement
no.
G
I'm
gonna
Spike
on
the
one
that
Kevin
suggested
and
then
revert
back
to
a
slightly
modified
version.
I'm
going
to
drop
a
comment.
I
realized
I,
never
sent
a
comment
to
one
of
those.
The
last
things
that
was
going
on,
but
also
I,
I'm
gonna
drop
a
comment
with
all
that
in
there
I
was
just
working
back
through
my
backlog
of
stuff
to
to
do,
but
I'm
just
spitting
it
out
here.
While,
while
we
are
here
that,
if
anyone
has
any
more
comments,.
G
H
Yeah
and
since
since
we
do
have
some
like
new
members
to
the
community,
you
might
want
to,
can
you
give
a
tldr
for
what
what
dam
is
and
maybe
how
that
could
relate
to
like
something
they
already
know
like
in
the
kubernetes
ecosystem?.
G
Well,
yeah
I
know
both
so
like,
like
what
is
a
damn
in
comparison
like
what's
the
so,
for
people
who
aren't
familiar
with
what
would
dam
is.
It
stands
for
awesome,
Cloud
deployment
manager,
that's
where
the
name
comes
from,
and
we
are
the
the
closest
analog
and
it's
not
a
one-to-one
relationship.
So
just
be.
Thank
you.
Thank
you
bricks.
So
the
one
of
the
big
things
that
we're
we're
looking
to
do
is
say
like
well.
We
need
a
man
like
declarative
State,
like
a
declarative
thing.
G
I
want
to
be
able
to
have
this
application
running
with
these
things,
so
the
closest
thing
is
like
a
kubernetes
deployment.
What
happens
with
that?
So
you,
you
say,
like
here's,
my
here's.
My
containers
in
my
pod
I
want
this
number
of
PODS
I
want
it
spread
across
these
things,
and
so
that
is
the
closest
analog
in
the
kubernetes
space.
G
It's
a
little
bit
different
in
how
it
works
here,
but
that's
kind
of
the
idea
of
of
where
it's
coming
from
is
that
people
want
something
that's
declarative
that
they
can
use
to
and
and
then
also
they
can
keep
applications
running.
But
as
a
reminder,
what
am
supposed
to
be
a
basically
canonical
implementation
of
how
to
run
one
of
these
things?
G
It
does
not
preclude
people
from
building
their
own
and
hopefully
they'll,
be
able
to
even
reuse
some
of
the
same
components
when
this
is
said
and
done
it's
just
that
this
is
the
canonical
one,
because
this
is
the
core
use
case
that
most
people
are
going
to
want
to
do
and
I
try
to
account
for
also
being
able
to
extend
it
with
custom
scheduling
types
in
the
future.
It's
not
going
to
be
part
of
the
first
draft,
but
I
wanted
to
call
out.
So
people
knew
that
that
was
a
design
goal
in
the
future.
A
Sounds
good,
so
Taylor
I,
guess
I'm
wondering.
Is
there
like
an
end
date
for
this
RFC
I
know
rfcs,
don't
have
to
have
a
specific
deadline
or
timeline,
but
do
you
feel
like
it's
getting
to
a
point
where,
like
by
the
next
or
by
the
next
Community,
call
Will
kind
of
close
it
and
start
opening
up
like
specific
tasks
to
get
this
done?
I'm.
G
Hoping
by
next
Community
call
I
have
actually
created
all
the
tasks
and
stuff
the
RFC
I'm,
hoping
to
scope
this
somewhat
within
around
a
six
week
period
roughly,
and
so
it
all
just
depends
on
community
feedback
and
how
we
Implement
things
I'm
trying
to
get
like
some
of
the
stuff
like
spiking
out
on
that
design
pattern
is
something
I
should
probably
do,
because
I
have
the
most
context
but
I'm
trying
after
that,
to
make
sure
there's
as
much
that
we
can
separate
out
an
individual
tasks.
G
So
anyone
who's
interested
in
the
community
to
to
like
want
to
help,
they
can
say,
like
oh
I,
want
this
task.
So
that's
going
to
be.
My
goal
is
to
try
to
create
as
many
discrete
tasks
as
possible
and
then
we'll
just
work
on
it
till
it's
done.
A
All
right
well,
that
sounds
like
a
pretty
pretty
solid
conclusion
to
that
section.
If
you
have
any
other
questions,
please
feel
free
to
hop
into
our
community
slack
and
we're.
We
are
active
all
the
time
so
happy
to
you
know,
happy
to
get
that
started
looks
like
we
actually
had
another
new
Community
member
join
the
call
about
halfway
through
hey
Chuck,
good,
to
good,
to
see
you
sorry
to
hey
how's
it
going
good
good.
A
I'm
gonna
put
you
on
the
spot
a
little
bit
here,
but
please
feel
free
to
say
no,
we
usually
let
people
do
an
introduction
in
the
in
the
call.
Would
you
like
to
do
one
and
talk
about
kind
of
what
you
do
and
what
you
work
on.
I
Oh
I'm,
new
I've
been
I've,
been
wanting
to
jump
on
in
one
of
these
for
a
while
we're
we
we've
got
a
legacy
platform
and
we
looking
at
modernizing
it
and
I've
been
interested
in
looking
at
possibly
using
this
technology.
I
need
to
learn
more
about
it.
A
Well
with
that
I
think
that
that's
all
that
we
had
on
our
published
agenda
for
today,
so
we'll
go
ahead
and
transition
into
free
time.
Now
is
a
great
chance
to
bring
up
anything
that
you've
seen
happen
in
the
awesome,
Cloud
world
or
just
general
wasm
ecosystem,
and
this
is
totally
open
floor.
So
anybody
just
raise
your
hand
or
speak
up
if
you
like
to
bring
up
something
or
ask
a
question.
H
I
want
to
put
up
all
the
events
that
are
coming
up,
because
there
are
so
many,
so
you
know
we
ran
a
bike.
Coat
of
line
or
I
I
was
the
the
host
for
the
bicode
alliance
stream
last
night.
So
we
do
that
monthly.
So,
if
you're
interested
in
updates
across
the
like
by
code
Alliance,
which
is
non-profit
grouping
of
a
bunch
of
different
software
folks
in
the
industry-
oh
no
there's
my
face.
Please
don't
hit
play.
H
If
I
hear
myself
I'm
gonna
like
dive
under
my
desk
but
yeah.
We
we
just
got
updates
across
a
lot
of
those
key
projects
and
a
lot
of
those
projects
also
integrate
and
influence
a
lot
of
the
things
that
we
do
within
miles
and
Cloud,
mainly
because
a
lot
of
the
first
implementations
of
the
standards
show
up
here
and
then
we'll
on
our
side,
try
to
leverage
those
and
expose
them
in
our
own
way
too,
within
lots
of
cloud.
H
So
that's
the
community
stream
there
it's
kind
of
similar
to
this,
but
at
a
monthly
Cadence.
The
next
conference
I
believe
is
was
scale
for
Brooks
and
Taylor.
Is
that
right?
Yeah?
You
guys
want
to
say
something
about
it.
Yeah.
G
Sure,
exciting,
Brooks
and
I
are
well
Brooks
and
I
are
giving
a
talk
together
then
I'm,
giving
a
talk
as
part
of
kubernetes
community,
so
Cloud
native
track
on
Saturday,
Brooks
and
I
are
giving
a
talk
around
how
easy
it
is
to
just
get
started
with
webassembly
now
and
then
on.
G
I
think
it's
third
Friday
for
me:
I'm
doing
the
career
next
Community,
Day
and
I
personally
liked
the
title
and
it's
a
recovering
kubernetes
Engineers
perspective
on
Watson
Cloud,
as
many
of
you
who've
been
in
this
community
for
a
while
know,
I
was
very
very
involved
in
the
kubernetes
community
for
a
long
time,
so
I
think
I
have
some
interesting
opinions
and
ideas
that
I
can
share
through
through
that
talk.
G
So
I'm
going
to
be
talking
about
that
I
think
all
of
these
are
going
to
be
recorded
and
streamed
out.
At
least
the
kcd
one
is
I'm
not
sure
about
the
the
scale
stuff.
It's
all
co-located.
If
you're
in
the
Southern
California
area,
it's
in
Pasadena
and
the
tickets
are
like
20
bucks
or
90
bucks
or
something
so
it's
not
expensive.
G
So
please
feel
free
to
stop
by
we'll,
be
there
we'll
be
around
to
to
talk
and
to
discuss
whatever
you
want
to
around
webassembly.
The
standards
was
in
Cloud
cosmotic.
Whatever
you
want
to
talk
about,
so
please
feel
free
to
stop
by
and
see
us
there.
We
add
that
is
coming
up
in
just
basically
not
this
week
but
next
week.
So
we
look
forward
to
seeing
some
people
there.
H
And
then
three
weeks
from
now
I
think
the
next
thing
is
wazam
IO,
that's
in
Barcelona,
Taylor
and
I
will
be
there
we'll
be.
You
know
doing
a
crash
course
on
wasmcloud
I
will
also
be
talking
about
standards,
because
I
sit
on
the
technical
steering
committee
for
the
by
code.
H
Alliance
and
one
of
the
some
of
the
new
standards
that
are
coming
up
are
basically
our
equivalent
of
capability
contracts
and
interfaces,
so
that
one
is
about
lazy
cloud
and
that'll
be
on
the
24th
and
I'm
doing
that
with
Microsoft
engineer,
which
should
be
super
fun,
so
that
is
lazomio
and
then
I
feel
like
there's
so
many,
but
an
MMA
will
have
keepcon
and
Blossom
Day
Kevin
Hoffman
is
speaking
kubecon
and
a
handful
of
us
are
talking
at
wasm
day,
most
likely
well
at
least
definitely
be
there.
H
So
I'm,
not
sure
Liam.
Last
Monday
is
largely
one
of
the
main
events
that
you
run.
You
want
to
talk.
D
About
you
know,
it's
a
it's
a
committee
of
us
that
pull
it
together
and
work
really
hard
to
make
it
happen.
We're
hoping
we've
got
a
draft
schedule
pulled
together
and
we're
hoping
to
finalize
it
in
the
next
couple
days.
We've
just
got
a
couple
of
final
selections
to
make
on
the
schedule.
I'm
super
excited
about
the
content
and
the
talks.
We've
got
a
great
lineup
and
there's
a
new
format
this
year
for
all
the
days
for
kubecon,
there's
an
extended
ticket
that
gets
you
access
to
all
the
days.
D
The
caveat
is:
is
the
extended
tickets
are
going
to
sell
out
this
week?
There'll
be
no
more
access
after
that,
so
they're
almost
sold
out
already
they
at
their
current
rate,
they
should
sell
out
by
the
end
of
the
week
now.
So,
if
you're
heading
to
kubecon
now,
not
only
do
you
get
a
discount
by
buying
now,
but
you
also
get
you
know,
there's
a
limited.
H
Number
of
availabilities
on
the
venue
cool
off
the
top
of
my
head:
that's
the
ones
that
I'm
thinking
about
I
know,
there's
a
handful
more
so
awesome.
H
That's
further
out
I
have
to
think
about.
You
know
now.
Next
later,
that's
a
later,
that's
in
the
later
category.
For
me,
but
yeah
that
one's
gonna
be
awesome,
that's
gonna
be
in
London
it's
going
to
be
situated
next
to
the
webassembly
community
group
and
from
what
I
understand
you
know,
cfp's
already
closed
and
they've
already
selected.
Some
speakers
I
think
their
session
list
is
now
published
and
there's
a
lot
of
good
stuff.
There,
too.
A
Yeah,
thank
you.
Bailey
for
kind
of
running
that
down
I
know
we're
gonna
have
to
keep
like
hubbing
things,
there's
so
many
so
many
events
coming
up
soon,
so
many
I
think
we've
submitted
for
a
lot
of
things.
So
the
the
cfp
storm
is
at
least
subsiding
for
now,
but
you
know
so
many
so
many
things
yeah.
H
I
feel
like
the
worst
thing
ever
would
be
that
we
forgot
to
do
it
one
time
and
like
tailor
you
or
somebody
in
our
community
is
going
to
be
in
somebody's
neighborhood
and
we
miss
an
opportunity.
So
just
gotta
keep
bringing
it
up
so
that
we
can
communicate
together
in
person
every
whenever
we
can
online's
cool
too.
D
D
Again
and
the
videos
cosmonic
is
the
sponsor
this
year
again
of
the
videos,
so
they
should
be
available
online,
almost
immediately
after
playing
if
you're
not
live
I.
Think
last
last
year
it
was
a
week
I
wish.
I
could
tell
you.
I
know
that,
based
on
the
production
company
they
use.
Sometimes
it's
taken.
You
know
a
week
before
they're
available.
Sometimes
it
was
like
a
month
so
I
just
don't
I,
don't
know
what
to
tell
you
as
far
as
anticipation
to
get.
H
Chuck
can
I
ask
when
you
say
an
edge
server.
Do
you
mind
qualifying
that
a
little
bit
more.
I
Yeah
we
have
small,
we
have
these
servers
that
Connect
into
Hardware
Network
sensors
that
sit
inside
industrial
control
system
very
deep,
like
right
in
front
of
plc's
in
an
industrial
control
system,
and
it's
it's
a
it's
a
legacy,
architecture,
they're,
basically
Debbie
in
boxes-
and
we
were
we
were
discussing.
I
You
know
moving
into
the
2010s,
at
least
in
our
15.
and
maybe
maybe
going
for
some
sort
of
kubernetes
type
system
they're
these.
Basically
these
are
kind
of
pseudo
air
gapped.
So
they
it's
gonna
change
a
little
bit,
but
they
don't
really.
I
They
can't
really
talk
to
the
internet,
but
they
kind
of
can
they're
kind
of
isolated
and
they're
they're
difficult
to
maintain.
Basically,
and
so
that
was
one
of
the
concepts
was
made,
possibly
seeing
what
we
could
do
in
terms
of
moving
towards
using
wasm
in
in
a
form
it
would
work.
Chuck.
D
I
Yeah
we're
actually
shipping
Zeke
data
and
it's
going
into
a
mongodb
in
a
proprietary.
It's
a
system
for
PLC
Engineers
to
see
what's
going
on
in
there,
and
it
can
control
these
little
things
that
they
actually
block
can
block
things
in
the
block.
I
A
network
activity
in
the
in
the
really
low
in
the
Purdue
model
like
about
layer,
one
okay,
and
then
they
extend
over
into
sensors
that
Connect
into
the
serial
connections
and
right
now,
they're
difficult
to
update
and
some
of
them
reside
on
Maritime
ships
that
are
in
the
middle
of
the
ocean
across
of
low
bandwidth,
High,
latency
connections
and
stuff,
like
that.
So
an
immutable
infrastructure
is,
is
appealing
actually
especially.
I
Know
absolutely
yeah
scalability
and
the
ability
to
it
needs
to
be
secure.
We
need
to
be
able
to
update
it
and
maintain
it.
The
system
right
now
is
more
of
a
prototype.
I
would
say.
D
One
of
our
community
members
has
a
project
at
the
at
the
financial
institution.
He
works
at
where
he's
been
shipping
Logs,
with
with
Blossom
Cloud
and
okay
yeah
doing
so
securely.
So
that
might
be
a
PhD
that
you
guys
could
pick
up
and
look
at
I'll
I.
Have
your
contact
info
check,
I'll,
connect.
I
I
I
So
this
potentially
could
could
solve
a
lot
of
things
simultaneously.
I'd
like
to
learn
more
about
it.
A
H
Research
project,
that's
more
like
in
a
clinic
so
right,
you
know,
I.
H
Options
and
wasmcloud
is
really
just
like
one
of
the
easiest
ways
to
set
that
up.
I
feel
like
and
there's.
I
H
Lot
of
great
options
out
there
today,
that's
not
that
I.
I
Mean
we
were
just
discussing
the
merits
of
maybe
moving
towards
kubernetes
K3
I
guess
I
haven't
used
it
much,
but
it
looks
like
we.
We
absolutely
should
be
moving
that
direction,
but
I
wanna
explore
this
too.
Maybe
we
should
move
directly
in
this
direction,
so
it
just
depends
on
how
we
want
to
read
recreate
the
architecture
or
how
much
work
it's
going
to
be
to
do
that.
F
D
A
A
D
Well,
we
do
have
this
awesome
demo
coming
soon
around
build
it.
Your
yourself
SDR
project,
using
Wallace
and
Cloud,
so
I've
actually
got
it
running
right
here.
It's
been
running
for
a
couple
weeks
and
we're
working
on
the
installation
instructions,
so
humble
tease,
watch
for
that
coming
out
soon
be
fun
one
to
walk
through.
That
could
go
right
in
the
iot
channel
that
works.
A
Yeah
we'll
get
a
gill
iot
Channel
going
that'll,
be
fun
all
right.
Well,
I'm
gonna
go
ahead
and
stop
the
recording
stream.
Thank
you.
Everybody
for
coming
I'll
hang
out
for
a
couple
minutes
after
we
get
it
stopped
just
in
case.
We
want
to.