►
From YouTube: wasmCloud Community Meeting - 9 Aug 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
wasmcloud
community
meeting
for
Wednesday
August
9th.
Here
is
our
agenda
for
today
we're
going
to
start
with
a
little
bit
of
a
demo
of
the
wadham
0.5
I'm,
calling
it
a
feature
showcase.
It's
just
showing
off
some
of
the
things
that
we've
been
working
on
for
the
upcoming
Autumn
release
and
then
we'll
do
a
little
discussion
talk
about
the
road
map
where
it's,
where
it's
at
for
now
and
specifically
try
to
update
on
the
rust
host
and
whatify
efforts
so
to
get
started.
A
I'll
do
just
a
little
bit
of
showing
some
things
for
the
Autumn
feature:
showcase,
let's
go
ahead
and
go
to
the
excuse
me.
The
Autumn
repository
I
set
something
up
in
the
issues
in
the
spirit
of
you
know,
setting
up
our
roadmap
and
what
we're
going
to
be
doing.
If
you
go
to
the
issues
page
and
then
you
go
over
to
Milestones.
You'll
now
see.
There's
a
V5
and
a
V6
issue
Milestone
here,
so
very
Loosely
v05
is
going
to
be
the
next
braking
release
of
autumn.
A
You
know
with
new
features
new
fixes
and
then
pretty
Loosely.
Anything
that's
not
going
to
fit
into
V5
or
isn't
really
prioritized
for
the
short
term
is
going
into
V6.
So
if
we
click
into
that
issue,
Milestone
anybody
should
be
able
to
see
things
here.
None
of
them
are
specifically
marked
as
good
first
issues.
I
think
that
that's
accurate
but
I
think
in
the
future.
I
would
love
to
help
set
some
of
those
things
up,
so
that
people
can
have
an
idea
of
where
we
would
like
some
help
for
contributors.
A
So
right
now,
one
of
them
is
complete,
but
all
of
these
I
think
have
work
in
progress
and
the
last
one
that
I'm
going
to
be
demoing
today.
That
isn't
quite
finished
here
are
version
upgrades
for
actors
and
providers
and
a
newly
deployed
applications,
don't
terminate
old
resources.
So
this
is
really
fun.
I
have
this
open
PR
that
ignore
this
red
X?
It
means
nothing,
but
it
contains
some
of
the
fun
features
that
I'm
going
to
show
you
right
now.
A
Things
again,
this
is
really
fun.
Okay,
so
let's
go
ahead
and
pop
into
the
the
terminal
a
little
bit
here,
I'm
going
to
go
ahead
and
launch
wash
in
the
background
and
I'm
going
to
disable
Autumn
just
so
that
I
can
run
it
on
my
own
and
then
let's
go
ahead
and
open
up
a
new
window
and
go
to
Autumn
and
run
a
lot
of
them.
A
Yet
so,
if
you're
new
to
the
awesome,
Cloud
community-
and
you
haven't
heard
of
either
of
these
projects
wash-
is
the
wasmcloud
shell
just
kind
of
helps
you
bootstrap
infrastructure
and
then
wadham
the
wasm
cloud
application
deployment
manager
is
essentially
responsible
for
managing
a
desired
state
in
across
the
entire
awesome,
Cloud
Network
or
the
wasm
top
lattice.
So
you
can
use
this
to
create
applications
and
then
Autumn
will
declaratively
manage
those
applications
and
the
the
desired
state.
A
For
you,
so
if
I
take
a
look,
if
I
query
the
current
list
of
applications,
we
don't
have
anything
defined.
That
is,
you
know,
kind
of
expected.
We
just
launched
it,
but
we
have
our.
What
I
have
set
up
here
is
our
lovely
pet
clinic
application,
and
in
this
in
this
directory
in
repository,
there
is
a
wadham.yaml
and
if
we
take
a
look
at
this
format,
it's
actually
using
the
open
application
model
format.
So
there's
nothing.
You
know
we
have
custom
components
here,
but
it's
using
the
exact
same
standard.
A
So
this
pet
clinic
application
consists
of
five
different
actors
which
you
can
see.
We
have
laid
out
here
as
components,
including
the
image
reference
and
then
a
simple
spread,
scalar
trait,
which
is
bottom
specific
for
setting
up.
You
know
ensuring
that
there's
a
certain
number
of
replicas
running.
You
can
also
spread
this
across
different
hosts
and
things
like
that,
but
we're
just
doing
it
all
local
to
start.
So
we
have
our
five
actors
that
make
up
our
pet
clinic
microservice
example.
A
So
the
first
thing
that
you
can
do
to
create
an
application
is
to
put
the
model
and
we
list
the
applications.
After
doing
that,
essentially
what
you're
doing
here
is
you're,
saying:
hey
here's
a
new
version
of
this
application,
but
don't
go
and
deploy
anything
yet
I
just
want
to
make
sure
that
it's
valid
I
want
to
make
sure
that
it
is,
you
know,
properly
able
to
be
stored
and
parsed
on
all
those
things.
So
after
we
put
the
Manifest,
we
can
see
that
we
have
one
application
and
it's
deploy.
A
Status
is
undeployed
when
you're
ready,
ready
to
run
the
example.
You
can
deploy
the
application
model
and
a
specific
version.
So
if
we
say
deploy
pet
clinic001
and
we
list
the
application,
we
can
see
that
it's
currently
compensating-
and
this
is
one
of
the
new
features
to
0.5
it'll,
essentially
report
on
the
deploy
status
very
similar
to
any
other
infrastructure
tool.
A
A
What
bottom
looks
like
from
the
basic
functionality
and
one
of
the
newer
features
to
this
is
the
status,
so
you
can
actually
tell
what's
happening
with
the
with
the
application
if
it's
fully
deployed
or
not
now,
I
want
to
show
off
some
of
the
one
of
the
bugs
that
we
fixed
and
one
of
the
other
things
that's
going
to
be
coming
with
this
latest
PR,
which
is
Manifest
upgrades
and
that's
what
happens
when
you
deploy
a
new
version
of
an
application
and
it
has
changes
so
whether
it's
scaling
up
or
changing
out
resources.
A
So
what
it
looks
like
for
you
once
you've
gotten
your
application
deployed,
then
you
want
to
make
some
changes.
You
can
simply
update
the
version
here
in
the
Manifest
and
then
say
if
we
wanted
to
change
this
change,
this
manifest
to
run
five
replicas
of
every
single
actor
like
one
just
isn't
quite
enough
for
the
scale
we
want
to
work
at.
So
we
can
change
that
to
update
the
replicas
of
every
single
actor
to
five,
and
then
we
can
either
we
can
I'll.
A
Do
it
this
way
again
and
then
I'll
show
you
the
shortcut
after
we
can
put
that
manifest,
and
then,
if
we
look,
the
latest
version
is
zero,
zero
two
and
we
can
deploy
the
pet
clinic
zero,
zero.
Two
oops
watch
app
deployed.
Again
we
take
a
look
at
the
dashboard.
We
can
see
that
it's
already
gone
and
started
spinning
all
those
things
up.
Great
we've
reached
the
desired
state
of
five
replicas
per
actor
and
we're
good
to
go.
So
that's
what
it
looks
like
to
do
a
like
a
simple
manifest
upgrade.
Now.
A
Let's
say
we
wanted
to
do
something
which
is
a
really
common
story
in
just
all
kind
of
Ops
developer
scenarios
where
we
wanted
to
upgrade
one
of
the
versions
of
the
providers.
So
right
now
we're
running
HTTP
server
17-0.
This
is
actually
I,
think
two
major
versions,
two
minor
versions
behind.
Let
me
check
the
latest
is
zero
nineteen,
one
yep,
so
the
old
version,
which
is
0
17
say
we
has
it
say
it
has
a
vulnerability
or
some
kind
of
bug
in
it,
and
so
we
want
to
be
able
to
come
into
our
manifest.
A
We
don't
update
any
of
our
actors,
like
any
of
our
business
logic,
we're
just
swapping
out
to
the
newest
HTTP
server
and
we
bumped
the
version
to
zero
zero.
Three
now
wash
app
deploy
supports
the
name
of
the
model
in
the
version,
but
you
can
also
directly
deploy
from
a
manifest
very
similar
to
like
a
cube
control
apply
and
we
deploy
from
this
Manifest.
A
This
is
actually
going
to
do
and
it's
going
to
do
a
diff
of
the
old
manifest
of
the
new
one
and
see
that
the
HTTP
server
provider,
the
component,
has
changed
meaningfully
the
image
reference
changed.
So
as
soon
as
we
deploy
this,
it
deletes
the
old
version
of
the
HTTP
server
and
then
starts
the
new
version
of
the
HP
HTTP
serving.
So.
If
we
check
the
inventory
of
this
at
of
this
host,
we
can
see
that
HTTP
server
0191
is
running.
We
can
do
the
same
thing
for,
for
example,
with
SQL
DB
postgres.
A
The
latest
version
zero
six
zero
and
we
can
deploy
that
new,
manifest,
which
will
should
delete
this
old
version
of
the
SQL
database
and
then
bring
up
the
new
one
see
if
that
went
all
the
way
through
I
might
just
have
to
help
it
out
a
little
bit
or
maybe
that
was
the
wrong
version
whoops.
Well
now
you
can
see
what
it
looks
like
to
do.
A
little
bit
of
a
rollback.
We
do
pet
clinic,
zero,
zero.
A
Four
I
think
that's
the
earliest
one
zers
are
three
and
we'll
give
it
a
second
to
actually
go
through
and
compensate
there,
but
essentially
what
it
looks
like
you
know
here
you
can
see
that
it's
converging
on
the
desired
State
and
we'll
see
the
link
definitions
come
up
in
just
a
second.
So
this
is
exactly
what
it
looks
like
to
do
upgrades
using
manifest
with
Autumn.
So
you
can
swap
out
this
individual
components
and
watch
isn't
going
to
or
what
I'm
isn't
going
to.
You
know
delete
the
entire
application
and
then
schedule
it
again.
A
It
should
just
be
doing
essentially
a
a
smart
diff
of
what
existed
before
and
then
what
exists
now.
So
taking
a
look
at
I
might
have
closed
this
out,
taking
a
look
at
the
bottom
milestone
for
0.5
the
things
that
we'd
like
to
get
in.
There
are
version
upgrades
for
actors
and
providers
which
I
kind
of
showed
during
during
that
demo.
A
I
think,
there's
just
still
a
couple
of
things
that
we
want
to
work
out
with
making
sure
that
that
works,
really
clean,
newly
deployed
applications,
determinating
old
resources-
if
they
don't
don't
need
to
exist
anymore
and
then
from
there
it's
just
a
little
bit
of
validation
around
manifests
and
a
bug
that
we
found
for
tracing
just
making
sure
that
that
all
works
fine.
A
So
that
was
a
little
bit
of
a
of
a
showing
of
what
it
looks
like
to
do.
You
know
some
of
the
Manifest
upgrades
anybody
have
any
questions
or
just
general
yeah
general
questions,
comments
on
on.
B
Hi,
it's
me
not
totally
audience.
Plant
I
was
wondering
if,
when
I
am
using
wadam
in
production
and
I'm
trying
to
run
it
like
what
is
there,
anything
I
can
do
to
alert
on
like
status
changes
if
something's
happening.
A
Great
question:
Taylor,
let
me
brings
up
exactly
something
that
I
didn't
show
during
the
demo.
It's
almost
like
you
are
a
plant
okay.
So
let's
take
a
look
at
this.
If
we,
if
we
list
the
applications
as
I
was
showing
before
I
was
essentially
showing
the
deploy
status
as
through
the
wash
API,
but
this
is
actually
this
status
is
represented
in
a
Nats
Stream
So.
This
wadham
status
stream
will
actually
contain.
It
contains
multiple
messages.
A
The
way
that
streams
work
in
Nats
is
you
just
publish,
as
you
normally
do,
to
like
a
to
a
topic,
but
streams
are
specifically
intended
to
you
know
there
are
many
different
things
they
can
do,
but
in
this
case
it's
essentially
taking
messages
from
that
topic
and
storing
them.
So
you
can
query
them
and
if
I
do
a
Nat
stream,
git
I
can
actually
grab
the
latest
status
for
the
wadham
application
at
clinic,
and
we
can
just
see
type
ready
here
right.
A
There's
nothing
super,
there's
nothing
more
informative
than
than
what
wash
is
telling
us,
but
if
we
were
to
deploy
pet
clinic
001
and
then
check
the
stream
again,
we
can
see,
compensating
and
then
I,
don't
think
anything
here
will
trigger
a
I,
don't
think
anything
here.
Well,
there
we
go.
A
I
was
wondering
if
it
would
trigger
the
status
message,
but
you
can
essentially
watch
this
stream
for
in
this,
like
little
script
is
just
like
spinning
over
and
over
to
check
out
the
stream,
but
you
can
watch
this
stream
for
the
status
type
until
it
becomes
ready
and
I
think
that
the
real
Nat
specific
way
of
doing
this
would
be
to
create
a
consumer
on
the
stream.
Basically
watching
messages
come
through
I'm
kind
of
doing
it
in
a
lazy
Way
by
watching
it
and
querying
it
every
second
Taylor
you
might
have
more
to
say.
B
Why
I
asked
the
question
so
that
bricks
could
show
it
off
was
that
you
can
consume
the
stream
data
to
build
like
monitoring
and
other
like
common,
like
SRE
type
tasks,
on
top
of
a
dam
with
with
ease,
you
can
do
it
with
like
basically
a
stateful
thing,
which
is
this
stream,
where
you
can
like
make
sure
you
have
consumed
every
event
that
has
happened,
which
could
be
useful
for
building
like
another
system
on
top
of
this,
or
you
can
also
just
subscribe
to
the
Nats
topics,
so
you
can
subscribe
to
woodam.sas.default
dot,
carrot
or
dot
star.
B
Actually,
because
it's
just
the
the
thing
and
so
any
any
status
changes
will
will
be
reflected
as
you
do
things
so
I
can
pretty
sure
if
Brooks
goes
and
deletes
this
yep
you'll
start
seeing
like
messages
come
in
as
they're
emitted.
So
you
have
two
different
ways
of
consuming
this
data,
depending
on
the
need
for
your
like
for
whatever
you're
trying
to
alert
on.
A
Yeah
I
can
totally
see
us
having
an
extension
on
a
wash
app
deploy
where
we
also
Taylor.
You
know
a
little
bit
about
weight
Flags.
We
could
add,
like
a
weight
flag
to
wash
out
deploy,
and
you
know
something
that
you
say:
hey,
deploy
this
application
and
then
wait
until
the
status
reports
is
ready
before
you
finish,
executing
the
command.
A
I
think
that
that
would
be
a
I'll.
Let
Taylor
have
the
ultimate
say
on
that
one,
but
the
I
think
that
that
would
be
a
really
neat
way
to
be
able
to
know
when
your
application
is
fully
deployed.
B
Yeah,
essentially,
it
makes
it
simple
to
do
like
an
easy
back
off
too
like.
If
you
see
it
go
to
error
State,
you
can
back
it
off
to
the
previous
version,
or
we
can
build
that
into
like
a
into
wash.
Those
are
the
kind
of
things
that
you
can
see
in
the
in
the
future.
With
having
this
data
available,
yeah.
A
Yeah
so
well,
I
guess:
I'll
pause,
really
quick.
Any
other
questions
or
comments
on
on
water.
C
Yeah
CJ
here
I
have
a
quick
question.
I
know
the
d
stands
for
deployment,
but
are
there
any
features
that
sort
of
support
developing
components
in
the
context
of
all
of
the
providers
and
other
components
that
exist
without
having
to
go
in
and
say,
update
the
minor
version
every
single
time
and
hit
deploy
because
I
know
that
exists?
There's
like
an
experimental
feature
in
wash
where
you
can
do
that
for
a
particular
actor.
A
Yeah
yeah
great
question,
so
this
is
something
that
technically
works
now
and
I'm.
Gonna
try
to
I
can
try
and
live
demo
this
as
well,
while
this,
while
this
builds
I'll
give
a
Spiel.
This
is
something
that
technically
works
now
and
we're
really
trying
to
look
at
for
a
really
polished,
developer
experience
around
developing
actors
and
and
providers.
You
know
all
the
components
for
wasmcloud
so
in
this
manifest.
A
Actually
let
me
grab
this
really
quick
I'm,
just
gonna
double
check
that
okay
Clinic
API
ads.
So
in
this
Manifest
this
technically
this
image
reference
does
not
have
to
be
a
an
oci
image
reference.
A
So
if
you
wanted
to
develop
instead
with
a
local
version
of
an
actor,
you
can
add
in
and
you
can
technically
do
a
relative
path
here
just
depends
on
where
you
launched
wash
from
or
where
you
launch,
wadum
from
which
is
enough
where
you
launch
wash
from
so
it's
a
little
bit
harder
to
actually
line
this
up
right,
but
you
can
actually
point
this
directly
at
a
file
on
your
local
file
system,
and
you
just
have
to
have
this
kind
of
prefix
the
file
colon
slash.
A
C
A
That
work
I'm
just
going
to
try
to
restart
it.
Just
because
I
haven't
tried
that
specific
scenario
before
okay
get
rid
of
some
of
the
old
things.
Essentially,
what
I'm?
What
I'm
getting
at
here
is.
You
can
swap
the
oci
reference
out
for
a
local
file
and
what
this,
what
this
does
essentially
has
Autumn
managing
the
state
of
bats.
Oh
there,
you
go.
What
are
you
doing
there
pet
clinic?
Oh
okay,
it
might
have
just
sent
off
those
commands
and
then
and
then
waited.
Let
me
get
the
inventory
to
check
that
now.
A
You
can
see
basically,
that
the
pet
clinic
API
actor
that
we
deployed,
instead
of
being
from
an
oci
image
reference
it's
from
a
file
instead.
So
this
is
my
local
file
system
and
the
part
that
we,
the
part
that
I
really
want
to
tease
out
here,
is
when
you
make
a
change
to
your
actor
right
like
you.
Can
you
can
make
any
changes
here?
You
can
run
washbuild
to
to
regenerate
the
actor
the
all
you
have
to
do
in
order
to
get
water
to
run
the
new
or
you
know,
to
run.
A
The
new
version
of
the
actor
is
to
scale
down
the
pet
clinic
API
to
xero,
and
then
the
act
of
stopping
those
actors,
kind
of
seems
like
I'm,
in
a
little
bit
of
a
a
half
deploy
state
but
the
foreign
stopping
those
actors.
So
here
I'll
try
it
again.
We
stop
all
the
pet
clinic
API
actors,
wadham
sees
them
exit
the
lattice
and
it
says:
hey,
go
start
more
of
those
actors
and
wasm
Cloud
pulls
them
directly
from
disk.
A
So
essentially,
here
the
the
hot
reloading
is
the
stage
that
we
is
is
the
step
that
we
have
to
add.
But
what
I
really
like
about
Autumn
here
is
that,
if
you're
developing
on
a
single
component,
the
Autumn
lets
you
define
all
of
the
other
related
actors
and
the
related
providers
and
all
their
configuration,
and
then
you
can
just
essentially
iterate
on
that
one
component
Taylor.
We
had
some
some
thoughts,
yeah.
B
B
That
could
be
really
handy,
whether
that's
just
like
some
like
whether
like
we
put
something
in
a
wash
that
does
the
step
of
scaling
down
to
zero
or
whatever
for
you
automatically
and
then
puts
it
like
I,
don't
know
what
we
what
we
can
make
it
look
like,
but
if
you
have
any
ideas
around
this
or
if
anyone
listening
to
this
now
or
in
the
future,
has
any
ideas
about
like
oh
I'd
love
for
it
to
do
this
or
I
think
I
can
make
it
work.
B
A
A
We
could
have
a
really
sweet
experience
by
combining
the
ideals
of
of
wash
Dev,
which
is,
does
watch
an
actor
locally
for
changes
and
will
hot
reload
it
and
wadham
the
ability
to
Define
all
the
configuration
and
the
links
that
you
need.
I
think
we
could
have
a
a
really
sweet
experience
there.
A
Yeah
Bailey,
if
you're
available
to
chat,
go
ahead
and
throw
that
out
there.
Otherwise
I
can
I
can
read
that
too,
but
I
I
completely
agree
with
you.
There
Bailey's
message
in
the
in
the
comments
just
said:
I
want
to
tilt
experience.
Tilt
is
like
a
as
long
as
I'm,
not
completely
wrong
like
it
helps
with
the
developer
iteration
loop
on
a
kubernetes
application,
and
it's
really
is
a
really
sweet
experience
compared
to
like
rebuilding
containers
re.
A
A
Right
well,
I
think
that
that's
all
that
I
had
for
the
for
the
Autumn
section
I
think
next
week,
since
it
probably
won't
release
this
week
next
week,
I'd
love
to
demo.
Some
of
the
work
on
validating
manifests
when
we
put
them
to
make
sure
that
they
are.
You
know
they're
they're,
gonna
work.
Well,
there's
not
going
to
be
any
obvious
conflicts
for
when
we
start
the
application
and
then
we
should
be
good
to
go
with
wadham
releasing
0.5,
and
you
know
from
there
we'll
just
cut
a
new
release
of
wash.
A
That
includes
that
version,
and
hopefully
we
can
add
a
little
bit
more
documentation
and
an
example
too,
so
that
you
all
can
can
run
through
it,
but
it
should
just.
This
should
just
be
a
essentially
a
wholesale
improvement
over
wadham
0.4,
just
implementing
some
of
the
things
past
MVP
to
to
make
it
feel
real
nice.
A
Okay,
all
right!
Well,
we
can
go
ahead
and
move
on
to
the
next
section
of
the
community
called
then
I
think.
So.
The
next
thing
that
we
want
to
talk
about
is
just
do
a
general
roadmap
update
on
the
well
really
where
we
are
in
general,
with
the
roadmap
and
then
talk
about
the
rust
host
and
and
whatify
efforts.
A
If
you
weren't
in
the
community
call
last
week,
we
do
have
a
zoom
out
just
a
little
bit
now
we
do
have
a
road
map
set
up
in
GitHub,
and
so,
if
you
are
looking
for
how
to
get
there,
you
can
actually
go
to
the
let's
click,
all
the
things
so
you
get
to
where
you
want.
You
can
go
to
github.comcloud
and
then
you
can
navigate
to
the
project
section
and
then
see
the
WASP
Cloud
roadmap
there.
So
this
is
totally
open
anybody.
A
Can
anybody
can
make
it
here
and
we've
got
a
couple
of
different
views
here,
but
I'm
going
to
focus
on
the
the
work
status
view
just
for
now,
just
to
show
some
of
the
things
that
we
are
working
on
at
a
high
level,
I'd
love
to
do
an
update
here.
So
we
can
see.
We've
completed
a
couple
of
things
from
when
we
opened
the
roadmap
last
week.
Just
getting
everything
cut
up
on
status
and
right
over
here,
the
one
that
I
really
want
to
call
attention
to
is
this
blocked
effort.
A
This
this
issue
is
not
really
encapsulating
the
whole
effort
of
calling
the
Watson
Cloud
rest
toast
done,
but
this
specific
issue,
once
the
rust
host
is
up
to
feature
parity,
we'll
be
able
to
be
worked
on
and
so
over
here
in
the
ready
for
work
and
in
progress
section,
we
have
some
big
efforts
going
on,
especially
around
two
issue:
Milestones,
which
is
the
widify
effort,
changing
all
of
our
interfaces
over,
to
wit,
and
then
expressing
our
expressing
our
logic
in
actors
and
providers
based
on
that
and
then
a
new
Milestone,
which
I
asked
Roman
and
Conor
to
get
set
up
yesterday
and
we've
got
kind
of
a
scaffold
here
called
OTP
feature
parity,
which
is
just
tracking
the
effort
that's
going
on
in
the
the
rust
host.
A
A
Taylor
or
Bailey,
are
you
interested
in?
Is
there
anything
else
that
you'd
like
to
add
onto
these
onto
the
efforts
here
in
the
roadmap.
B
I
can
give
a
bigger
update
on
things.
I
do
want
to
call
out,
like
some
work
being
done
so
various
community
members
and
people
who
are
here
Connor
and
Roman
have
been
working
a
lot
on
the
the
rest
host
me
and
Victor
have
been
working
on
wittifying
things,
I've
been
kind
of
just
trying
to
scaffold
it
all
out,
make
it
work
and
Victor's
been
doing
the
some
heavy
lifting
around
getting
the
code
generation
working,
especially
for
providers
and
so
like
those
are
all
in
progress.
B
If
you
are
curious
in
seeing
what
things
are
going
on,
I
have,
if
you
remember
last
week,
I
talked
around
like
this
idea
of
wazzy
fills
and
multiplexers
and
a
whole
bunch
of
Concepts
I'd
highly
recommend
going
to
the
community
call
last
week,
the
recording
of
that
and
watching
that
if
you
want
more
information,
but
this
is
the
example
that
has
the
Wazi
fill
here
at
the
top
level
and
then
the
multiplexer
and
a
subdirectory.
B
These
are
just
experiments,
I'm
working
on
we're
currently
paused
on
this,
while
some
some
things
happen
inside
of
inside
of
the
webassembly
community,
because
right
now,
there's
been
a
couple.
Changes
that
landed,
so
things
aren't
completely
working
together
until
they
go
get
to
the
basically
the
next
tag,
so
we're
working
on
solving
that
and
that'll
solve
some
of
my
issues
with
the
with
putting
together
the
Wazi
fill
and
then
composing
it
all
together
and
then
we'll
have
the
magical
moment
where
everything
just
composes
together
and
runs
as
described
last
week.
B
So
that
is,
that
is
where
we're
currently
at
I
know.
I.
Think
I
saw
maybe
like
Conor
victory
in
here.
If
they're
available,
they
can
say
something
otherwise,
like
that's
kind
of
the
status
of
where
things
are
at
we're.
Moving
along
with
the
rest
host
getting
most
the
core
functionality
in,
we
should
be
getting
done
in
the
next
few
weeks
with
at
least
the
core
functionality.
So
we
can
show
right
like
that.
It
can
run
what
we
expect
it
to
run.
A
I
did
not
mean
to
stop
sharing
there
if
anybody's
interested
in
just
tracking
this
at
a
pretty
high
level
in
the
WASP
Cloud
Watson
Cloud
repository
like
our
home,
slash
where
the
the
rust
hosts
and
some
other
things
are
going
on.
There
are
also
two
issue:
Milestones
there
that'll
be
important
to
track
and
there's
going
to
be
some
more
things
added
for
OTP
feature
parity,
but
you
can
see
we're
making
really
steady
progress
on
whatify
and
that's
a
really
it's
really
exciting
effort.
A
So
if
anybody
has
any
comments
or
concerns
or
suggestions
for
for
the
roadmap
and
an
issue,
Milestones
really
trying
to
keep
these
things
a
little
more
transparent
at
a
high
level,
we
would
love
to
love
to
hear
your
feedback.
There's
opportunities
to
concern
to
whatever
that
wasn't
a
good
English
sentence,
but
we'll
just
keep
moving
on.
A
All
right,
well,
I,
think
that's
what
we
had
planned
for
our
for
the
Washington
section
of
the
community
meeting
I
know
that
there
is
at
least
one
exciting
thing
going
on
in
the
broader
webassembly
ecosystem,
so
I
wanted
to
at
least
call
attention
to
that.
If
you
go
take
a
look
on
the
golang
site
on
the
go
blog,
they
release
go
1.21,
big
text
and
if
you
scroll
down
here
to
the
bottom,
we
see
a
nice
little
heading
here.
A
Newport
to
Wazi,
so
go
1.21
adds
an
experimental
port
for
Wazi.
A
You
can
just
set
your
you
goose
and
your
gorch
for
webassembly
and
you
can
compile
things
to
to
awesome,
which
is
a
really
really
exciting
advancement
in
the
go
space.
There's
a
lot
of
complicated
terminology
around
the
pattern
that
go
uses
for
interacting
with
webassembly
modules
and
if
go
or
go
wow.
That's
what
I
think
of
you.
If
Jordan
is
here,
he
could
maybe
give
a
little
bit
of
extra
comments
on
how
his
work
is
going
with
creating
go
actors.
A
As
you
know,
wasmcloud
has
had
support
for
tinyo
for
for
quite
a
long
time
for
actor
languages,
but
this
is
a
really
exciting.
You
know
this.
This
support
to
Wazi
supports
command
only
modules,
and
you
know
is-
is
specifically
adding
Wazi
support
here
in
this
version
of
go,
which
is
really
exciting.
A
I
am
totally
coming
up
with
all
that
on
my
own
and
not
just
reading
Bailey's
comments.
Bailey
is
there
more
that
you
wanted
to
say
here.
B
D
No,
that
was
perfect
and
I
think
the
main
thing
to
highlight
is
that
it
doesn't
allow
for
exports.
D
Yet
so
you
can
see
in
that
comment,
it
says:
go
wasm
import,
so
you
can
import
things
like
from
the
host
environment,
which
is
you
know,
kind
of
hard
to
like
solve
that
first,
but
what
they
haven't
solved
is
being
able
to
export
functions
that
are
within
your
go
module
so
that
your
go
module
can
be
essentially
a
library
that
other
people
can
consume,
and
so
that's
a
really
powerful
thing
that
we
want
and
I
heard
from
many
birds
yesterday
that
the
that
folks
are
are
working
on
that
and
we
might
have
that
in
the
next
go
release.
D
A
Awesome,
I'm
gonna
blind
click.
A
couple
of
links
here,
oh
sweet,
so
this
is
one
that
that
Jordan
sent
me
in
the
chat.
It
looks
like
that
the
by
code
Alliance
is
adding
a
go
subgroup
and
getting
members
together
there,
which
is
really
awesome.
I,
think
that
this
you
know
this
is
really
exciting
to
have
this
in
the
in
the
pipeline.
What
groups
are
there
now
in
the
in
Sig
gas
languages,
python,
JavaScript
typescript
and
go
very
exciting?
Well,
this
is
this
is
really
cool.
A
I
can't
wait
to
add
all
these
things
to
to
wasmcloud
around
the
around
the
language
support.
A
All
right,
well,
that
was
that
was
what
I
had
from
the
broader,
broader
webassembly
ecosystem.
Liam
I
see
you
sent
a
couple
of
links
here
in
the
chat,
looks
like
for
the
by
code.
Alliance
component
ties
the
world.
Do
you
want
me
to
go
ahead
and
share
some
of
those
things?
Yeah.
B
That's
right,
if
you
want
to
just
open
up
the
two
links,
that'd
be
awesome,
Brooks,
just
a
quick
call
to
action
to
everybody.
B
You
can
catch
up
with
the
awesome
Cloud
team
and
the
cosmonic
crew
at
two
upcoming
events:
there's
the
Linux
foundations,
wasmcon
2023,
helping
in
Bellevue
Washington
up
September,
6th
and
7th,
and
that
will
be
followed
by
the
bytecode
alliances
componentize
the
world
or,
as
I
like
to
refer
to
it
bacon
by
codealliancecon,
where
we're
going
to
take
the
new
standards
and
all
the
exciting
stuff
you
learn
about
it.
B
A
Hey
thank
you.
Sweet
I
think
that
that
is
it's
pretty
sweet
to
have
some
some
movement
in
the
broader
there's,
always
things
moving
around,
but
it's
great
to
have
some
some
of
the
noteworthy
things
that
that
we
can
share
here,
at
least
that
that
I'm,
aware
of
so
I,
always
like
adding
some
things
on
the
broader
webassembly
ecosystem
at
the
end
here,
I
think
we've
got
some
time,
though,
left
in
the
the
rest
of
the
call.
So
I'll
go
ahead
and
open
the
floor.
A
For
you
know
this
can
be
relating
to
anything
that
we
showed
off
today
or
just
general
General
things
that
folks
would
like
to
talk
about
in
the
awesome.
Cloud
ecosystem
go
on
me
for
a
few
minutes
and
see
if
there's
interests.
D
The
wazzy
subgroup
meeting
tomorrow
is
going
to
go
over
a
proposal
that
we
put
in
two
weeks
ago
that
defined
what's
going
to
go
into
YZ
preview
too.
We
kind
of
came
up
with
a
set
of
launch
criteria
which
essentially
comes
down
to
we've,
got
these
two
different
types
of
interface:
definitions
that
are
generally
useful.
D
They
have
more
than
one
implementation
and
they've
reached
a
level
of
stability
once
we
have
that,
then
we're
going
to
basically
call
yazzy
Preview
2
launched,
but
it's
a
it's
a
window
of
launch
in
that
there
may
likely
be
other
different
types
of
interfaces
and
worlds
that
also
reach
a
level
of
stability
and
implementation.
That
could
eventually
be
added
to
that
set
that
we
kind
of
consider
what
is
YZ
preview
to,
and
so
we're
going
to
have
an
open
discussion
tomorrow
going
over
that
a
little
bit
more.
D
There
was
a
lot
happening
over
the
last
week
or
so
in
that
issue
after
after
we
we
made
that
proposal.
So
if
you're
interested
in
that
definitely
join,
that's
part
of
the
w3c
foreign.
B
A
Was
gonna
say
as
much
fun?
It
is
for
you
me
and
Bailey
to
just
kind
of
look
around
in
this
virtual
space.
I
think
we'll
probably
go
ahead
and
call
it
now
thanks
everybody
for
for
coming
to
the
community
stream
community
meeting
this
week
as
usual.
Please
let
me
know-
or
let
us
know
in
slack
if
there's
anything
that
you'd
like
to
demo
or
discuss
next
time
and
I-
think
with
that
we'll
just
post
notes
shortly
after
the
call
thanks,
everybody.