v1.0.0-rc.1

[brooksmtownsend]

Hey everyone! Creating a thread here to talk about the 1.0 release candidate 1. Please use wash-cli v0.27.0-alpha.2 to test this release as it includes all new client libraries, tools, and pins to 1.0 rc.1.

Known Issues/Limitations

• We're actively updating our 1.0 release candidate documentation. Make sure to browse with the 1.0 version selected if you're using documentation on https://wasmcloud.com/. (As of writing this, the quickstarts still need some updates!)
• The wadm version bundled in this release does not have support for creating or deleting configuration. If you specify configuration in your manifest, please ensure you create it manually beforehand with wash config put. @brooksmtownsend is planning on taking this.
• The wash scale and wash start commands for components do not have support for specifying a configuration, this will be fixed in the next wash alpha release. fix/wash alpha fixes #1889
• The components in the wasmCloud quickstart are pinned to WASI logging / cloud versions @0.1.0, while the host is pinned to @0.2.0-draft. @brooksmtownsend is updating these templates now. (fixed in fix(examples): Hello world component examples #1856)
• The wasmCloud dashboard was not updated by wash v0.27.0-alpha.2, but it is updated in Update wash ui to be compatible with wasmCloud 1.0 #1857 and will be released in the next alpha version of wash.
• The TypeScript example included in our quickstart is failing to fully write the outgoing body, you should still see a response but the component might hang indefinitely. Use of wasi-http fails to fully finish writing the body bytecodealliance/ComponentizeJS#99. Fixed in fix(example): typescript hello world hang #1911
• If you previously ran a version of wadm and updated to this version, your streams may be out of date. We should provide [FEATURE] Provide simple way to reset/wipe wadm store/s #1740 in the next alpha version of wash. fix: ensure streams have updated subjects wadm#262 and wadm v0.11.0-alpha.3 include patches for these issues.

Possible feature adds

Though the release candidate is meant to denote a line where no new features or breaking changes are implemented, I'd like to call out a couple of possible beneficial changes to make before we draw the line in the stability sand

• Refactor and streamlining of the keyvalue interfaces is a significantly nicer-to-use API for keyvalue which is one of our core capabilities in wasmCloud. This would both make the component API nicer for examples and applications, and reduce our immediate maintenance burden with an adapter. @rvolosatovs and @thomastaylor312 are both interested parties here. [FEATURE] update to latest wasi-keyvalue #1859. Implemented in feat(runtime): update wasi:keyvalue in runtime #1863

Please let us know if there are any issues or rough edges that you run into while testing! We're available here and on the wasmCloud Slack.

[rvolosatovs]

Refs #1859

[ricochet]

It looks like I have the pre-1.0 wadm when I install with this wash rc. I was expecting this to be bundled in with the rc and my wash up (thanks to #1853).

# clean slate
wash drain all
rm -r ~/.wash

cargo install --git https://github.com/wasmCloud/wasmCloud --tag wash-cli-v0.27.0-alpha.2 --jobs 4 wash-cli

# start and host and check we're all good
wash up
wash get inventory

# follow quick start
rustup target add wasm32-wasi
wash new component hello --template-name hello-world-rust
cd hello
wash config put default-http address=127.0.0.1:8080
wash build

# errors with wadm
wash app deploy wadm.yaml

Could not put manifest to deploy Validation Error:
Should be able to parse object at: spec/components/ at index: 0
Please check for missing or incorrect elements

# check version
wash --version
wash 0.27.0-alpha.2

[brooksmtownsend]

🤔 You should have the v0.11.0-alpha.2 wadm with the alpha of wash, I wonder if this is an issue relating to the above need of a wash drain for wadm streams

[ricochet]

I don't actually know if I needed to drain, I was just trying to get to a super-duper clean slate and didn't want to forget adding any context here for how I did that.

[brooksmtownsend]

Oh! Yes the validation error is a bug. It's fixed in #1856

[brooksmtownsend]

@ricochet if you can retry from wash new component, see how that works out for you

[ricochet]

Works!

[thomastaylor312]

list_keys for wasi:keyvalue is not yet implemented

[thomastaylor312]

Looks like @rvolosatovs added this in #1876

[rvolosatovs]

Yes, also closed #1743

[brooksmtownsend]

As far as small developer experience improvements, here's the list I was able to compile from my journey through all 4 of our quickstarts:

wasmcloud:

• Similar to how we allow overwriting of component references for components, we should do the same things for providers fix(host): allow overwriting provider reference #1909
• The HTTP server provider still seems to fail the periodic health check, ensure we aren't msgpack serializing the httpserver health check [BUG] HTTPServer provider reports a failed health check #1925
• The error message for linking to a component on the wrong interface is unintuitive and appears more like a panic, consider at least logging a nicer error on the host side [FEATURE] Improve error output for incorrectly configured links. #1927

wash:

• Remove the ? from wash app history output (the header) fix/wash alpha fixes #1889
• Left-align the "Host Inventory" header from wash get inventory fix/wash alpha fixes #1889
• Update the dashboard version @lachieh Washboard and websockets #1890
• Rename configuration block in wasmcloud.toml from [actor] to [component], keeping the name backwards compatible for deserialization purposes. fix/wash alpha fixes #1889
• wash down should remove the pidfile for the host even if disconnected
• wash link del should have a nicer way of specifying the interface instead of --namespace <namespace> --package <package>. Strawman would be wash link del <component_id> <wit>. So instead of wash link del component --namespace wasi --package http, it would be wash link del component wasi:http. [FEATURE] Add a wit positional argument to wash link del #1926
• Enable websockets by default Washboard and websockets #1890

wadm:

• Consider a nicer error message for fetching links when the only host in a lattice stops (fails with no responders, as expected. Not a huge deal)
• Build the component ID based on the manifest name and the component name, not the sanitized reference (way too long) fix: calculate component ID from model and name wadm#259
• Fix bug where when deploying a new manifest old components (just wasm components) are not stopped Fixes from alpha2 testing, bump to alpha3 wadm#261
• The wadm link scaler should react to the deleted event Fixes from alpha2 testing, bump to alpha3 wadm#261
• Rename the ID of the spreadscaler from actor to component

Folks should feel free to fix these if they see them, but I'm going to come back later today / this week to just knock a bunch of them out

[lachieh]

Could you add "enable websocket by default with option to disable" to the wash section

[brooksmtownsend]

Now that you fixed websockets, we need to make sure to remember to change docs

• Update wasmcloud dashboard port to 4223 wasmcloud.com#370

[lachieh]

@brooksmtownsend should merge wasmCloud/wasmcloud.com#371 after the next wash RC and then we can close that too 👍🏻

[brooksmtownsend]

Just a note that for anyone updating wadm, the correct command to resolve issues involves recreating the mirror stream. I may try and patch this into wadm.

nats stream del wadm_mirror --force
nats kv del wadm_state host_default

The latter kv del I'm fixing with a backwards compatible deserialize in wadm.

This is because of the change to the wadm event topics, which previously listened for all events on wasmbus.evt.* but now listens on wasmbus.evt.*.>

[brooksmtownsend]

wasmCloud/wadm#262 resolves this and with wadm v0.11.0-alpha.3 both of these issues will be fixed.

[ricochet]

Should the actor crate be renamed? https://github.com/wasmCloud/wasmCloud/tree/main/crates/actor

[brooksmtownsend]

Yes, probably to something like wasmcloud_component_sdk. It's not a huge issue for now as we don't use the crate in our examples, since it alters the way Rust looks compared to other components, but we should rename it and use it more

[brooksmtownsend]

All of the above fixes should be released into the next version of wash (v0.27.0-alpha.3).

• wasmCloud 1.0.0-rc.2, which includes the updated wasi-keyvalue implementations
• wadm v0.11.0-alpha.3, which includes bug fixes as listed above
• wash-lib v0.20.0-alpha.2, which includes bug fixes as listed above

[thomastaylor312]

wasmCloud 1.0.0-rc.2 and wadm v0.11.0-alpha.3 have been cut

[thomastaylor312]

wash-lib-v0.20.0-alpha.2 also has been cut

[brooksmtownsend]

• As identified in feat(providers): implement OTEL tracing for HTTP server provider #1878 we need to ensure that our providers are e2e implemented with tracing, which @vados-cosmonic is tackling