►
From YouTube: wasmCloud Community Meeting - 01 Feb 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
Okay,
welcome
everyone
to
the
wasm
cat.
Wasn't
Cloud
Community
call
for
February
1st.
Yes,
it
is
already
February,
so
congrats
we
made
it
through
January,
only
a
couple
more
months
of
freezing
for
the
Northern
Hemisphere
for
the
southern
hemisphere.
You
look
forward
to
the
freezing.
Okay,
so
welcome
to
this
call.
We
have
a
bunch
of
demos
today
that
are
going
to
be
pretty
exciting.
A
C
D
A
I
was
swapping
it
out
according
to
the
agenda,
so
anyway
there's
the
agenda.
So
people
know
what
I'm
following
Stephen
go
ahead:
okay,.
E
D
D
Yeah?
Okay,
so
something
I've
been
playing
with
recently?
Is
the
C4
Model
A
lot,
so
I
came
from
like
a
a
bit
of
a
mechanical
background
and
I
I
think
that
in
that
field
they
love
imparting
information
with
pictures,
so
I
got
a
little
used
to
that
and
I
was
really
excited
when
a
colleague
at
my
last
job
showed
me
this
model
and.
D
F
C
C
D
Awesome
so,
as
I
was
saying,
the
C4
model
is
something
a
colleague
shared
with
me
before
and
I'm
sure
many
people
probably
already
know
about
it,
but
it
really
excited
me
and
I
can
paste
the
URL
into
the
chat
after,
but
it's
basically
taking
the
like
a
uml,
drawing
which
I've
never
really
had
experience
with
to
a
level
where
it
can
vary,
the
Scopes
of
who
you
want
to
speak
to
so
be
able
to
address
different
stakeholders
in
your
business.
D
Better
and
there's
really
four
main
model
perspectives
that
that
you
can
look
at,
and
that
would
be
context
container
component
and
code,
and
it
allows
you
to
just
dive
into
your
app
a
little
bit
better.
So
the
context
might
focus
more
on
people.
D
The
relationships
the
container
will
be
looking
at
the
thing
like
how
people
interact
with
maybe
your
single
page
application
or
something
the
components
will
be
breaking
apart,
that
application
into
the
major
components
and
then
the
code
will
be
the
elements
of
those
components,
so
the
function
calls
and
interfaces
and
all
that
kind
of
stuff.
So
this
was
pretty
fun
to
play
with
I
just
tried
to
do
something
really
basic.
That
might
be
evident
for
Watson
cloud
and
you
can
start
to
dive
into
context.
D
So
maybe
at
the
context
level
you
have
like
you,
you,
your
application,
needs
certifications
or
you
have
different
people
relationships
that
need
to
be
managed,
and
then
you
could
dive
in
so
a
user
is
interacting
with
the
WASP
Cloud
application.
I
can
dive
in
a
little
bit
look
at
how
that
application
comes
together,
so
a
user
might
be
interacting
with
a
client
it
and
then
how
that
client
gets
through
and
gets
all
the
information
it
needs.
And
then
you
could
jump
in
a
little
bit
more
and
look
at
it
at
a
component
level.
D
D
See
the
major
parts
of
the
single
like
the
awesome,
Cloud
application
and
how
maybe
the
calls
are
happening
so
here
it
might
be
like
Watson
bus
rfpc.
That
should
be
shown
most
I
I
put
interfaces
here,
but
when
I
was
doing
some
more
research
after
I
think
they
were
supposed
to
be
in
the
code
section,
so
don't
mind
that,
then,
when
you
can
jump
into
the
code,
you
can
see
you
start
to
get
an
even
deeper
picture
of
how
the
application
looks
and
you're
not
tied
to
a
single
pers.
D
Like
four
perspectives,
you
can
create
as
many
perspectives
as
as
you
want,
but
I
I
personally
think
that
one
of
the
best
ways
to
impart
you
know
documentation
or
information
is
through
images
just
because
they're,
a
language,
agnostic
and
they're
pretty
easy
to
understand
if
they're
done
well.
D
All
of
this
was
created
with
a
yaml-like
Syntax
for
the
tool
that
I
was
using.
So
this
is
what
that
yaml
might
look
like
you
kind
of
specify
the
components
you
give
them
children
and
then
you
build
relationships
out
of
them
at
the
bottom.
D
So
you
can
see
like
from
this
element
to
that
element
and
you
can
build
out
this
application
and
what
was
really
exciting
for
me
with
this
tool,
was
that
it
can
export
to
HTML
so
My
Hope
after
this
is
to
be
able
to
Tinker
a
little
bit
with
embedding
this
in
maybe
some
documentation,
I
know
markdown.
Can
you
can
you
can
do
inline
HTML?
D
So
my
Hope
was
that
I
could
maybe
post
this
type
of
HTML
document
on
like
a
static
web
server
and
then
be
able
to
do
like
an
inline
iframe
in
my
docs,
and
maybe
someone
would
be
able
to
interact
with
it
that
way,
but
this
is
still
very
new
to
me.
I
just
was
very
excited
about
it
and
thought
I
would
share.
It
was
created
by
someone
named.
The
model
itself
was
created
by
someone
named
Simon,
Brown
and
yeah.
D
D
A
G
B
Cool
all
right,
so
in
good
fashion
of
forcing
as
much
go
into
wasm
Cloud
as
possible
and
Stewart
showed
us
this
way
back
when,
when
it
was
like
just
announced
on
Twitter
I
play
with
dagger,
because
recently
there
was
some
talking
slack
about
like
testing
actors,
and
it
was
a
good
point.
B
I
didn't
really
know
how
to
do
it
unit
test,
not
what
I'm
going
to
be
getting
into
I'm
more,
like
the
end-to-end
in
integration
test
topic
right
now,
I'm
also
working
on
a
way
to
like
mock
the
lattice
which
I'll
use
for
unit
tests.
Eventually.
B
So,
looking
at
the
the
terminal
here,
here's
kind
of
what
I've
done
the
module
that
I'm
testing
is
just
wash
new
Echo
actor
Straight
Out
of
the
Box
there's
nothing
special,
but
I
have
added
five
tests
to
it.
We're
gonna
build
it,
make
sure
it's
built,
we're
going
to
sign
it,
make
sure
it's
signed,
we're
going
to
inspect
it,
make
sure
it
has
HTTP
server
and
the
name
dartman,
which
is
the
name.
I
gave
it,
and
then
this
is
where
we
actually
get.
This
is
all
kind
of
blah.
B
This
is
where
we
get
kind
of
fun.
We're
actually
going
to
call
it
with
wash
call
and
that's
kind
of
the
code
I
have
pulled
up
here
and
what
we'll
see
is
right
now
up
to
this
point,
we're
actually
signing
the
module
inside
call,
because
we
have
not
oh
I
hate
that
that
function
is
there,
since
we
have
not
officialized
made
official
the
the
start
from
file
functionality
here
on
line,
13.
B
I
just
called
an
audible
and
we're
just
going
to
pull
in
the
actual
Echo
actor.
Eventually,
this
start
from
file
that
Patrick
gave
us
will
replace
this
so
anyway,
so
we're
going
to
start
the
provider
we're
going
to
then
call
it
with
this
call
right
here,
get
Echo
body,
derp
and.
A
Then
we're
actually
going
yes,
sir
sorry
interrupt.
Can
you
enhance
please
I'm
going
to
shout
enhance
at
the
screen
until
it
gets
bigger?
Oh.
A
B
Right
cool
since
you're
streaming,
I'm
trying
not
to
scroll
because
I'm
pretty
sure
there
are
secrets
hard-coded
in
here,
but
more
or
less
yes,
as
I
was
saying
right
here,
where
we
would
pick
up
the
module
s
wasm
and
start
it
with
the
file
as
soon
as
that
lands.
B
I
will
switch
these
out,
but
I'm
I'm
pulling
the
the
actor
we're
starting
it
we're
going
to
call
it
with
essentially
a
get
Echo,
no
query
string,
no
headers
derp
and
then
we're
going
to
check
to
make
sure
the
body
comes
back
with
the
byte
value
of
derp,
with
Echo
get
and
then
call
response.
So
we
run
it
look.
It
was
cached
ta-da.
So,
what's
really
cool
is
what
I've
done
essentially
is
a
call
test
on
the
actor
which
allows
me
to
do
some
sort
of
Santa
sanity.
B
Checking
of
you
know
that
it's
actually
functioning
and
as
a
bonus
down
a
little
further,
we
actually
tested
starting
and
stopping
it
inside
cosmonic
using
appropriate,
wash
contacts.
So
not
only
do
we
test,
you
know
the
functionality,
we're
actually
testing
to
make
sure
it
deploys
and
stops
appropriately.
B
So
the
only
reason
I
pursued
this
is
there
were
talks
of
the
challenges
of
testing
actors
and
while
unit
tests
are
a
little
hard
right
now,
because
we
can't
mock
Lawson
Cloud,
yet
I
know
rust.
I'm
talking
about
ghosts,
specifically
I
decided
to
take
it
from
a
different
angle
and
and
test.
B
You
know
integration
and
kind
of
end
to
end,
and
the
next
iteration
here
would
would
be
something
along
the
lines
of
start:
the
actor
start,
the
provider
link
it
and
then
the
full
end-to-end
test
would
be
curl
through
the
provider
and
and
whatnot
and
I
was
gonna
get
there,
but
I
ran
out
of
time.
So
yeah
are
there
any
questions.
B
Liam
says
enhance
it's
on
a
different
screen.
I
can't
see
the
chat.
A
Thanks
Jordan,
okay,
to
add
more
to
the
testing
mine
actually
has
to
do
with
testing
too
Jordan
and
I
are
gonna,
go
Rock'em,
sock'em
robots
in
the
ring
together
just
kidding.
Okay,
let
me
go
ahead
and
share
my
screen
and
yeah.
That's
exactly
what
I
was
thinking.
Man.
F
A
I
forgot,
I
didn't
have
the
screen
recording
thing
on
for
zoom
in
my
Mac
settings
to
give
me
10
seconds.
Hopefully,
I
don't
have
to
rejoin.
C
Well,
I'd
love
to
see
some
of
the
efforts
around
testing
people
have
like
gotten
further
along
in
scaling
their
wasable
Cloud
deployments.
I
think
this
is
a
very
natural
topic
to
sort
of
come
up.
A
Okay,
welcome
to
Mr
Blobby
tables.
Mr
Blobby
tables
is
a
new
actor
that
we
created
in
our
examples,
repo,
but
as
far
as
I
know,
it
is
the
first
quote-unquote
real
one.
We
also
just
added
a
cool
signing
one,
that's
also
a
real
application.
So
this
is.
This
is
a
real
actor
that
acts
as
a
file
server
that
basically
exposes
a
basic
HTTP
endpoint
that
can
take
a
file
and
then
store
it
in
anything
that
implements
The
Blob
store
contract.
A
We're
gonna
come
up
with
some
cool
demos.
For
this
soon,
where
we
submitted
a
wasm
cloud
talk
around
this
too
I
think
it
was
Blossom
Summit
for
for
this
one
that
will
have
some
pretty
cool
demos,
but
I
might
also
show
them
off
before
we
we
get
to
that
conference.
A
A
So
if
you
want
to
follow
this,
it's
all
in
here,
but
I
wanted
to
do
this
completely
from
scratch.
To
show
like
how
it
works
number
one
and
then
also
some
testing
things
around
it.
F
A
Sorry,
this
is
gonna,
be
a
little
bit
longer
demo
than
I
generally
like
to
do,
but
I'm
going
to
go
ahead
and
just
actually
run
through
the
example
here
with
I'm,
just
going
to
say
wash
up
I'm
going
to
do
this
straight
from
scratch,
so
that
I
can
show
people
like
exactly
how
easy
this
is
to
just
start
off
with
so
I
went
ahead
and
started
this
up
and
I'm
going
to
go
ahead
and
go
to
the
washboard.
A
So
people
can
see
me
doing
this,
but
you
can
start
this
up
pretty
easily
with
this
Command
right
here.
So
you
can
watch
control,
start
actor
and
so
I'm
going
to
just
do
this
right
over
here.
A
I'll
take
a
second
to
download
and
then
it'll
be
fine
and
then
I'm
going
to
go
ahead
and
Link
them
with
what
will
be
the
blob
store,
file
server
and
the
HTTP
server.
So
that
was
the
blob
store,
contract
I,
just
added
as
a
link
and
the
HTTP
server
that
I
just
started
and
then
I'm
going
to
go
ahead
and
start
up
the
the
two
different
providers
I
need.
So
this
is
blob
store
FS.
This
means
it's
going
to
treat
my
file
system
at
a
specific
path.
I
gave
it
as
like
a
blob
store.
A
This
could
be
S3
as
well
and
we're
working
on
polishing
up
some
stuff
that
we
were
doing
some
testing
and
found
some
bugs
we
wanted
to
fix,
but
that's
the
blob
store,
fs
and
then
yield
HTTP
server,
which
we
all
should
know
pretty
well
at
this
point
if
you've
been
in
the
Wildcat
community,
so
I
just
started
that
too,
and
so,
if
we
look
here,
we
have
everything's
spun
up.
A
A
Okay
you'll
see
they
got
okay
and
we
can
actually
see
inside
of
and
what's
this
actor's
ID
I
always
forget.
A
A
A
So
it
is
a
real
fully
like
there's
no
like
unwrapping
or
panicking
or
any
sort
of
things
going
on
in
the
code.
It's
actually
fully
error
handled
and
everything
inside
of
it.
So
hopefully
this
can
serve
as
a
good
example
for
people
who
want
to
build
like
a
fully
featured
application
from
the
get-go.
So.
A
C
Well,
I
think
Taylor
I'm,
sorry
to
jump
in
this
is
an
incredible
demo
that
you
just
sort
of
like
sandbag
the
lead
that
you
can
easily
move
across
any
compatible
blob
store.
So
that's
S3
or
like
the
the
Google
blob
store
it
can
operate
in
S3
mode
mimeo.
A
I'm
planning
on
doing
for
this
is
actually
using
it
with
vaults
to
store
encrypted
files.
So,
like
there's
so
many
different
things
you
can
do
here
that
are
that
are
really
cool.
But
the
other
thing
that
I
add
is
I,
wanted
to
kind
of
do
a
test
bed
for
integration,
testing
actors.
Unit
testing
actors
is
a
little
bit
more
difficult.
A
If
Jordan
manages
to
create
a
mocked
out,
lattice
that'll
make
it
a
little
bit
easier,
but
what
what
I
wanted
to
do
was
create
something
that
would
serve
as
a
scaffold
for
how
we
can
start
adding
this
into
wash,
and
so
what
I'm
about
to
show?
You
is
very
janky,
but
it
works
and
you
could
copy
it
and
use
the
same
thing
and
it's
going
to
kind
of
serve
as
a
template
for
adding
this
into
wash
and
being
able
to
test
any
sort
of
actor.
A
And
so
this
is
the
kind
of
thing
where
I
work
with
Jordan
and
we'll
figure
out,
because
because
dagger
is
a
product
we
don't
want
to
make.
Everyone
have
to
use
dagger,
though
that's
a
great
option
for
people
to
use
this
one
is
one
that
works
just
inside
of
like
GitHub
actions
or
any
think
you
can
run
a
unit
test
or
any
testing
pipeline.
F
A
What
this
looks
like
is
a
really
gnarly
thing
that
sets
up
all
like
the.
It
builds
your
actor
for
you.
It
makes
sure
that
the
the
links
and
everything
are
set
up,
but
then
it
actually
outside
of
that
kind
of
gross
part.
The
actually
doing
the
test
is
not
too
difficult.
We
have
a
thing
that'll
give
you
like,
like
you,
just
do
a
client
and
you
can
call
the
different
URLs
and
everything
that
it's
trying
to
do
just
like
you
would
write
any
test
and
rest
or
any
other
language.
A
So,
ideally,
this
is
going
to
be
actually
I'm
debating
whether
or
not
we
want
to
make
kind
of
like
a
super
lightweight
like
IDL.
That
says
you
can
do
this
call
or
if
it
just
passes
in
a
script,
that
you
can
do
I'm
still
working
through
that,
but
something
will
allow
you
to
call
it.
So
what
this
actually
looks
like
is
I
can
go
into
testing
and
let
me
go
ahead
and
fill
it
wash
real,
quick.
A
This
test
is
limited
to
be
one
thread
at
a
time
just
because
I
didn't
want
to
have
to
figure
out
starting
up
multiple
washes
simultaneously,
but
you
can
go
ahead
and
run
this
and
you'll
see
that
it
compiles
the
actor
and
make
sure
it's
all
ready
to
go.
It
starts
wasn't
platforming
in
the
background
and
then
it
goes
ahead
and
starts
all
the
different
providers
and
then
it'll
run
the
tests,
and
so,
as.
F
A
C
C
Of
this
demo
is
the
is
the
sweet,
emojis
Taylor.
Oh.
A
F
A
Just
this
can
happen
sometimes
when
I
was
testing
with
another
awesome
Cloud
host
so
anyway,
this
runs
these
tests
and
actually
make
sure
that,
like
it
goes
through
each
of
the
things
it
can
upload
a
file,
it
can
delete
it.
It's
trying
to
do
all
the
different
things
and
also
shout
out
to
someone
from
YouTube
who
just
said:
they'd
use
little
Blobby
tables
yesterday
without
any
hiccups.
A
So
that's
great
to
hear
so
anyway,
the
like
I
said
this
is
janky
totally
is
but
I'm
I
I
think
it's
a
good
place
to
start
from,
so
that
we
can
add
this
to
wash
and
I
really
want
to
show
everyone
the
community,
what
we're
trying
to
do,
because
this
has
been
kind
of
a
thorn
in
our
side
for
a
while
we're
like
how
do
we
test
these
things,
because
it's
a
little
bit
hard
inside
the
wasm
space
to
actually
run
a
unit
test,
and
then
there's
like
the
lattice
and
different
things
so
like?
A
So
anyway,
that's
what
we
have
mostly
terminal
demo,
nothing
super,
exciting
and
flashy,
but
I
think
something
that
shows
a
pretty
good
set
for
it
and
we're
going
to
try
to
be
doing
more
examples
that
are
very
concrete,
real
world
things
you
can
actually
use.
So
you
have
better
things
to
copy
paste
from
when
you
start
and
are
learning
laws
of
cloud.
G
G
I
want
to
pull
a
Liam
here,
I'm
just
going
to
say
what
you
just
said,
but
again
in
high
level
terms.
I
can
take
the
actor
that
you
created
little
Blobby
tables
and
it
can
be
my
basically
crud
actor.
My
crud
app
for
dealing
with
any
kind
of
blob,
so
I
can
have
a
thing.
That's
doing
a
file
server.
What
you
demoed
I
can
have
it
connected
to
S3
I
can
have
it
connected
to
Vault
just
about
anything
without
ever
changing
that
actor
and
changing
any
of
its
code.
G
So
when
I
do
that,
and
it's
something
really
that
I
could
add
to
my
sack
like
this
is
like
a
thing
that
I
could
just
pick
up
and
plug
in
and
then
I
can
have
a
different
actor
call.
This
actor
called
little
Blobby
tables
and
it
will
I
don't
have
to
write
any
of
that
code
for
myself
and
I
don't
have
to
deal
with
reconnecting
any
of
that.
Whatever
it's
configured
for
me
for
my
infrastructure,
it
just
goes
honestly.
G
This
was
something
that
kind
of
like
blew
my
mind
and
then,
and
then
you
were
just
like.
Oh
Jerry
I
also
just
made
a
really
simple
way
to
add
integration
tests
for
all
of
these
things.
So
thank
you
so
much
Taylor
I
loved
your
I
loved
your
work.
C
G
C
I
I
think
what
the
reason
why
it's
very
strategic-
and
it's
not
just
like
being
the
dumbest-
you
know,
person
in
the
room
but
I-
think
it's
helpful
to
restate
some
of
the
really
Salient
points
in
these
presentations
so
that
we
drive
home
one,
how
important
they
are
and
two
so
that
different
people
have
heard
the
message
from
different
perspectives.
C
That
is
why
you
know
open
source
is
always
you
know
the
world's
best
knife
fight,
because
you're
competing
on
two
things:
you're
competing
on
value
and
you're
competing
on
experience,
and
we
need
lots
of
diverse
people
to
help
understand
this
and
help
explain
it
and
help
and
help
to
bring
others
along.
So
Brooks
is
our
usual
host.
C
He
does
such
a
wonderful
job
sort
of
thinking
through,
like
what
question
might
someone
like
Liam
want
to
ask
now
and
just
sort
of
play
that
play
that
that
color
commentary
on
the
call
Bailey,
but
thank
you
so
much
for
taking
the
time
to
re-emphasize
that
along
the
way
and
Taylor
I
love
this
example.
It's
phenomenal
I
can't
wait
to
play
with
this
yeah.
A
So
anyone
can
try
this
out
and
use
it.
Like
I
said
it
is
a
like
actual
real
service
you
can
use.
So
please,
if
you
find
anything,
that's
There's
issues
with
it
file
a
bug
open
a
PR
I
said:
I'm
gonna
do
some
crazy
things
with
this.
My
next
stream
thing
that
I'm,
like
I,
said
I'm
doing
it
for
a
talk,
but
I
wanted
to
be
out
there.
A
It's
a
really
cool
example,
is
making
this
be
an
encrypted
file
server
by
storing
files
in
vaults
and
so
having
a
blob
store,
wasn't
Cloud
blobster
contract
implementation
for
Vault,
and
then
we've
also
been
talking
about.
We
need
to
like.
A
There's
there's
some
really
cool
things
that
I'm
hoping
to
do
here
in
the
future,
and
then
it
looks
like
Oren
has
a
question
before
I
go
so
Oren.
Do
you
have
you
want
to
go
ahead
and
ask
that.
E
Sure
wow
you,
you
notice
that
I
feel
like
before
I
pressed
enter
so
so
will
wash
tests
involve
like
a
little
bit
of
a
pre-setup
testing
framework
e
thing
that
the
developer
would
interact
with
as
opposed
to
like
kind
of
hand.
Rolling
things
mostly
like
so
there'll,
be
like
a
I.
Don't
know
like
some
kind
of
like
more
of
a
library
experience
with
the
with
writing
an
integration
test.
A
Yeah,
so
that's
a
really
good
question.
What
I'm
trying
to
do
with
with
anything
we
do
with
wash
chest
is
try
to
make
it
language
agnostic,
because
that's
what
wasm
is
and
so,
ideally
we
take
an
actor,
and
you
say
here
is
my
actor
wasm
and
we
can
tie
this
in
with
wash
build.
So
anything
we
support
with
washbuild.
We
could
say,
build
my
actor
for
me
and
then
take
that
actor
that
was
built
or
hey.
Here's
a
webassembly
file.
Please
test
it
and
it's
going
to
do
a
lot
of
that
like
frameworky
stuff.
A
So
it's
going
like
right
here,
because
we
don't
have
the
start
from
file.
I
had
to
very
janky
start
up
a
like
Docker
thing
with
the
registry,
so
I
could
push
it
and
have
it
local,
but
once
that's
changed
until
you
can
start
from
a
local
file
system,
that'll
be
removed,
but
then
I
do
like
washbuild
and
then
I
go
ahead
and
say,
like
Docker
push
and
then
I
say
wash
reg
push
to
that
or
sorry
wash
Ridge.
A
Push
to
that
and
then
wash
up
and
so
I
do
all
those
things
and
all
that
will
be
started
up
and
ideally
like
that's,
why
I
think
I'm
still
going
to
be
brainstorming
and
as
soon
as
I
start
to
like
coalesce
my
ideas
I'm
going
to
open
it
up
as
like
an
issue
for
people
to
kind
of
give
me
their
ideas
on
too
of
how
like
we
can
do
the
like.
Do
we
need
like
a
small
IDL
that
says,
like
oh
here's,
my
script
or
run
these
like
like
testing
things
for
me
or
whatever?
A
Then
you
can
like
exercise
that
actor
with
whatever
tests
you
write
for
it,
but
I
want
to
try
to
make
it
as
language
as
agnostic
as
possible.
So,
even
if
that's
like
a
even
if
this
is
like
becomes
like
a
simple
wrapper
that
we
provide
to
most
languages,
that
knows
how
to
like
hold
down
wash
call
Wash
test
or
wash
scaffold
or
whatever,
but
it's
not
fully
frameworked
out
yet
I'm.
Just
that
is.
E
Do,
okay
and
and
I
guess
a
follow-up
is?
Is
it
the
case
that
Autumn
fits
for
like
a
configuration
that
you
would
want
to
have
running
for
a
test,
or
is
that
not
the
right
layer
for
that.
A
I
think
for
Ed
tests.
Wadham
is
definitely
involved
because
you
say
here's
my
full.
Like
application,
here's
all
the
providers
I
need
here's
the
links,
I'm
setting,
here's
the
application,
I'm
deploying
so
when
we
get
like
bottom
to
a
full
like
actual
production
state.
That
will
definitely
be
a
good
tool
to
have
for
E
to
e
for
this
kind
of
testing.
It's
more
about
testing
the
actor
in
isolation
because
it
doesn't
really
matter
in
this
case.
It
just
shows
like
blob,
store,
fs
and
HTTP
client.
A
It
doesn't
really
matter
what
is
get
I
just
need
to
get
data
to
the
actor
and
make
sure
that
it
does
the
right
calls
and
then
gets
data
data
back
out,
and
so
that's
what
I'm
that's!
What
this
is
going
to
be
hopefully
focused
on
is
testing
the
actor
itself,
not
necessarily
the
components
around
it,
and
then
you.
F
A
E
A
Thank
you,
Jordan
had
a
question
chat
but
CJ
had
his
hand
raised
so
CJ.
Do
you
want
to
go
ahead
and
ask
yours
and
then
I'll
jump
over
to
Jordan's.
H
Sure
can
you
hear
me
thanks
for
my
microphone.
A
H
Okay,
so
I
have
a
question
concerning
your
comment
about
implementing
multiple
capabilities
on
the
same
providers
and
I,
don't
want
to
sort
of
you
know,
put
words
in
your
mouth,
so
I
won't
make
a
specific
question.
But
what
do
you
think
the
advantage
is
of
doing
like
implementing
multiple
capabilities
on
one
provider
versus
just
spinning
up
two
providers
with
multiple
capabilities
and
creating
two
separate
links.
A
There
is
an
argument
to
be
made
like,
for
example,
when
you
have
like
something
that
could
Implement
a
KV
store
and
messaging
or
you're
like
listen,
so
redis,
actually,
most
key
value
stores
have
something
where
you
can
watch
a
key
right
and
so,
instead
of
having
to
spin
up
like
multiple
providers
to
handle
one
that
that
does
messaging
and
one
that
does
like
just
the
key
value
stuff,
you
could
have
one
that
does
both
like
has
both
of
those
contracts
available,
and
the
other
thing
is
exactly
what
I
described
where
you
could
have
something:
acting
as
a
like
processing
layer.
A
So,
like
think
about
things
like
simdi
or
other,
like
platform,
specific
instruction,
type
stuff
or
let's
say
you're,
you
have
like
you're,
exposing
a
like
a
Cuda
or
something
like
that
from
like
that's
a
capability,
but
you
could
also
be
wanting
to
have
that
like
that,
could
be
a
processing
layer.
So
you
could
have
the
Implement
blob
store,
but
then,
instead
of
having
to
like
do
an
HTTP
client
call,
you
could
just
have
it
be
like
messaging
and
have
something
listening
on
the
other
end.
A
A
H
A
Yeah,
it's
it's
just
more
about
same
like
there's,
there's
times
when,
when
a
system
can
be
used
to
implement
multiple
contracts
and
it's
more
saving
that
rather
than
like,
because
you're
spinning
up,
you
have
to
spin
up
basically
a
provider
for
every
single
one
of
those
contracts.
When
you
could
have
it
be
one.
So
that's
that's
kind
of
part
of
the
other
like
I,
said
part
of
the
other
reason.
So
gotcha
thanks!
A
Jordan
had
a
question
for
those
who
are
in
were
in
live
streams.
He
said
so.
What's
the
advantage
to
this
approach
over
the
dagger
approach
seems
to
be
two
approaches
to
the
same
end.
That's
a
great
thing.
When
I
saw
what
you
were,
demoing
Jordan
I
was
laughing
because
it
is
the
here.
Here's,
my
initial
gut
thing.
This
is
not
any
judgment
call
this
is
just
this
is
why
we're
supposed
to
be
discussing
this
stuff
as
a
community
is.
A
My
initial
reaction
is
dagger,
requires
the
use
of
a
specific
product,
an
API
and
it
requires
like
I
mean
we
could
reuse
some
of
the
ideas
from
it,
but
it
is
requiring
like.
Oh,
you
write
these
tests
and
go
you're
reliant
on
their
SDK
for
testing.
So
it's
adding
yet
another
SDK,
that's
required
for
doing
stuff
in
wasm
cloud
and
I.
Don't
want
I
want
to
make
less
of
that.
A
Not
more
of
that
and
so
I'm
more
inclined
to
do
something
that's
built
into
wash
and
then
from
there
like
being
able
to
like
add
in
things
we
need
to
that
doesn't
mean
we,
we
don't
copy
ideas
or
take
some
inspiration
from
it,
but
like
that's
what
I
lean
towards
with
it
and
why
I
did
it.
The
way
I
did
was
because
I
was
like.
Okay.
I
can
run
this
in
GitHub
actions.
A
This
is
something
that
I
can
at
least
use
as
a
starting
point
for
testing
other
types
of
actors
as
well,
and
then
that
that
was
kind
of
my
my
reasoning
behind
it,
so
that
I'm.
F
A
Like
married
to
that
idea,
but
that's
my
initial
thinking
is
that
just
avoiding
the
whole
like
Justin,
said
yet
another
tool
and
trying
to
keep
this
like
not
latched
onto
a
specific
product
or
thing
and
keeping
it
focused
on
on
wasmcloud
and
what
it
needs.
A
Yeah,
like
I,
said,
like
I,
don't
think,
there's
a
negative
thing,
because
if
people
are
using
dagger,
that
seems
like
a
really
nice
way
to
do
it
and
I
wouldn't
I,
say
if
you're
doing
that
go
right
ahead
with
it.
I
just
also
think
we
should
work
on
one
that
works
for
any
type
of
cicd
pipeline,
which
would
be
like
a
wash
test
kind
of
thing.
G
Hey
Taylor
yeah
I
see
another
question
here:
we're
wondering
if
you're
gonna
hack
on
this
on
live
stream,
like
you
did
for
the
wash
Library
Factor
stuff.
A
I'm
going
as
soon
as
we
I'm,
not
gonna
hack
on
this
one
as
much,
but
there
was
another
one
that
I
think
I
can't
remember.
If
I
demoed
in
this
call
or
not
I
did
start
it
and
that
stream
I
did
or
no
I'm.
Sorry
I
didn't
start
in
that
stream,
but
there's
a
an
actor
that
I
created
called
a
resizer
and
I
think
I
demoed
it
in
the
community
call
where
it
resizes
images
for
you
and
so
and
that's
all
like
using
a
wasmcloud
actor.
A
It's
pretty
cool,
and
so
what
I'm
going
to
do
is
as
soon
as
we
polish
up
some
of
the
bugs
we
found
in
Blob
store
S3
I
wanted
to
do
a
stream,
adding
like
uploading
those
those
processed
image
files
to
a
blob
store
for
me
and
so
I'm
going
to
do
that
on
a
stream
next
to
kind
of
show
this.
So
it's.
A
A
Little
things
we
add
on
you
know
like
little
features
here
and
there,
but
it's
not
meant
to
be
super.
Complex,
just
meant
to
be
a
super
basic
plug
it
in
where
you
need
it
actor
so
yeah
I
will
wants
to
and
Oren
those
live
streams
are
announced,
a
lot
of
them.
We
do
through
cosmotic,
because
that's
where
a
lot
of
us
are
invites
are
like
we're
doing
it
like
for
fun
over
there.
A
We
do
some
laws
in
Cloud
streams
too,
so
you
can
follow
us
on
Twitter
and
we
also
talk
about
them,
especially
if
there
wasn't
Cloud
specific
and
not
cosmotic
specific.
We
generally
will
talk
about
them
in
the
slack
channels
too,
and
just
so
people
know,
because
we
don't
do
just
cosmotic
stuff
there.
We
actually
do
quite
a
bit
of
just
plain
walls
and
Cloud.
A
So
that's
where
those
are
announced
so
yeah
we'll
try
to
get
that
on
the
schedule,
just
trying
to
fix
some
bugs
with
the
The
Blob
store,
S3
stuff,
so
that
I
can
actually
upload
it
to
an
S3
compatible
store
because
I'm
looking
to
upload
it
to
digitalocean.
It's
purely
for
my
own
I.
Do
photography
on
the
side,
so
that's
where
that
comes
from,
and
so
it's
purely
self-motivated,
but
it
it's
a
really
cool
demonstration
of
what
you
can
do.
A
Okay
thanks
everyone
for
that
go
ahead
and
move
on
to
the
next
agenda
item.
Here
we
just
want
to
give
a
quick
update
on
the
Wasson
Cloud
host
b0.60,
so
we
are
working
on
that
actively
right
now
to
help
with
some
of
the
issues
that
you
could
see.
A
As
you
were
running
Watson
Cloud
at
scale
with
how
claims
were
stored,
we
want
we
made
some
changes
that
swapped
out
how
those
claims
are
being
stored
inside
of
maps
and
so
we're
working
through
some
of
the
bugs
that
have
come
out
of
that,
and
there
were
just
some
like
small,
like
we
thought.
We'd
covered
most
of
the
things
that
were
going
on,
but
when
we
actually
like
tried
exercising
it
pretty
strongly.
A
So
like
one
of
the
things
we
do
as
at
people
at
cosmonic,
we
actually
stress
test
it
inside
of
cosmotic
too,
because
we
we
pretty
much
use
all
blossoms,
wasn't
clouds
capabilities
and
when
we
did
that
we
discovered
some
bugs
we're
like
oh
yeah,
that
would
break
somebody
who's
going
to
be
running
walls
and
Cloud
on
their
own,
and
so
we're
trying
to
fix
some
of
those
right
now
to
get
them
all
working,
because
there
were
some
because
of
the
breaking
change.
A
There
were
some
task
breaking
change
inside
of
like
how
certain
data
structures
were
sent,
we've
had
to
go
back
and
make
sure
we've
we've
covered.
All
of
that
across
the
whole
stack,
so
we're
working
on
it.
There's
been
some
learnings
there
about
how
we're
how
we're
catching
all
those
in
the
different
places
it
has
to
be
updated,
but
that's
why
it
hasn't
been
fully
released.
Yet
we're
really
close
I've
been
working
on
on
testing
some
of
those
last
things
myself.
Actually,
so
that's
just
an
update
just
so
you
all
know.
A
What's
going
on
with
it,
we
hope
to
get
it
out
as
soon
as
we
can,
and
that
has
a
bunch
of
nice
goodies
in
it,
as
well
as,
like
I,
said,
a
lot
more
durable
way
of
of
handling
your
claims
that,
like
store
all
your
link,
definitions
and
whatnot.
A
C
12Th,
if
you
want
to
share
your
screen
Taylor
all
they
should
all
be
hyperlinked
for
you,
yeah.
A
A
So
there
is
the
cfp
for
the
cfp
for
a
cloud
native
wasm
day,
we're
looking
to
have
everything
there.
This
is
going
to
probably
be
the
biggest
cloud
native
awesome
day,
we've
had
and
forever.
So
that's
it's
going
to
be
really
really
cool
to
see
what's
going
on
there.
So
if
you
have
anything
webassembly
related
or
you
have
friends
that
do
things
webassembly
related
and
that's
not
just
server
side,
that's
everything
from
the
browser
to
the
server.
So
please
let
people
like
know
about
this
and
submit
because
there's
always
some
really
cool
talks.
A
So
we
want
to
have
any
an
even
bigger
School
of
companies
and
people
who
are
working
on
this
stuff
available
to
pull
from
so.
A
And
let
them
submit
and
we'd
love
to
we'd
love
to
see
that,
just
as
a
couple
other
reminders
for
events,
we
have
wazam
IO
coming
up
in
Barcelona
on
March,
23rd
and
24th
I
know
from
the
community
at
least
like
me,
and
Bailey
are
going
to
be
there.
If
anyone
else
is
going
to
be
there,
please
let
us
know
we'd
love
to
meet
up
with
you.
A
A
We
also
have
like
I
said:
there's
Cloud
native
Watson
day
itself
is
April
18th,
it's
right
before
the
actual
coupon,
and
then
there
is
also
wasm
Summit
coming
up
in
London.
The
date
is
not
fully
set
on
that
one.
It
is
mid
2023,
so
they're
thinking,
probably
junish
time
frame,
so
they're,
hopefully
going
to
nail
down
those
dates
soon.
That
is
both
virtual
and
in
person.
So
if
that
interests,
you
oh.
A
They
said
a
couple
different
dates
on
the
cfp,
thanks
Liam,
and
so
those
those
are
just
a
couple
of
the
big
like
wasm,
related
events
that
are
coming
up
and
we'd
love
to
see
people
at
them.
If
you're
in
those
areas,
we
also
might
have
a
few
others
Coming,
there's
the
other
one.
I'd
also
like
to
notice.
A
If
you're
in
Southern,
California
or
nearby
areas
me
and
Brooks
are
going
to
be
there
talking
purely
wasn't
Cloud
stuff
at
both
the
kubernetes
community
day
and
the
Cloud
native
track
of
scale
so
we'll
be
in
Pasadena.
If
any
of
you
are
in
that
area
and
would
like
to
meet
up
or
come
to
those
talks,
you
can
go
ahead
and
check
out
the
scale
website
as
well,
so
I
think
that's
it
for
all
of
the
events.
Was
there
any
other
events
that
we
should
that
anyone
else
knows
about
that?
C
We're
in
the
we're
in
the
early
planning
stages
of
a
cloud
native
cncf
dedicated
web
assembly
only
event,
but
that
is
still
like
early
exploration
and
planning.
We
have
a
meeting
about
that
next
week,
though,
but
we'll
keep
everybody
everybody
in
the
loop
as
soon
as
we
have
more
details
about
it.
A
Okay,
I
think
with
that.
Are
there
any
other
things
from
the
community
that
people
want
to
talk
about
before
we
go
ahead
and
finish
up
the
call
today,
I.
G
I
see
one
question
about
how
awesome
it
would
be
to
learn
how
we
do
that
testing
within
cosmotic
and
my
immediate
thought
there
was
I
wish
it
was
more
awesome
than
it
is.
But
do
you
want
to
elaborate
on
that
Taylor.
A
Yeah,
so
we
actually
start
that
running
basically
in
our
our
development
environment
and
then
actually
exercise
all
the
different
functionalities.
A
So
we
have
users
log
in
we,
because,
if
you're
unfamiliar
with
cosmotic,
we
host
managed
versions
of
a
lattice
they're
called
constellations
and
yeah
it's
basically
a
b
testing
is
kind
of
what
it
boils
down
to,
but
we
we
test
out
those
options
and
we
make
sure
that
you're
able
to
create
new
hosts
inside
of
your
constellation
and
do
everything
that
you're
supposed
to
be
able
to
do
and
then
one
and
because
it's
in
like
a
big
environment
and
a
multi-tenant
environment.
We.
A
Hit
all
the
different
kind
of
edge
cases
you
could
expect
from
there,
and
so
that's
the
kind
of
testing
we
do.
A
And
also
yeah,
it
is
resource
constrained
because
we're
limiting
people
to
how
many
things
they
can.
They
can
run
because
it's
a
free,
free
tier
right
now,
and
so
they
like
that's
the
kind
of
thing
that
really
helps
us
stress
kind
of
the
things
you
wouldn't
normally
think
of
doing
so
that's
that's
the
kind
of
testing
we
do
yeah
and
it's
not
as
impressive
as
you
think.
A
So,
when
it's
more
impressive,
we
might
do
a
talk
about
it
and
or
show
it
here
just
to
show
other
people
who
are
running
was
on
cloud
at
scale
like
how
we're
testing
it
out,
but
right
now
it's
really
not
that
impressive.
To
be
honest,.
A
Okay,
any
other
questions
or
discussion
items.
A
So
the
question
was:
are
you
using
drill
or
Goose
for
load,
testings
and
I
haven't
used?
Neither
of
those
we'll
generally
load
test
with
some
things
like
hey
yep
hay
is
our
big
one
just
really
like
hit
some
endpoints
and
make
sure
it
can
handle
it
obviously
like
we'll,
keep
doing
more
and
more
things
as
we
continue
to
grow
the
platform
there
and
we'll
those
learnings
almost
always
get
directly
passed
back
into
the
Lawson
Cloud
Community.
A
So,
okay,
well
I,
think
we're
I
mean
we.
We
can
end
early
so
we'll
go
ahead
and
and
stop
the
live
stream
here
in
just
a
second,
but
thank
you.
Everyone
for
attending
we'll
be
here
next
week
same
time
same
place
and
feel
free
to
join
through
any
of
the
the
stream.
The
streaming
options
we
put
out
there
or
here
on
the
zoom,
call
and
we're
really
grateful
you're
all
here
and
attending
and
giving
us
your
feedback.