From 7fa2a607579aff26e05597dfbf41b1c7f2d86e05 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Viktor=20Sz=C3=A9pe?= Date: Wed, 15 Jan 2025 20:36:20 +0000 Subject: [PATCH 1/9] Fix typos MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Viktor Szépe --- .../index.mdx | 2 +- .../index.mdx | 2 +- .../index.mdx | 2 +- .../index.mdx | 2 +- .../index.mdx | 2 +- .../index.mdx | 2 +- .../index.mdx | 2 +- .../index.mdx | 2 +- community/2023-02-01-community-meeting.mdx | 2 +- community/2023-05-10-community-meeting.mdx | 2 +- community/2023-06-21-community-meeting.mdx | 2 +- community/2023-07-12-community-meeting.mdx | 2 +- community/2023-08-02-community-meeting.mdx | 2 +- community/2023-09-20-community-meeting.mdx | 2 +- community/2023-09-27-community-meeting.mdx | 2 +- community/2023-10-04-community-meeting.mdx | 2 +- community/2023-10-18-community-meeting.mdx | 4 +-- community/2023-11-15-community-meeting.mdx | 2 +- community/2023-11-29-community-meeting.mdx | 2 +- community/2024-02-21-community-meeting.mdx | 2 +- community/2024-02-27-community-meeting.mdx | 6 ++-- community/2024-03-06-community-meeting.mdx | 2 +- community/2024-05-08-community-meeting.mdx | 2 +- community/2024-05-15-community-meeting.mdx | 2 +- community/2024-06-12-community-meeting.mdx | 4 +-- community/2024-06-20-community-meeting.mdx | 2 +- community/2024-07-31-community-meeting.mdx | 2 +- community/2024-08-07-community-meeting.mdx | 4 +-- community/2024-08-14-community-meeting.mdx | 6 ++-- community/2024-08-21-community-meeting.mdx | 8 ++--- community/2024-08-28-community-meeting.mdx | 4 +-- community/2024-09-11-community-meeting.mdx | 2 +- community/2024-09-25-community-meeting.mdx | 2 +- community/2024-10-02-community-meeting.mdx | 4 +-- community/2024-10-16-community-meeting.mdx | 14 ++++---- community/2024-10-30-community-meeting.mdx | 6 ++-- community/2024-11-06-community-meeting.mdx | 10 +++--- community/2024-11-27-community-meeting.mdx | 4 +-- community/2024-12-04-community-meeting.mdx | 8 ++--- community/2024-12-11-community-meeting.mdx | 6 ++-- community/2024-12-26-community-meeting.mdx | 6 ++-- .../Component/sqldb-postgres-query/index.md | 2 +- docs/cli/wash.mdx | 6 ++-- docs/concepts/applications.mdx | 2 +- docs/concepts/index.mdx | 2 +- docs/contributing/contributing-guide.mdx | 2 +- docs/deployment/deployment-guide/index.mdx | 2 +- .../observability-with-opentelemetry.mdx | 2 +- docs/deployment/security/secrets.mdx | 2 +- docs/developer/workflow.md | 4 +-- docs/ecosystem/wash/plugin-developer.md | 4 +-- docs/installation.mdx | 6 ++-- docs/reference/cloud-event-list.mdx | 2 +- docs/reference/glossary.md | 2 +- docs/reference/wasi/incoming-http.md | 32 +++++++++---------- docs/reference/wasi/interfaces.md | 4 +-- docs/reference/wasi/wrpc-interfaces.md | 4 +-- docs/roadmap/2024-q1.md | 2 +- docs/roadmap/2024-q2.md | 2 +- docs/roadmap/2024-q3.md | 2 +- docs/roadmap/index.md | 4 ++- .../_components/what-is-wasmcloud/index.tsx | 2 +- src/pages/privacy-policy/index.mdx | 2 +- versioned_docs/version-0.82/cli/dev.md | 2 +- versioned_docs/version-0.82/cli/new.md | 4 +-- .../version-0.82/concepts/applications.mdx | 2 +- .../developer/providers/consuming.md | 2 +- .../version-0.82/ecosystem/wadm/model.md | 2 +- .../wasmbus/interfaces/code-generation.md | 2 +- .../abis/wasmbus/interfaces/tips/index.md | 2 +- .../hosts/lattice-protocols/rpc.md | 2 +- versioned_docs/version-0.82/hosts/security.md | 4 +-- versioned_docs/version-0.82/installation.mdx | 6 ++-- .../reference/cloud-event-list.md | 4 +-- .../reference/official-oci/index.md | 2 +- .../reference/wasi/incoming-http.md | 32 +++++++++---------- .../version-0.82/reference/wasi/interfaces.md | 32 +++++++++---------- versioned_docs/version-0.82/roadmap/index.md | 2 +- writing-styles/Microsoft/Avoid.yml | 4 +-- 79 files changed, 172 insertions(+), 170 deletions(-) diff --git a/blog/2022-05-23-deploying-wasmcloud-actors-from-github-packages/index.mdx b/blog/2022-05-23-deploying-wasmcloud-actors-from-github-packages/index.mdx index 6dd43e49..948e242d 100644 --- a/blog/2022-05-23-deploying-wasmcloud-actors-from-github-packages/index.mdx +++ b/blog/2022-05-23-deploying-wasmcloud-actors-from-github-packages/index.mdx @@ -1,5 +1,5 @@ --- -title: 'Deploying wasmCloud Actors from Github Packages' +title: 'Deploying wasmCloud Actors from GitHub Packages' image: './images/github-packages.png' date: "2022-05-23" authors: [brooksmtownsend] diff --git a/blog/2022-05-25-wasmcloud-capabilities-are-managed-algebraic-effects-for-webassembly-functions/index.mdx b/blog/2022-05-25-wasmcloud-capabilities-are-managed-algebraic-effects-for-webassembly-functions/index.mdx index 1e2697df..1e00bef6 100644 --- a/blog/2022-05-25-wasmcloud-capabilities-are-managed-algebraic-effects-for-webassembly-functions/index.mdx +++ b/blog/2022-05-25-wasmcloud-capabilities-are-managed-algebraic-effects-for-webassembly-functions/index.mdx @@ -24,7 +24,7 @@ This function is _"pure"_. For every input of `x` there is only one output. In m Unfortunately, the second we expand our code beyond the realm of "hello world", it becomes more and more difficult to maintain purity. Our code needs to interact with the world, and it often does so in messy, unpredictable ways. Even if it isn't messy, we frequently see functions where the answer is only predictable for a short period of time. -Let's take a look at this (psuedocode) function from a hypothetical bank back-end that handles an international withdrawal from a customer's account: +Let's take a look at this (pseudocode) function from a hypothetical bank back-end that handles an international withdrawal from a customer's account: ``` internationalWithdrawal account amount localCurrency = diff --git a/blog/2022-06-16-webassembly-components-and-wasmcloud-actors-a-glimpse-of-the-future/index.mdx b/blog/2022-06-16-webassembly-components-and-wasmcloud-actors-a-glimpse-of-the-future/index.mdx index 2ec68913..3b528225 100644 --- a/blog/2022-06-16-webassembly-components-and-wasmcloud-actors-a-glimpse-of-the-future/index.mdx +++ b/blog/2022-06-16-webassembly-components-and-wasmcloud-actors-a-glimpse-of-the-future/index.mdx @@ -91,7 +91,7 @@ Here are what the interfaces look like: ``` // These are importing some common types that you see in the receive function signature. See the -// actual code on Github if you are curious what these types look like +// actual code on GitHub if you are curious what these types look like use * from error-type use * from wasmbus-common diff --git a/blog/2023-06-07-wasmtime-a-standardized-runtime-for-wasmcloud/index.mdx b/blog/2023-06-07-wasmtime-a-standardized-runtime-for-wasmcloud/index.mdx index bbb3f88a..8cf90fa7 100644 --- a/blog/2023-06-07-wasmtime-a-standardized-runtime-for-wasmcloud/index.mdx +++ b/blog/2023-06-07-wasmtime-a-standardized-runtime-for-wasmcloud/index.mdx @@ -13,7 +13,7 @@ The world of WebAssembly (Wasm) runtimes has evolved quickly over the last coupl {/* truncate */} -As part of the continued effort to align wasmCloud with WASI standards and the component model, we've made a considered shift to Wasmtime for a couple of important reasons. Firsly, Wasmtime lives at the cutting edge of the Wasm ecosystem. It is the runtime used in a slew of major projects, and has been adopted by [Shopify, Fastly, Fermyon, Microsoft, and more](https://bytecodealliance.org/articles/wasmtime-1-0-fast-safe-and-production-ready). We're incredibly lucky to be able to participate with them as our friends and teammates in the Bytecode Alliance, where the Wasmtime project is hosted. +As part of the continued effort to align wasmCloud with WASI standards and the component model, we've made a considered shift to Wasmtime for a couple of important reasons. Firstly, Wasmtime lives at the cutting edge of the Wasm ecosystem. It is the runtime used in a slew of major projects, and has been adopted by [Shopify, Fastly, Fermyon, Microsoft, and more](https://bytecodealliance.org/articles/wasmtime-1-0-fast-safe-and-production-ready). We're incredibly lucky to be able to participate with them as our friends and teammates in the Bytecode Alliance, where the Wasmtime project is hosted. With flexibility and choice in mind, we've also re-architected the way that we pull in Wasmtime so that we can use _other_ types of runtimes that work well in tiny places. We haven't started that work yet, but we've been sure to design for it. diff --git a/blog/2024-04-10-wasm-day-summary-blog/index.mdx b/blog/2024-04-10-wasm-day-summary-blog/index.mdx index 43b4ef9d..88c4f2a7 100644 --- a/blog/2024-04-10-wasm-day-summary-blog/index.mdx +++ b/blog/2024-04-10-wasm-day-summary-blog/index.mdx @@ -38,7 +38,7 @@ For the latest and greatest in Wasm standards and innovation, and a practical gu ## [Pathfinder to GPU Offload in WASM](https://www.youtube.com/watch?v=3G9kANTKjmQ&list=PLj6h78yzYM2MQteKoXxICTWiUdZYEw6RI&index=4)—Atanas Atanasov & Aaron Dorney, Intel -It's an exciting time for companies at the cutting edge of embedded systems and devices. Atanas and Aaron's talk gives a sense of the opportunity companies like Intel are identifying in bringing Wasm to embedded systems. Speficially, this demo-laden talk questions why we would want GPU offload in the Wasm ecosystem and takes a closer look at the tools available right now to achieve this. +It's an exciting time for companies at the cutting edge of embedded systems and devices. Atanas and Aaron's talk gives a sense of the opportunity companies like Intel are identifying in bringing Wasm to embedded systems. Specifically, this demo-laden talk questions why we would want GPU offload in the Wasm ecosystem and takes a closer look at the tools available right now to achieve this. According to Adanas and Aaron, there are two major use cases for GPU offload in Wasm. The first is when working with AI/ML as a service, the second rendering as a service. This makes sense when considering the associated deployment targets; standalone desktop apps, cloud apps in resource-constrained environments, applications running in browsers and node js. All these environments rely on low-latency and high performance. This is something that containers struggle with—as the team describes, the overhead of spinning up a container is not conducive to these use cases. diff --git a/blog/2024-04-18-wasmcloud-1.0-webassembly-apps-production-any-cloud-any-edge/index.mdx b/blog/2024-04-18-wasmcloud-1.0-webassembly-apps-production-any-cloud-any-edge/index.mdx index c272b4bb..1b6ae77e 100644 --- a/blog/2024-04-18-wasmcloud-1.0-webassembly-apps-production-any-cloud-any-edge/index.mdx +++ b/blog/2024-04-18-wasmcloud-1.0-webassembly-apps-production-any-cloud-any-edge/index.mdx @@ -65,7 +65,7 @@ Since wasmCloud supports custom interfaces written with the community-standard i - You might also want to see our [**blog on why WASI 0.2 is such a big deal**](/blog/wasi-preview-2-officially-launches). -- If you're new to components, WASI, and the wider WebAssembly ecosystem, check out our [**Concepts documention**](/docs/concepts) to get up to speed—the [**Components**](/docs/concepts/components) page is a great place to start. +- If you're new to components, WASI, and the wider WebAssembly ecosystem, check out our [**Concepts documentation**](/docs/concepts) to get up to speed—the [**Components**](/docs/concepts/components) page is a great place to start. ## Completely OTEL observable diff --git a/blog/2024-07-16-how-to-virtualize-webassembly-components-with-wasi-virt/index.mdx b/blog/2024-07-16-how-to-virtualize-webassembly-components-with-wasi-virt/index.mdx index 0f63b31c..deaa3f03 100644 --- a/blog/2024-07-16-how-to-virtualize-webassembly-components-with-wasi-virt/index.mdx +++ b/blog/2024-07-16-how-to-virtualize-webassembly-components-with-wasi-virt/index.mdx @@ -138,7 +138,7 @@ world root { export example:pong/pingpong; } ``` -The new component exports `pingpong` but no longer imports `wasi:cli/environment`—that requirement has been abstracted awat. If we run this component on wasmCloud, the host will be able to satisfy the `random` import—it will simply require another component to invoke it via the `pingpong` interface. +The new component exports `pingpong` but no longer imports `wasi:cli/environment`—that requirement has been abstracted away. If we run this component on wasmCloud, the host will be able to satisfy the `random` import—it will simply require another component to invoke it via the `pingpong` interface. In the `http-hello2` directory is a modified `http-hello-world` component that imports the `pingpong` interface and calls for a string from `pong` to append to the hello world message. Navigate to that directory and build the component. diff --git a/blog/2024-08-27-wasmcloud-1.2-improved-streams-automatic-config-updates/index.mdx b/blog/2024-08-27-wasmcloud-1.2-improved-streams-automatic-config-updates/index.mdx index 95147a12..41281ef0 100644 --- a/blog/2024-08-27-wasmcloud-1.2-improved-streams-automatic-config-updates/index.mdx +++ b/blog/2024-08-27-wasmcloud-1.2-improved-streams-automatic-config-updates/index.mdx @@ -27,7 +27,7 @@ Capability providers using the latest provider SDK will now be able to [subscrib Capability providers implementing `wrpc:blobstore` are **strongly recommended** to update to the latest version (`0.2.0`) in order to take advantage of blobstore async streaming. The host will remain backwards compatible with `wrpc:blobstore@0.1.0` for at least a minor release. -See https://github.com/wasmCloud/wasmCloud/pull/2779 for three implementation examples (Fileystem, Amazon S3, and Azure Blobstore) to see the best path for upgrading. We’ve updated and released each of these providers, so make sure to update your wadm manifests when possible: +See https://github.com/wasmCloud/wasmCloud/pull/2779 for three implementation examples (Filesystem, Amazon S3, and Azure Blobstore) to see the best path for upgrading. We’ve updated and released each of these providers, so make sure to update your wadm manifests when possible: - [ghcr.io/wasmcloud/blobstore-azure:0.4.0](http://ghcr.io/wasmcloud/blobstore-azure:0.3.0) - [ghcr.io/wasmcloud/blobstore-fs:0.9.0](http://ghcr.io/wasmcloud/blobstore-fs:0.9.0) diff --git a/community/2023-02-01-community-meeting.mdx b/community/2023-02-01-community-meeting.mdx index ba70c269..5bdc8543 100644 --- a/community/2023-02-01-community-meeting.mdx +++ b/community/2023-02-01-community-meeting.mdx @@ -33,7 +33,7 @@ date: 2023-02-01 - Been keen to get started since Slack started discussing testing actors with Dagger. - Focused on end-to-end integration tests rather than unit tests right now. - Also working on a way to mock the lattice which he'll use for unit tests eventually. -- Dagger allows you to take your CI/CD pipelines and run them identically, locally as you would in Github action or anywhere else. +- Dagger allows you to take your CI/CD pipelines and run them identically, locally as you would in GitHub action or anywhere else. - This is pretty cool as one of the biggest pain points occurs when testing code at work, then trying to test later at home or in github - these are completely different test structures which causes confusion. - Demo shows wash new echo actor - build, sign, inspect, name and then call. - What's really cool is a call test on the actor which allows me to do some sanity checking. I.e. that it's functioning. diff --git a/community/2023-05-10-community-meeting.mdx b/community/2023-05-10-community-meeting.mdx index 95f3372f..78eff5d4 100644 --- a/community/2023-05-10-community-meeting.mdx +++ b/community/2023-05-10-community-meeting.mdx @@ -84,7 +84,7 @@ date: 2023-05-10 - It'd be more unpredictable which would be an even bigger problem than security. - Link names can't change since the actor needs them - Brooks: It's interesting - - Jochen: Is this a limitation of NATS or a chosen path? since it can only receive on single paht but listen on a \*? + - Jochen: Is this a limitation of NATS or a chosen path? since it can only receive on single path but listen on a \*? - Brooks: It's more of a chosen path -- we use a different links (frotend and backend) to get around that, so we're flexible in routing. - Brooks: We're trying to find a way for linking to be more natural - Most of the time there's not even configuration required (ex. HTTP Client is just making outbound requests, versus HTTP Server which _might_ need a port to listen on) diff --git a/community/2023-06-21-community-meeting.mdx b/community/2023-06-21-community-meeting.mdx index 6a4b7a98..bd6518e3 100644 --- a/community/2023-06-21-community-meeting.mdx +++ b/community/2023-06-21-community-meeting.mdx @@ -18,7 +18,7 @@ date: 2023-06-21 - We had a problem with the observability of wasmCloud capability providers. In particular, official capability providers and example actors that we publish to Azure Container Registry. - The issue? Azure CR does not support unauthenticated dynamic content discovery so it's tricky to track versions. - We had a workaround - the Capability Provider Repo and shields.io badges. We've been using a dynamic json badge - using their API to provide a custom payload. -- Issue: Readme in Github - markdown does not have ability to run customer code - no auto-update. +- Issue: Readme in GitHub - markdown does not have ability to run customer code - no auto-update. - Last week we ran with an idea proposed by Jordan: capitalizing on the Azure Container Registry webhook - allows you to call version data after it pushes a new image version to Azure CR. - From here we can see the latest information and use the Key-Value contract to save this information in the KV store. - We also set up categories in order to fetch all the official capability provider data - name, OCI URL, actors. diff --git a/community/2023-07-12-community-meeting.mdx b/community/2023-07-12-community-meeting.mdx index 72f0fd68..7d17e3cc 100644 --- a/community/2023-07-12-community-meeting.mdx +++ b/community/2023-07-12-community-meeting.mdx @@ -19,7 +19,7 @@ date: 2023-07-12 - Starting point: identify in wit what wasmcloud's RPCbus looks like - [PR in wasmCloud interfaces](https://github.com/wasmCloud/interfaces/pull/116). - If you were to pull up the smithy version of our core contract it maps pretty much 1:1 (with a few possible future exceptions). - With the provider SDK in Go we can convert any wasmCloud interfaces on Tiny Go into core Go interfaces. -- If we were to take the Bytecode Allliance wit-bindgen binary in the Github repo and run it over a wit file we would be able to replace smithy. +- If we were to take the Bytecode Allliance wit-bindgen binary in the GitHub repo and run it over a wit file we would be able to replace smithy. - Demo is still work in progress but it funnels in 2 parts: - Provider and an actor running in wasmCloud with no more smithy IDL interface pieces generated. - You can see in NATS that the 30-second health check is running - ping pong provider running/ We can query the actor (you say ping, we say pong). diff --git a/community/2023-08-02-community-meeting.mdx b/community/2023-08-02-community-meeting.mdx index 0e06a0bd..0b299233 100644 --- a/community/2023-08-02-community-meeting.mdx +++ b/community/2023-08-02-community-meeting.mdx @@ -39,7 +39,7 @@ date: 2023-08-02 - This is an exciting time as we have componentized wasmCloud in line with these new standard and the soon-to-be-finalized Component Model. - As we move towards WasmCon in September, stay tuned for more detail on the wasmCloud blog. - As you know any open source project is going through constant change but we now have a high level wasmCloud roadmap. Currently in review by docs maintainers. -- Find the relevant pages on our [docs site](https://wasmcloud.com/docs/roadmap). Also a continously updated [GitHub Project](https://github.com/orgs/wasmCloud/projects/7/views/3). +- Find the relevant pages on our [docs site](https://wasmcloud.com/docs/roadmap). Also a continuously updated [GitHub Project](https://github.com/orgs/wasmCloud/projects/7/views/3). - Loosely pinned to q3 and q4 of 2023. ### Goals: diff --git a/community/2023-09-20-community-meeting.mdx b/community/2023-09-20-community-meeting.mdx index 95dc7689..8326115f 100644 --- a/community/2023-09-20-community-meeting.mdx +++ b/community/2023-09-20-community-meeting.mdx @@ -51,7 +51,7 @@ date: 2023-09-20 - Rust Host lost some of that introspection. - Info on number of actors providers invocations that have a particular provider or actor. - Interesting summary stats around specific resource usage: so we can more accurately scale actors up and down. - - Provider exposing metrics - counter for number of 500s/400s is pretty common. We want to be able to do the same thing in wasmCoud. + - Provider exposing metrics - counter for number of 500s/400s is pretty common. We want to be able to do the same thing in wasmCould. - Some work to do to decide how, but this is where we're leaning. - [Observability and metrics RFC](https://github.com/wasmCloud/wasmCloud/issues/664) - please get involved if you have expertise - we're excited to hear your opinions and experiences. - Check out the recording for the full discussion. diff --git a/community/2023-09-27-community-meeting.mdx b/community/2023-09-27-community-meeting.mdx index 260f1cdf..84768541 100644 --- a/community/2023-09-27-community-meeting.mdx +++ b/community/2023-09-27-community-meeting.mdx @@ -35,7 +35,7 @@ Welcome to our new community members Marcelo Lopez and Mfon! 🎉 - Note: wasmCloud processes are limited by executing for 2 seconds by default, overridable by the `WASMCLOUD_RPC_TIMEOUT_MS` variable. - Recommended additional reading: [Dealing with the Diabolical Distributed Deadline Dilemma](https://kevinhoffman.blog/post/distributed_deadlines/) -- Timeout is usually configured at runtime. Whatever value you state, that's how long wasmCloud will allow a chain to execute - nested timout. +- Timeout is usually configured at runtime. Whatever value you state, that's how long wasmCloud will allow a chain to execute - nested timeout. - wasmCloud is a distributed system capable of running on one or many machines. As such, it's hard to tell whether an operation is taking a long time because it's timing out versus a process that will never finish because it has made requests that it will never return. - Example: downloading a file can take an arbitrary amount of time depending on the quality of the network, how big the file is etc. We limit execution types, and infinite timeout, with the timeout kill switch. - Discussion diff --git a/community/2023-10-04-community-meeting.mdx b/community/2023-10-04-community-meeting.mdx index 1b42565f..4313481e 100644 --- a/community/2023-10-04-community-meeting.mdx +++ b/community/2023-10-04-community-meeting.mdx @@ -28,7 +28,7 @@ date: 2023-10-04 ### DISCUSSION: Hacktoberfest! 🎃 - 10th year of Digital Ocean's event. [Hacktoberfest.com](http://Hacktoberfest.com) brings together open source maintainers who are eligible to designate their open source project for Hacktoberfest. -- All you need to do is to close or have 4 approved pull requests on Github or GitLab. +- All you need to do is to close or have 4 approved pull requests on GitHub or GitLab. - One you have this, DigitalOcean will plant a tree on your behalf and send you a nice virtual badge. - All you need to do if you want to partake is sign up on the website. - On the wasmCloud side we'll designate our good issues and some stretch issues with the goal to lower the barrier to people are getting started in Wasm. diff --git a/community/2023-10-18-community-meeting.mdx b/community/2023-10-18-community-meeting.mdx index 48fab608..b69149a4 100644 --- a/community/2023-10-18-community-meeting.mdx +++ b/community/2023-10-18-community-meeting.mdx @@ -46,7 +46,7 @@ date: 2023-10-18 - We went over the [kvcounter demo](https://github.com/wasmCloud/examples/tree/main/actor/kvcounter-wasmcon2023) Rust code - After building actors with `wash build`, we can inspect the resulting Wasm module with `wash inspect` - If we use `wasm-tools component wit` on the web assembly component that is built to see the imports and exports that are expected. -- The host expects the interface that WASI provides here, so components that run on it must provie those. +- The host expects the interface that WASI provides here, so components that run on it must provide those. - You can use the `just run-actor` in the repo to do some of the local things that are possible there (use `just` to see a list of available commands) #### Question: how does the code look like? (Kevin) @@ -94,7 +94,7 @@ It's a custom function that's written but it's necessary to write the HTTP respo - The [Host Metrics RFC](https://github.com/wasmCloud/wasmCloud/issues/664) is a great example, thanks to Patrick for putting it up - The last time we commented on this was - While we have a process around RFCS to propose, accept & close -- we don't have an official process for moving something from proposed to accepted. -- It would be a good idea for maintainers in the relevant project to vote on accepted RFCs to move them from proposed to acepted. +- It would be a good idea for maintainers in the relevant project to vote on accepted RFCs to move them from proposed to accepted. - Once it's been accepted, we could push the RFC through to the roadmap. - What we're going to ask Patrick to do (like other RFC proposers) is to put a comment tagging relevant maintainers to ask for approval after a couple of rounds for discussion. - To somewhat formalize it we can specify something like "2 maintainers have to approve". diff --git a/community/2023-11-15-community-meeting.mdx b/community/2023-11-15-community-meeting.mdx index 1ae48df6..a35d3dcc 100644 --- a/community/2023-11-15-community-meeting.mdx +++ b/community/2023-11-15-community-meeting.mdx @@ -20,7 +20,7 @@ date: 2023-11-15 - We have a bunch of new control interface topics/features that we'd like to discuss. We'd like to get some feedback on them before we merge them into main. - First up is the ability to adjust labels on actors. This is a feature that both allows for - scheduling (letting wadm make scheduing decisions) and for features like drain/cordon/lame duck + scheduling (letting wadm make scheduling decisions) and for features like drain/cordon/lame duck mode. - There is a possible security concern, but Kevin pointed out that other tech like Kubernetes doesn't have an answer to this either. There could be other edge cases diff --git a/community/2023-11-29-community-meeting.mdx b/community/2023-11-29-community-meeting.mdx index c2eb8254..1c3ff45e 100644 --- a/community/2023-11-29-community-meeting.mdx +++ b/community/2023-11-29-community-meeting.mdx @@ -48,7 +48,7 @@ date: 2023-11-29 - Jochan Rau: We implement a data processing actor - using messaging. In linkdef we need to give the creds. We could use key value store but it's more meta level and not really the responsibility of the actor to know where the creds are stored. Is there a way to make this easier and make sure our creds are protected? - Secrets management strategy has been discussed and there is a stale RFC for a basic level of secrets config. - Our answer right now is to use a providers like the Hashicorp Vault implementation in order to store secrets. - - The big question around that is if you need to send the secret over the wire. E.g. pull out Github secret to send over HTTP - will go over NATS in the current methodology and expose sensitive data. + - The big question around that is if you need to send the secret over the wire. E.g. pull out GitHub secret to send over HTTP - will go over NATS in the current methodology and expose sensitive data. - We'll bring up this RFC again - tokenization on the linkdef is important. More to come on this in the coming months. - Team to sync with Jochen in Slack. - There was plenty of additional discussion and plenty of insight from Victor, so check out the recording below. diff --git a/community/2024-02-21-community-meeting.mdx b/community/2024-02-21-community-meeting.mdx index 8e4b434c..e91f407e 100644 --- a/community/2024-02-21-community-meeting.mdx +++ b/community/2024-02-21-community-meeting.mdx @@ -43,7 +43,7 @@ date: 2024-02-21 ### COMMUNITY DISCUSSION AND Q&A - Colin: Fuzzing (send random bits and see if it creates fatal errors). - - Fuzzing in rust unless you want to stand up the entire wasmCoud host every time, it's hard to call a specific function without standing everything up. + - Fuzzing in rust unless you want to stand up the entire wasmCould host every time, it's hard to call a specific function without standing everything up. - Limitations of macros on top of macros. - Mock All - most commonly used. - Anyone have any familiarity mocking/fuzzing in Rust? diff --git a/community/2024-02-27-community-meeting.mdx b/community/2024-02-27-community-meeting.mdx index 7ebedc76..2b27d3e1 100644 --- a/community/2024-02-27-community-meeting.mdx +++ b/community/2024-02-27-community-meeting.mdx @@ -38,7 +38,7 @@ Q&A: - **Jochen**: Provider vs component - this is a little confusing. - The way we think of provider is a privileged actor - one is stateless (components) and one is stateful (providers). Stateful - connection pools, machine learning models. Long-lived elements. - Privileged actor— we are looking into how we store creds or secret info in the link - clear text is a little tricky. - - Yes! We have some updates there. Now, when you put a linkdef you're not posting the full config map as part of the linkdef - you're linking a source to a target and providing a list of names for config that the source or target may beed. We so this by pulling he config from an external location. + - Yes! We have some updates there. Now, when you put a linkdef you're not posting the full config map as part of the linkdef - you're linking a source to a target and providing a list of names for config that the source or target may be. We so this by pulling he config from an external location. - Designed to be more flexible and reusable. We may not always want to store this type of into in jetstream - we may want to pull config from K8s to satisfy a component link, or a secret store and - Tooling will look similar - we will have an easy way of assoc and designing config. More to come here soon. @@ -49,9 +49,9 @@ Q&A: ### DISCUSSION: Quick check-in on the [1.0 roadmap](https://wasmcloud.com/docs/roadmap/) -- You can see the detail [in Github here](https://github.com/orgs/wasmCloud/projects/7/views/8) +- You can see the detail [in GitHub here](https://github.com/orgs/wasmCloud/projects/7/views/8) - We have completed a ton of work over the last few weeks. The major focus is getting wRPC in place and operational. -- Next and ready for work comes with removing some of the claims signing. All discernable with WIT and linked together at runtime. +- Next and ready for work comes with removing some of the claims signing. All discernible with WIT and linked together at runtime. - We are well on the road to the release of 1.0! ## Community Updates diff --git a/community/2024-03-06-community-meeting.mdx b/community/2024-03-06-community-meeting.mdx index 5dc839df..19196029 100644 --- a/community/2024-03-06-community-meeting.mdx +++ b/community/2024-03-06-community-meeting.mdx @@ -36,7 +36,7 @@ date: 2024-03-06 ### DISCUSSION: Progress in the 1.0 roadmap -- Review where we are in the roadmap [here](https://wasmcloud.com/docs/roadmap/)! And in [Github](https://github.com/orgs/wasmCloud/projects/7/views/8). +- Review where we are in the roadmap [here](https://wasmcloud.com/docs/roadmap/)! And in [GitHub](https://github.com/orgs/wasmCloud/projects/7/views/8). - Lots of progress has been made in the last week alone to get us closer to 1.0. - Completed: Deprecated Wasmbus is a good first issue—we have made some small modifications. - There are a couple of open RFCs open for contribution—thank you to the community for your support. diff --git a/community/2024-05-08-community-meeting.mdx b/community/2024-05-08-community-meeting.mdx index b2f80a54..c3e4862b 100644 --- a/community/2024-05-08-community-meeting.mdx +++ b/community/2024-05-08-community-meeting.mdx @@ -40,7 +40,7 @@ date: 2024-05-08 - Thank you to all the community for your contributions to the roadmap discussion, and the suggestions seen since. Our [Q2 high level goals](https://github.com/orgs/wasmCloud/projects/7/views/10) are updated and ready to view. - Several notable new RFCs in the plan which are priorities for the next season. -- New documentation, new feature and improvement buckets can be [viewed in Github](https://github.com/orgs/wasmCloud/projects/7). +- New documentation, new feature and improvement buckets can be [viewed in GitHub](https://github.com/orgs/wasmCloud/projects/7). - As community members looking to contribute, scan the good first issues as the starting point. ### DISCUSSION: cargo smart-release in wasmCloud/wasmCloud diff --git a/community/2024-05-15-community-meeting.mdx b/community/2024-05-15-community-meeting.mdx index 678afae3..8c80a2a6 100644 --- a/community/2024-05-15-community-meeting.mdx +++ b/community/2024-05-15-community-meeting.mdx @@ -27,7 +27,7 @@ date: 2024-05-15 - DAN: There is another side to the discussion: build attestation. - GitHub artifact attestation is now in public beta and so, along with SigStore, we wanted to do something similar with wasmCloud, integrated with GitHub. - GitHub Action to attest builds. Attestation is different to signing as it deals with the CI/CD pipelines: "You can trust that this pipeline was the one that built the application." -- In the Github UI, you can build, verify, sign and attest any build. +- In the GitHub UI, you can build, verify, sign and attest any build. - The name of the certification is the pipeline tag where it originated. - Both the SigStore and GitHub Build Attestation demos were pretty quick to implement due to the [Policy Service](https://wasmcloud.com/docs/deployment/security/policy-service) in wasmCloud, which is as flexible as you want it to be. diff --git a/community/2024-06-12-community-meeting.mdx b/community/2024-06-12-community-meeting.mdx index d1f23cf7..70b193a6 100644 --- a/community/2024-06-12-community-meeting.mdx +++ b/community/2024-06-12-community-meeting.mdx @@ -39,9 +39,9 @@ date: 2024-06-12 ### DISCUSSION: Tracing/OTLP issue in wasmCloud - We noticed a couple of issues with trace propagation - we updated to a newer version of the downstream OTLP crate we use for wasmCloud and that did change the behaviour of URL provision for exports. -- If you are overriding your endpoint this shoudn't affect you but this is something we fixed in the host so that based on the URL you provide will append the v1 or cut it off (GRPC endpoint). +- If you are overriding your endpoint this shouldn't affect you but this is something we fixed in the host so that based on the URL you provide will append the v1 or cut it off (GRPC endpoint). - Lands in the next patch of the host or wasmCloud 1.1. -- Ritesh - tracing enpoint propogation issue. Thank you so much for the flag. +- Ritesh - tracing endpoint propagation issue. Thank you so much for the flag. - Bug fix for NATS also included. - New versions of all capability providers will absorb these changes. diff --git a/community/2024-06-20-community-meeting.mdx b/community/2024-06-20-community-meeting.mdx index 3dc3715d..4a4a7dfb 100644 --- a/community/2024-06-20-community-meeting.mdx +++ b/community/2024-06-20-community-meeting.mdx @@ -36,7 +36,7 @@ Welcome also [Matthew Cascio](https://www.linkedin.com/in/mcascio) - knows of us - When we interact with a key-value store, we will use the wasi-kv store to open a bucket and call operations on that bucket. This allows us to increment an object value. - When Massoud introduced us to his implementation, we decided to think about the role of a bucket in wasmCloud. When we think of the interaction from the NATS key-value perspective, NATS key-value has a notion of a store, where there are buckets that are opened individually and where we have a collection of keys and values. - wasmCloud concept - link names - logically separate piece of configuration for relationship between a component and a provider. -- Link name as specified as the bucket - binding an identifier to a specific key-vaue store, defined at runtime - easier to understand and preserves vendor neutrality. +- Link name as specified as the bucket - binding an identifier to a specific key-value store, defined at runtime - easier to understand and preserves vendor neutrality. - Link name = unique ID to specific connection between a capability and the things that consume it. A unique link name collects all the info needed to configure and connect multiple providers in the same interface. And swap in/out dynamically. - This a wide-ranging discussion and so we recommend diving into the recording below. diff --git a/community/2024-07-31-community-meeting.mdx b/community/2024-07-31-community-meeting.mdx index ab499534..e36e5ecd 100644 --- a/community/2024-07-31-community-meeting.mdx +++ b/community/2024-07-31-community-meeting.mdx @@ -44,7 +44,7 @@ title: 'Meeting Agenda - 2024-07-31' - WASI 0.2.1 is coming this week. In wasmCloud, we will get this as an update to wasmtime. - Users won't need to update anything on component, provider, or host side. - The main feature coming in WASI 0.2.1 is feature gates, allowing you to provide features "**since**" a certain version in the WIT. -- This way, you'll know if your runtime supports a new feature before instatiation. +- This way, you'll know if your runtime supports a new feature before instantiation. - Bailey: It will probably be a couple of weeks for wasmtime to update and then for us to consume that within wasmCloud. The other thing to note is that we've added a lot more documentation inside of WASI interfaces themselves. ## Weekly highlights diff --git a/community/2024-08-07-community-meeting.mdx b/community/2024-08-07-community-meeting.mdx index 0556ed56..3efc7c0c 100644 --- a/community/2024-08-07-community-meeting.mdx +++ b/community/2024-08-07-community-meeting.mdx @@ -54,8 +54,8 @@ title: 'Meeting Agenda - 2024-08-07' ### Issue of the Week - [FEATURE: Add --secrets-topic and --policy-topic flags + env vars to wash up](https://github.com/wasmCloud/wasmCloud/issues/2631) -- This is a great first issueLooking at contrubyting ot a CLI - especially the command line interface in wash. -- Enviroment variables and flags. +- This is a great first issueLooking at contributing to a CLI - especially the command line interface in wash. +- Environment variables and flags. - Shout out to the community for picking up our earlier Issues of the Week! Thank you to all our contributors! - Also, a huge shout out *Ahmed* to our newest maintainer and has written a quarter of the `wadm` project. Thank you so much! diff --git a/community/2024-08-14-community-meeting.mdx b/community/2024-08-14-community-meeting.mdx index 56120e04..1efdf4c6 100644 --- a/community/2024-08-14-community-meeting.mdx +++ b/community/2024-08-14-community-meeting.mdx @@ -19,9 +19,9 @@ title: 'Meeting Agenda - 2024-08-14' - As always, it's difficult to share the demo goodness in notes so check out the recording below. - `wash spy` provides a component provider ID; how it is running in wasmcloud. -- This subscribes to all the invocations - if youre dubugging a component and looking at what is going over the lattice - it's a great command to get an entire readout, allows us to focus in on an individual component. +- This subscribes to all the invocations - if your dubugging a component and looking at what is going over the lattice - it's a great command to get an entire readout, allows us to focus in on an individual component. - We have 2 apps deployed - echo and K-V counter - Brooks shows what it looks like to spy on a component. -- We can send a request to the topic that the comonent is subscribed on - e.g. hello there - we can see what wash was able to synthesize. +- We can send a request to the topic that the component is subscribed on - e.g. hello there - we can see what wash was able to synthesize. - We noticed the message isn't that useful - we found out that this is a remnant from when we encoded the paylaods with message pack - we now use the standard Wasm component encoding proposal - how wRPC works over the lattice. - Brooks shows how we've updated the `wash spy` command and what it looks like now to spy on the invocations of a component - sounds bad, good for debugging! - We have a ton of great debugging features in `wash` - worth checking out. @@ -32,7 +32,7 @@ title: 'Meeting Agenda - 2024-08-14' - These improvements are focused on the Rust provider SDK - 1 will also come to Go. - Thanks to Victor for updating capability provider configuration - in wasmCloud 1.2 we will have support for configuration updates. Provide a certificate for a provider to connect, or a token. - We will file an issue on the Go Provider SDK shortly. -- On the Provider SDK in Rust: when we delete a link in a provider we would hand you the source ID of the componejt if you're targeted wth a link. We now provide a more fulsome set of information for deleteing a link. +- On the Provider SDK in Rust: when we delete a link in a provider we would hand you the source ID of the componejt if you're targeted with a link. We now provide a more fulsome set of information for deleting a link. - This means you'll gave more robust information re. what the link is - source, target, link name - without these it's difficult to make capability providers multi-tenant so this is a useful way to resolve this challenge. - Provider SDK in Rust - breaking change - release notes to follow. diff --git a/community/2024-08-21-community-meeting.mdx b/community/2024-08-21-community-meeting.mdx index 20ed8dff..ee8d0d09 100644 --- a/community/2024-08-21-community-meeting.mdx +++ b/community/2024-08-21-community-meeting.mdx @@ -20,10 +20,10 @@ title: 'Meeting Agenda - 2024-08-21' - As always, it's difficult to express the goodness of Brooks's demo in notes and so please check out the recording below! - Affectionately referred to as Little Blobby Tables in the wasmCloud ecosystem, this is a implementation of a file system using `wasi-http` and 'wasi-blobstore' standand interfaces. Essentially, this is an example of a reusable component that can be deployed with any http or blobstore to generate a file system. -- Historically, we have used a system of blocking reads and writes - we have been working on the `wasi-blobstore` implemetation in wasmCloud, fixed a couple of bugs and improved the way streaming works over wRPC. +- Historically, we have used a system of blocking reads and writes - we have been working on the `wasi-blobstore` implementation in wasmCloud, fixed a couple of bugs and improved the way streaming works over wRPC. - This is a perfect example of streaming data from 2 different interfaces and how nice it is when you can provide implementations with a standard language library. Also a great examples of how great it feels to work with these WASI constructs. - WASI crate being used directly in pretty much all our Rust examples, with a huge amount of work happening in the Go community. -- In wasmCloud 1.2.0 we'll have the ability to strean data with WASI - more on that soon. +- In wasmCloud 1.2.0 we'll have the ability to stream data with WASI - more on that soon. - Liam: this opens up a whole host of new possibilities. For example, we could now use stremaing algorithms for analysing the data. E.g. calculate shot 1 for each streaming file. - Follow along with the demo and a much broader discussion in the recording! @@ -48,7 +48,7 @@ Roman's Resources: ### Issue of the Week - [[FEATURE] move wasmcloud.toml to a different directory for a tinygo component](https://github.com/wasmCloud/wasmCloud/issues/2757) - - Addition to wash library and wash CLI - there is already support in Rust where you can put the wasmCloud toml in a different diretory to where you're building the component, + - Addition to wash library and wash CLI - there is already support in Rust where you can put the wasmCloud toml in a different directory to where you're building the component, - For tinygo this doesn't work - we expect for that - but this feature will allow you to put this piee of metadata in a different file to improve the experience for TinyGo. - Being able to put metadata into a build folder should be super useful. - This is a great first issue to get started! @@ -57,7 +57,7 @@ Roman's Resources: - [wash-cli autogenerated documentation](https://wasmcloud.com/docs/cli/wash) - One of the best updates we've seedn in a while - check it out! - - We noticed the command line docs we had for wash a were outdated. Keeping ahead of all our changes was a challege. + - We noticed the command line docs we had for wash a were outdated. Keeping ahead of all our changes was a challenge. - Now we can autogenerate updates for each command, which will ensure all minor release are captured and adopted across the entire ecosystem (e.g. adding and removing command line flags). - Uses clap markdown, the implemnentation is not yet merged but will be soon! diff --git a/community/2024-08-28-community-meeting.mdx b/community/2024-08-28-community-meeting.mdx index 2ab5a4f8..b9f1d437 100644 --- a/community/2024-08-28-community-meeting.mdx +++ b/community/2024-08-28-community-meeting.mdx @@ -24,9 +24,9 @@ title: 'Meeting Agenda - 2024-08-28' - In focus: `wasi-blobstore` streaming has seen a whole suite of improvements; manifests are better. Suggest checking out the [blobby example](https://github.com/wasmCloud/wasmCloud/blob/04d7e8e902ec27dcc20e1deeb222574554166ad1/examples/rust/components/blobby/README.md?plain=1#L4) to see how this works in practice. - This closes out all the remaining issues in the Q2 roadmap. - In wash 0.31 we have a couple of great improvements - as always check out the recording for Brooks's demo. -- FEATURE: If you output the version for wash we now get the version and the embeded default versions of NATS, wadm and wasmCloud that wash will utilize. This is super useful in the command line - easy to do wash version and get all the versions needed by wash. +- FEATURE: If you output the version for wash we now get the version and the embedded default versions of NATS, wadm and wasmCloud that wash will utilize. This is super useful in the command line - easy to do wash version and get all the versions needed by wash. - FEATURE: improvements to the tables that we output in the command line. wash app lists - instead of having many separate fields, we have the description listed below the app and have streamlined the information there. -- We have also updated the way we output to the terminal so we don't exceed the width of the terminal, which helps wth consistency. +- We have also updated the way we output to the terminal so we don't exceed the width of the terminal, which helps with consistency. - FEATURE: Thank you for your work [Aditya Salunkhe](https://github.com/Aditya1404Sal) in enabling us to watch the status of wash app lists - instant refresh allows us to reconcile before compiling. - FEATURE: We have a much improved wash status view. We can see a lot more information about the application and its inner state. When we query the wash app status, we can now see why it might not reconcile - infinitely more helpful. diff --git a/community/2024-09-11-community-meeting.mdx b/community/2024-09-11-community-meeting.mdx index 6dc741c3..367c9b06 100644 --- a/community/2024-09-11-community-meeting.mdx +++ b/community/2024-09-11-community-meeting.mdx @@ -26,7 +26,7 @@ title: 'Meeting Agenda - 2024-09-11' - We can use this if we want to use a standard wasm component in Go. This is the workflow that we would use. - Go-native, essentially an idiomatic way to build Go-native WebAssembly components. - The one we currently have in wasmCloud generates Go and C files - that’s pretty much how wit-bindgen works today. -- If we look at components that use wit-bindgen Go, you’ll see a diff set of files that wil be 100% Go - C doesn’t get a look in. +- If we look at components that use wit-bindgen Go, you’ll see a diff set of files that will be 100% Go - C doesn’t get a look in. - We are now using a different bindgen that is hosted in ByteCode Alliance tools. - How will this change things? - If we take a look at the interface names, there’s a lot of text - code that is hard to read. diff --git a/community/2024-09-25-community-meeting.mdx b/community/2024-09-25-community-meeting.mdx index ec8d9a24..1e96cdbb 100644 --- a/community/2024-09-25-community-meeting.mdx +++ b/community/2024-09-25-community-meeting.mdx @@ -44,7 +44,7 @@ title: 'Meeting Agenda - 2024-09-25' - Upcoming changes to wash build. This started as a way to build components in languages that wasmCloud knows - Rust, TinyGo etc. - One specific aspect will improve - the way we build source code to a Wasm component, this [Rust toolchain blog](https://blog.rust-lang.org/2024/04/09/updates-to-rusts-wasi-targets.html) is a good reference point. -- As we move forward we have just updated to the latest verson of wash to use Rust's `wasm32-wasip1` target, then proceeding with adapting the module to a Wasm component +- As we move forward we have just updated to the latest version of wash to use Rust's `wasm32-wasip1` target, then proceeding with adapting the module to a Wasm component - Once `wasm32-wasip2` is included in the stable toolchain (works in nightly today!), we'll update wash to use this directly. - TinyGo components will also compile to the `wasip2` target, which means we can use native TinyGo to build directly to a component. - Targeting P2 will be the standard default when you're running wash build. diff --git a/community/2024-10-02-community-meeting.mdx b/community/2024-10-02-community-meeting.mdx index a8c874fb..aaa0c582 100644 --- a/community/2024-10-02-community-meeting.mdx +++ b/community/2024-10-02-community-meeting.mdx @@ -25,7 +25,7 @@ title: 'Meeting Agenda - 2024-10-02' - Our new [Developer Guide](https://wasmcloud.com/docs/category/developer-guide) now has a [Go-specific](https://wasmcloud.com/docs/developer/languages/go/components) testing guide (under Languages), and we'll continue to build out our language-specific resources in the coming months. - The guide details everything you need to do to get started. It starts with new Go component code which can be used alongside the wit-bindgen and WAdge toolset (preliminary information there right now, but we will expand in the coming weeks). - Brooks shows off some of the new tooling coming down the line in wash. E.g. Init function and implementation of a wasi-http transport for Go's http library. -- It's worth reminding ourselves that wash dev is a powerful addtion to the toolbox. wash dev is a muti-facted feature that allows us to build, review our dependencies and create the declaritive manifest. +- It's worth reminding ourselves that wash dev is a powerful addition to the toolbox. wash dev is a multi-facted feature that allows us to build, review our dependencies and create the declarative manifest. - Thank you to everyone who has worked hard to get this working. In particular, everyone on the Tinygo side pushing WASI P2 as a target, our internal maintainers and community contributors. - Maahir: what about Wasm adoption and big code spaces? Is it being adopted by giants or just in testing phase? - Brooks mentions the upcoming [WasmCon conference](https://events.linuxfoundation.org/wasmcon/program/schedule/) that features many wasmCloud adopters. We also have several user stories published on the [CNCF](https://www.cncf.io/blog/2024/08/23/wasmcloud-on-the-factory-floor-efficient-and-secure-processing-of-high-velocity-machine-data/) and [wasmCloud](https://wasmcloud.com/blog/tm-forum-webassembly-canvas-project-in-phase-2) blogs. @@ -49,7 +49,7 @@ title: 'Meeting Agenda - 2024-10-02' ### DISCUSSION: [wasmCloud Q4 2024 Roadmap](https://github.com/wasmCloud/wasmCloud/discussions/3119) - Next week (9th Oct) we will have a special community board to plan our Q4 activities. A great opp to look at where we can make the most impact for our users and community. -- Check in on our [Github disussion](https://github.com/wasmCloud/wasmCloud/discussions/3119) to suggest features, prioritize fixes, and to brainstorm priorities for the next phase of development. +- Check in on our [GitHub discussion](https://github.com/wasmCloud/wasmCloud/discussions/3119) to suggest features, prioritize fixes, and to brainstorm priorities for the next phase of development. - Our previous roadmap focused on community contributions, improving developer workflows, and finalizing some support for WASI interfaces. Based on the discussion next week, we'll determine our next roadmap's focus. - Please feel free to comment whether you're a long-time wasmCloud user, maintainer, first-time contributor, or just curious onlooker that noticed something we should do. diff --git a/community/2024-10-16-community-meeting.mdx b/community/2024-10-16-community-meeting.mdx index 591ccf30..6d63e7f5 100644 --- a/community/2024-10-16-community-meeting.mdx +++ b/community/2024-10-16-community-meeting.mdx @@ -25,10 +25,10 @@ title: 'Meeting Agenda - 2024-10-16' - We will be publishing a developer blog post with all the details shortly so keep an eye on the wasmCloud blog and social channels. - wash dev is the major update in 1.3 which provides a way for us to review component dependencies in full. - [Release notes](https://github.com/wasmCloud/wasmCloud/releases/tag/v1.3.0) are tagged along with the 1.3 release. -- Notably, we have introduced a new validation path for links. Earlier, you cauld have an http server provider forwarded to components based on a path. We used ot be able to do this with the same inteface without specifying a link name - this is now invalid. -- What must be present to create a link from the same source o multipe targes, you must soecufy the kink name - a unuqie idejtifier for calling a specific target at runtime, -- Works by extenson for cap providers - htto triggered by an external handler. -- Wasm componet context requires additional identifcation layer. +- Notably, we have introduced a new validation path for links. Earlier, you cauld have an http server provider forwarded to components based on a path. We used to be able to do this with the same interface without specifying a link name - this is now invalid. +- What must be present to create a link from the same source o multiple targes, you must soecufy the kink name - a unuqie idejtifier for calling a specific target at runtime, +- Works by extension for cap providers - htto triggered by an external handler. +- Wasm component context requires additional identification layer. - Check out the recording for [Massoud's](https://github.com/wasmCloud/wasmCloud/blob/main/examples/rust/components/keyvalue-messaging/src/lib.rs) example - a great way to demo why we need this feature. In your code you can denote you're calling 2 different locations, identified with link names. - Another [example in our documentation}(https://wasmcloud.com/docs/concepts/linking-components/linking-at-runtime/#defining-and-using-link-names) for a guide to using links. @@ -38,16 +38,16 @@ title: 'Meeting Agenda - 2024-10-16' - V1 - wadm and wasnckoud are both binaries and crates. As such, we can start a wasmcloud host and wadm but embedded in wash. - When we run wash up, once we've ensured we are running NATS locally, wadm and wasmCloud can run within the same process as wash. - Why is this important? This allows us to handle errors better and make it easier to short-circuit runtime errors. -- It ensures there are no runaway proceses and it's quicker, 2 less binaries to download from Github. +- It ensures there are no runaway processes and it's quicker, 2 less binaries to download from GitHub. - Jordis: what is driving this, are there quick wins to push readiness? Comment: getting ahead on docs that provide visual simplicity is desired. -- Brooks: The origin started in realizing it can be frictionful to download through Github - proxies cause issues for enterprises. We want to make it easier to work locally with less requirements for external access - tricky when there's poor connectivity, esp if you're being asked to take more steps. +- Brooks: The origin started in realizing it can be frictionful to download through GitHub - proxies cause issues for enterprises. We want to make it easier to work locally with less requirements for external access - tricky when there's poor connectivity, esp if you're being asked to take more steps. - There was a much broader discussion, check out the recording for the full discussion. ### DISCUSSION: [wasmCloud Q4 roadmap](https://github.com/wasmCloud/wasmCloud/discussions/3119) - Last week we did our Q4 roadmapping session which was super productive. -- The [Q4 roadmap](https://github.com/orgs/wasmCloud/projects/7/views/12) is now live in Github projects, with a host of good first issues in triage. +- The [Q4 roadmap](https://github.com/orgs/wasmCloud/projects/7/views/12) is now live in GitHub projects, with a host of good first issues in triage. - In the Ready for Work section, you'll see we have a higher ratio of good first issues - perfect for those who are looking to get started. - We have already started on a number of Q4 issues and so check out the [repo](https://github.com/orgs/wasmCloud/projects/7/views/12) for all the details. - For Q4 we will be prepping for WasmCon + KubeCon, taking place in Salt Lake City in 3.5 weeks. We'll be there in force and so be sure to stop along our Project Booth on the Wednesday 13th November. diff --git a/community/2024-10-30-community-meeting.mdx b/community/2024-10-30-community-meeting.mdx index 84a9c4d6..30e97435 100644 --- a/community/2024-10-30-community-meeting.mdx +++ b/community/2024-10-30-community-meeting.mdx @@ -31,7 +31,7 @@ title: 'Meeting Agenda - 2024-10-30' ### DEMO: `wasmcloud_component` HTTP wrappers -- This is V2 of the components crate which incudes HTTP wrapper. +- This is V2 of the components crate which includes HTTP wrapper. - This was spurred by improved support for Wasm P1/P2 on a stable toolchain in Rust - this means it is a much nicer experience when starting and compiling with or without `wash build`. - Brooks shows what the experience looks and feels like now the Rust toolchain is a little more mature. - This has now been published to our documentation as a template. @@ -46,7 +46,7 @@ title: 'Meeting Agenda - 2024-10-30' - `wkg` manages WIT dependencies packaged as **OCI artifacts** which means any organization that already has an OCI registry can access, store and call standard WIT interfaces. - Now available in wash 0.36.0! - `wkg` is now used directly in wash - very exciting as this means it automatically manages your dependencies - declared in a WIT world. -- You just run `wash build` and it will automagically fetch the dependencies required - locked insde a wasmcloud.lock file. +- You just run `wash build` and it will automagically fetch the dependencies required - locked inside a wasmcloud.lock file. - This is a great example of how the Wasm component model lends itself to automation by exposing component dependencies from the start. - If you want to convert from `wit-deps` or commit the deps directory in this model and need some assistance, head on over to [Slack](https://wasmcloud.slack.com/). - [Resource](https://docs.rs/wash-lib/0.30.0/wash_lib/parser/struct.WasmcloudDotToml.html#structfield.package_config). @@ -58,7 +58,7 @@ title: 'Meeting Agenda - 2024-10-30' - Time flies when you're a wasmCloud maintainer. We have made some significant progress in the roadmap and you can follow progress [here](https://wasmcloud.com/docs/roadmap/). - Notable issues: we have xloisethe omponet sdk go is already in the wild and we've closed several other issies. - wasmCloud.toml can exist in alternative directories which adds an additional layer of flexibility and repo cleanliness. -- Open PR: host running mutiple lattices. New contributor: working on tab autocomplete for resources in wasmCloud. Human time values - new contribution - super cool. +- Open PR: host running multiple lattices. New contributor: working on tab autocomplete for resources in wasmCloud. Human time values - new contribution - super cool. - New Quickstarts for Rust and Typescript - We are on track to deliver what we wanted to this quarter. If there is anything fokls wannt to take but you need more info, please come and join us on Slack. Or visit [wasmCloud Contribute](https://github.com/wasmcloud/wasmcloud/contribute) which shows all the good first issues to get stuck in. diff --git a/community/2024-11-06-community-meeting.mdx b/community/2024-11-06-community-meeting.mdx index b10cfdc1..adf99ff3 100644 --- a/community/2024-11-06-community-meeting.mdx +++ b/community/2024-11-06-community-meeting.mdx @@ -26,7 +26,7 @@ title: 'Meeting Agenda - 2024-11-06' - He shows an iniitially cloned TinyGo 'hello world' template - [accessible](https://wasmcloud.com/docs/tour/hello-world) through the Quickstart. - The component logic is an http handler which parses the query perameter for naming out of the URL using the Go request type. - We will use the generated wasi key-value bindings to open a key-value store - and we can see our key-value counter demo. -- We're moving towards a world where we can be selective about the interfaces we use, and make them fully configurable for indivdual needs. +- We're moving towards a world where we can be selective about the interfaces we use, and make them fully configurable for individual needs. - Check out the demo in action in the recording below and the wider discussion that ensued. - Kudos to Massoud and Victor for the collaboration and deployment. @@ -35,13 +35,13 @@ title: 'Meeting Agenda - 2024-11-06' - Community Slack - bug reported - there have been a few comments around the Windows developer experience as a dev target for wasmCloud. - In our docs you'll find several tabs that allow you to set up based on what you're using. Toolchains and capability providers etc. - We also run our unit testing on the Windows target. -- We have tried dilgently to keep Windoes as OSS maintained. We have done an OK job but there are some concerns. +- We have tried dilgently to keep Windows as OSS maintained. We have done an OK job but there are some concerns. - For instance: use of chocolatey to run `wash`. - Very few of our maintainers are running on Windows, so we're not exercising these flows in a local environment. - Seeking community feedback on Windows as a dev env. We are keen to support Windows in a better way and so we're looking for feedback on moving Windows to a tier 2 target for developments in the wasmCloud environment. -- Massoud and Aditya: Depends on how many in the comminyt are usign the platform - has to be justified based on need. -- Bailey: Suggest we document how to use WSL - in theory we don't have to do much more but there is definitey a path to success. Potentially depricate our scoop and chocolatey. Set Windows support to community maintained - with WSL recommended for running on Windows. +- Massoud and Aditya: Depends on how many in the community are using the platform - has to be justified based on need. +- Bailey: Suggest we document how to use WSL - in theory we don't have to do much more but there is definitey a path to success. Potentially deprecate our scoop and chocolatey. Set Windows support to community maintained - with WSL recommended for running on Windows. ### DISCUSSION: [WasmCon](https://events.linuxfoundation.org/wasmcon/program/schedule/) and [KubeCon + CloudNativeCon](https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/program/schedule/): the rundown @@ -55,7 +55,7 @@ title: 'Meeting Agenda - 2024-11-06' - [Contribfest](https://kccncna2024.sched.com/overview/type/%F0%9F%9A%A8+Contribfest?iframe=no) sessions are available to all KubeCon attendees and are 90-minute in-person sessions designed to provide projects with the space and resources to tackle outstanding technical debt, security issues, or outstanding impactful feature requests. It is intended to provide a place for maintainers to meet contributors and potential contributors and work together on solving a problem. - We are delighted to have been selected this year - a major deal for us as maintainers and we'd love to see you there! -- This is such an important moment to get in a room wth maintainers, contributors and users to build Wasm components and contribute them to the wider WebAssembly ecosystem. And those who want to contribute to our Rust and Go projects in wasmCloud ecosystem. +- This is such an important moment to get in a room with maintainers, contributors and users to build Wasm components and contribute them to the wider WebAssembly ecosystem. And those who want to contribute to our Rust and Go projects in wasmCloud ecosystem. - This is a great opportunity for us to work with our community to reduce the technical debt and forge a way forward. Come join us, write some code and have some fun! See you there! See you all in Salt Lake City! diff --git a/community/2024-11-27-community-meeting.mdx b/community/2024-11-27-community-meeting.mdx index 0908b8ee..5f15a1bc 100644 --- a/community/2024-11-27-community-meeting.mdx +++ b/community/2024-11-27-community-meeting.mdx @@ -23,9 +23,9 @@ Thanks also to Florian and Massoud for your ongoing support and contributions to ### [Securing software supply chains with SBOMs](https://wasmcloud.com/blog/2024-11-14-secure-your-wasmcloud-supply-chain-with-sboms): what, how, why? -- We’re thinking more deeply about how to secure our software supply chains with SBOMs and Brooks takes us through how we do this in wasmCloud. Check out the handy post on the blog on the subject. In his walkthrough, Brooks explains how there has been a ton of work in this area revolving around tthe idea of tracing back a binary to the original version of the source libraries used to build it. +- We’re thinking more deeply about how to secure our software supply chains with SBOMs and Brooks takes us through how we do this in wasmCloud. Check out the handy post on the blog on the subject. In his walkthrough, Brooks explains how there has been a ton of work in this area revolving around the idea of tracing back a binary to the original version of the source libraries used to build it. -Super important as if there's a vulnerability in a library, an SBOM is there to notify you of the deployments artifacts, infra deployed that rely on that CPE. -- Wasm is different to containrs and so the approach is a little different. As such, we've pulled together a post to explain these differences and how you create an SBOM in wasmCloud with tools like syft and grype. +- Wasm is different to containers and so the approach is a little different. As such, we've pulled together a post to explain these differences and how you create an SBOM in wasmCloud with tools like syft and grype. - You can create an SBOM for components and capabilities alike. - Q: are you defining the use cases? A: this is very much defined by the user. What we're seeing is the enterprises that have the security infrastructure to have the requirement for an SBOM they already have the existing processes to handle it. wasmCloud Policy Service (pluggable policy that adds further constraints) is the natural integration in some use cases. - Check out the recording for the full discussion. diff --git a/community/2024-12-04-community-meeting.mdx b/community/2024-12-04-community-meeting.mdx index 66158728..f2260017 100644 --- a/community/2024-12-04-community-meeting.mdx +++ b/community/2024-12-04-community-meeting.mdx @@ -22,14 +22,14 @@ Welcome [Márk Kővári](https://github.com/markkovari), he is full-stack develo ### Demo: `builtin-http` and `builtin-messaging` - As always it's difficult to cover the joy of our demos and so please check out the recording below. -- PR landed last week - provider builtins. Just as we have native capability providers, we have been thinking about `builtin-http` and `builtin-messaging` providers. Instead of spinning out a seperate binary we delegate the listening on an http port or listen to a NATS message going to the wasmCloud host itself. +- PR landed last week - provider builtins. Just as we have native capability providers, we have been thinking about `builtin-http` and `builtin-messaging` providers. Instead of spinning out a separate binary we delegate the listening on an http port or listen to a NATS message going to the wasmCloud host itself. - There are some key differences and some pros and cons and so Brooks takes us through what's new. -- These new devlopments will come in 1.5. `builtin-http` and `builtin-messaging` are experimental. +- These new developments will come in 1.5. `builtin-http` and `builtin-messaging` are experimental. - Enabling this with Feature Flags - new to the host. We'll cover this later. - In his demo, Brooks shows how the http server image reference is formed of a special syntax for a wasmCloud 'builtin'. We can use this alongside the same configuration we use for native providers. - We do the same thing for the messaging contract. Single function `handle message` is received from a message broker. This is initially built in the wasmCloud message interface but we are also designing for WASI messaging. - The biggest benefit is speed and performance - noticeable. Microseconds versus milliseconds. More to come. -- The downside? Building the provider into the host means if we want to ship a new versiom of the http server or a security patch for the http library we need to ship a new version of the host, rather than a new versiom of the plugin. This is worth consideration if you're thinking of taking advantage of this capability. You can opt in now, but we will make these optional and easy to disable. +- The downside? Building the provider into the host means if we want to ship a new version of the http server or a security patch for the http library we need to ship a new version of the host, rather than a new version of the plugin. This is worth consideration if you're thinking of taking advantage of this capability. You can opt in now, but we will make these optional and easy to disable. - Check out the demo and the wider discussion below. ### Discussion: Feature flags @@ -42,7 +42,7 @@ Welcome [Márk Kővári](https://github.com/markkovari), he is full-stack develo - Scheduling requires Feature Gate specification. As feature matures it progresses from Beta to GA. - This is a way to experiment with new features without making them a requirement, and invite trials within a protected, gated process. Joonas takes us through how this approach works. - Flags exposed by apps themselves? Bailey kicks off an interesting discussion as to how this can be done - check out the recording below. -- Jochen: open feature back end - could be a really cool ecosystem to plug into. Github - most folks using this now. +- Jochen: open feature back end - could be a really cool ecosystem to plug into. GitHub - most folks using this now. - Component wrapping - Luke Wagner's donut model is another exciting evolution and the focus becomes how can we optimize wasmCloud to capitalize. More soon. ### Catch up! diff --git a/community/2024-12-11-community-meeting.mdx b/community/2024-12-11-community-meeting.mdx index 03ed5671..c285e704 100644 --- a/community/2024-12-11-community-meeting.mdx +++ b/community/2024-12-11-community-meeting.mdx @@ -24,10 +24,10 @@ title: 'Meeting Agenda - 2024-12-11' - We're constantly looking at ways to keep track of wasmCloud performance across different versions. Most of the time we run tests locally (for minor versions). The challenge with this is every developer works in different environments. - The way we test on one set of devices (and the results we get) will look vastly different depending on the hardware we're using. - We wanted to create a system in which we can run tests that use a consistent infrastructure, where testing is consistent in terms of a wide range of possible variations. E.g. how many requests; for how long it should run; what are the components and versions we need; if NATS is to be clustered etc. The testing framework needs to allow for these variations. -- We have defined 2 key architectural shapes we see in wasmCloud (based on the most common uses cases) against which we can run multiple tests. We have combined these shapes in a Github repo so we can quickly get a K8s cluster, deploy the benchmarking architecture shape, run many tessts, collect the data, tear it down, and do all that in a cost-effective way. +- We have defined 2 key architectural shapes we see in wasmCloud (based on the most common uses cases) against which we can run multiple tests. We have combined these shapes in a GitHub repo so we can quickly get a K8s cluster, deploy the benchmarking architecture shape, run many tessts, collect the data, tear it down, and do all that in a cost-effective way. - The solution - Testbed - is designed to orchestrate performance tests to the point we can include this benchmarkting in our CI workflow. Lucas takes us through a practical demonstration of how Testbed works. Testbed will be open source in the not-too-distant future. Watch this space for more. Take a look at the recording below for the full session and Q&A. - Q: Colin: what do you see you'll be testing the nost? -- A: RPC transport is part of it. Crucially, HTTP provider/HTTP component - elements that we need to grind on. Also, replicating application behaviour. For instance, where a component that is API garetway is receiving and sending reqests to more than 2 components downstream. Lifecycle handler, logging system etc. Introducing varying numbers of downstream requests and latencies so we mirror behaviours. WASI messaging is a key consideration when we consider testing metholoigies. +- A: RPC transport is part of it. Crucially, HTTP provider/HTTP component - elements that we need to grind on. Also, replicating application behaviour. For instance, where a component that is API garetway is receiving and sending requests to more than 2 components downstream. Lifecycle handler, logging system etc. Introducing varying numbers of downstream requests and latencies so we mirror behaviours. WASI messaging is a key consideration when we consider testing metholoigies. - Also important; mapping individual performance for each transport; TCP, NATS etc. and understanding the performance characteristics of these, which helps us understand where to use different transport types. - Overall more performance benchmarking as a whole - the aim is to get these built into each release so raising the bar on an ongoing basis. Numbers we can depend on. @@ -51,7 +51,7 @@ title: 'Meeting Agenda - 2024-12-11' - WASI control commands are making progress - thanks to our fantastic community contributors for the work there! - Our own Massoud has made serious progress on the NATS object store implementation for wasi-blobstore - thank you Massoud! - Multi-tenancy in wasmCloud has some excellent comments and this will remain a focus going into the New Year. -- CTA - there are a couple of really good first issues that are a perfect starting point for new contributors. If folks are looking to get a feel for how this works, and make a quick conribution, take a look at the [roadmap](https://github.com/orgs/wasmCloud/projects/7/views/12) in Github and tab to Q424! If you want to contribute, just drop a note in the issue! +- CTA - there are a couple of really good first issues that are a perfect starting point for new contributors. If folks are looking to get a feel for how this works, and make a quick conribution, take a look at the [roadmap](https://github.com/orgs/wasmCloud/projects/7/views/12) in GitHub and tab to Q424! If you want to contribute, just drop a note in the issue! - Thank you to every contributor, old and new, for the hard work this year! ### Tune in… diff --git a/community/2024-12-26-community-meeting.mdx b/community/2024-12-26-community-meeting.mdx index c038f39a..f17a634a 100644 --- a/community/2024-12-26-community-meeting.mdx +++ b/community/2024-12-26-community-meeting.mdx @@ -41,7 +41,7 @@ Welcome our new community member, Danesh who has a particular interest in elimin - How does the community feel about the way we maintain templates? Go maintainers looking for us to simplify. - Having a static toml file that points to the templates is more frictionful than is necessary. No objections to templates being in a different repo. Repo for wasmCloud where project templates live. - Lachlan: organizing around languages is good because it's how developers think. We can compare between languages but most of the time the decision is already made. Keeping these pieces together will make it easier to create tooling that is language-specific. Templates and examples the same treatment - examples in my preferred language. wasmcloud/typescript wasmcloud/Go etc. -- Important: unification to make sure that if we use multiple repos they are consistent, Taylor has started on work in Go, to pull changes to docs in Github autonatically to the docs site so they become more easily discoverable. Docs site becomes the authority. The ability to pull in a consistent naming format and having docs that exist alongside the component is powerful. +- Important: unification to make sure that if we use multiple repos they are consistent, Taylor has started on work in Go, to pull changes to docs in GitHub autonatically to the docs site so they become more easily discoverable. Docs site becomes the authority. The ability to pull in a consistent naming format and having docs that exist alongside the component is powerful. - Templates in line with examples, and separation is important as they can be tested in line with their differences. But language specific repos is the ideal. /Go - all things Go. - Check out the recording for the full details and join us on [Slack](https://wasmcloud.slack.com/) to continue the discussion. @@ -56,9 +56,9 @@ Welcome our new community member, Danesh who has a particular interest in elimin ### Open Discussion - [Masoud (@ossfellow)](https://github.com/ossfellow): Using Leptos in the context - demo banking app - front end is using React if data needs to be streamed back to front end how does ut work in that context? -- [Lachlan (@lachieh)](https://github.com/lachieh) It is standard HTTP calls but as far as Leptos is concerned, we belive the front end loads a Wasm module that generates javascript and html that the browser then loads - this calls the Wasm module - RPC call over HTTP, using its own Leptos system protocol. +- [Lachlan (@lachieh)](https://github.com/lachieh) It is standard HTTP calls but as far as Leptos is concerned, we believe the front end loads a Wasm module that generates javascript and html that the browser then loads - this calls the Wasm module - RPC call over HTTP, using its own Leptos system protocol. - Check out this [blogpost on the subject](https://wasmcloud.com/blog/2024-12-10-leptos-and-wasi-0.2-for-full-stack-wasm-development) - Leptos and WASI 0.2 for full-stack Wasm development. -- Review the recording below for the full discusson. +- Review the recording below for the full discussion. - Masoud: What is the status of WASI P3? Looking for something around HTTP2 specifically? wasi-io is tricky. - [Bailey (@ricochet)](https://github.com/ricochet): 1. When we're talking about .3 we are focusing on priorities. Being able to add HTTP2 can happen any time. 2. GRPC is the driver for HTTP2 - consensus has not yet been reached on how we support this, but there are a number of options on the table - separate implementation for HTTP2 is as possibility but no firm decisions as yet. diff --git a/docs/Examples/Go/Component/sqldb-postgres-query/index.md b/docs/Examples/Go/Component/sqldb-postgres-query/index.md index 69d9073c..f279560e 100644 --- a/docs/Examples/Go/Component/sqldb-postgres-query/index.md +++ b/docs/Examples/Go/Component/sqldb-postgres-query/index.md @@ -24,7 +24,7 @@ Before starting, ensure that you have the following installed in addition to the ## 👟 Quickstart -As with all other examples, you can get started quickly by using whe [Wasmcloud SHell +As with all other examples, you can get started quickly by using the [Wasmcloud SHell (`wash`)][wash]. Since `wash` supports declarative deployments (powered by [Wasmcloud Application Deployment Manager diff --git a/docs/cli/wash.mdx b/docs/cli/wash.mdx index d0b9825b..a3d2337b 100644 --- a/docs/cli/wash.mdx +++ b/docs/cli/wash.mdx @@ -1426,7 +1426,7 @@ Generate a wasmCloud component project ###### **Options:** -- `--git ` — Github repository url. Requires 'git' to be installed in PATH +- `--git ` — GitHub repository url. Requires 'git' to be installed in PATH - `--subfolder ` — Optional subfolder of the git repository - `--branch ` — Optional github branch. Defaults to "main" - `-p`, `--path ` — Optional path for template project (alternative to --git) @@ -1448,7 +1448,7 @@ Generate a new capability provider project ###### **Options:** -- `--git ` — Github repository url. Requires 'git' to be installed in PATH +- `--git ` — GitHub repository url. Requires 'git' to be installed in PATH - `--subfolder ` — Optional subfolder of the git repository - `--branch ` — Optional github branch. Defaults to "main" - `-p`, `--path ` — Optional path for template project (alternative to --git) @@ -2087,7 +2087,7 @@ Update a component running in a host to a newer version ###### **Arguments:** - `` — Unique ID of the component to update -- `` — Component reference to replace the current running comonent with, e.g. the absolute file path or OCI URL +- `` — Component reference to replace the current running component with, e.g. the absolute file path or OCI URL ###### **Options:** diff --git a/docs/concepts/applications.mdx b/docs/concepts/applications.mdx index 5f8e309e..ad834958 100644 --- a/docs/concepts/applications.mdx +++ b/docs/concepts/applications.mdx @@ -83,7 +83,7 @@ Application deployment and management is handled by the **wasmCloud Application For an in-depth guide on how wasmCloud manages applications, see [wasmCloud Application Deployment Manager](/docs/ecosystem/wadm/). :::info[Imperative or declarative?] -While wasmCloud supports the imperative management of [components](/docs/concepts/components), [providers](/docs/concepts/providers), and [links](/docs/concepts/linking-components/) (which can be useful for experimentation or debuggging), these are generally considered low-level operations. Declarative application management is generally better-suited to complex distributed applications that can be dynamically adjusted at runtime. +While wasmCloud supports the imperative management of [components](/docs/concepts/components), [providers](/docs/concepts/providers), and [links](/docs/concepts/linking-components/) (which can be useful for experimentation or debugging), these are generally considered low-level operations. Declarative application management is generally better-suited to complex distributed applications that can be dynamically adjusted at runtime. ::: Application models are stored in a NATS key-value bucket and persist beyond a particular host. For more information on how Wadm handles models, see the [reference for the Wadm API](https://wasmcloud.com/docs/ecosystem/wadm/api). diff --git a/docs/concepts/index.mdx b/docs/concepts/index.mdx index 4673ebd9..b5effd5a 100644 --- a/docs/concepts/index.mdx +++ b/docs/concepts/index.mdx @@ -41,7 +41,7 @@ Why use wasmCloud? * The architecture of wasmCloud makes it naturally suited to hybrid clouds and multi-tenant environments, with failover and load balancing that simply works out of the box. -wasmCloud can stand alone *or* run on Kubernetes with the [**wasmCloud Kubernetes operator**](https://github.com/wasmCloud/wasmcloud-operator). Moreover, wasmCloud is designed to integrate with existing cloud native tooling and standards such as OpenTelementry and Open Policy Agent. See [wasmCloud with Kubernetes](/docs/kubernetes/) to learn more. +wasmCloud can stand alone *or* run on Kubernetes with the [**wasmCloud Kubernetes operator**](https://github.com/wasmCloud/wasmcloud-operator). Moreover, wasmCloud is designed to integrate with existing cloud native tooling and standards such as OpenTelemetry and Open Policy Agent. See [wasmCloud with Kubernetes](/docs/kubernetes/) to learn more. ::: ## Exploring the platform diff --git a/docs/contributing/contributing-guide.mdx b/docs/contributing/contributing-guide.mdx index a21fbb26..d105fca2 100644 --- a/docs/contributing/contributing-guide.mdx +++ b/docs/contributing/contributing-guide.mdx @@ -194,7 +194,7 @@ Whether you are a user or contributor, official support channels include: - The GitHub Issues in each subproject repository - [Slack](https://slack.wasmcloud.com/) - - Please note that Slack is meant for help in discussing specific problems or asyncronous + - Please note that Slack is meant for help in discussing specific problems or asynchronous debugging/help. If you are reporting a specific bug, please do so it in GitHub Issues Before opening a new issue or submitting a new pull request, it's helpful to search the project - diff --git a/docs/deployment/deployment-guide/index.mdx b/docs/deployment/deployment-guide/index.mdx index 73c52896..acb19100 100644 --- a/docs/deployment/deployment-guide/index.mdx +++ b/docs/deployment/deployment-guide/index.mdx @@ -21,7 +21,7 @@ This page outlines platforms supported by wasmCloud with the best available depl | **Google Cloud Platform** | Google Kubernetes Engine (GKE) | Yes | [GKE Documentation](https://cloud.google.com/kubernetes-engine/docs/quickstart) | [Deploy wasmCloud on Kubernetes](/docs/deployment/k8s/index.mdx) | | | Google App Engine | Yes | [App Engine Documentation](https://cloud.google.com/appengine/docs) | [Request documentation](https://github.com/wasmCloud/wasmcloud.com/issues/new) | | **Microsoft Azure** | Azure Kubernetes Service (AKS) | Yes | [AKS Documentation](https://learn.microsoft.com/en-us/azure/aks/) | [Deploy wasmCloud on Kubernetes](/docs/deployment/k8s/index.mdx) | -| | Azure Container Instances (ACI) | Yes | [ACI Documentation](https://learn.microsoft.com/en-us/azure/container-instances/) | [Request documentation](https://github.com/wasmCloud/wasmcloud.com/issues/new) | +| | Azure Container Instances (ACPI) | Yes | [ACPI Documentation](https://learn.microsoft.com/en-us/azure/container-instances/) | [Request documentation](https://github.com/wasmCloud/wasmcloud.com/issues/new) | | | Azure App Service | Yes | [App Service Documentation](https://learn.microsoft.com/en-us/azure/app-service/) | [Request documentation](https://github.com/wasmCloud/wasmcloud.com/issues/new) | | | Azure Red Hat OpenShift | Yes | [Azure Red Hat OpenShift Documentation](https://learn.microsoft.com/en-us/azure/openshift/) | [Request documentation](https://github.com/wasmCloud/wasmcloud.com/issues/new) | | **IBM Cloud** | IBM Cloud Kubernetes Service | Yes | [IBM Cloud Kubernetes Service Documentation](https://cloud.ibm.com/docs/containers) | [Deploy wasmCloud on Kubernetes](/docs/deployment/k8s/index.mdx) | diff --git a/docs/deployment/observability/observability-with-opentelemetry.mdx b/docs/deployment/observability/observability-with-opentelemetry.mdx index 48b559b8..98a838dd 100644 --- a/docs/deployment/observability/observability-with-opentelemetry.mdx +++ b/docs/deployment/observability/observability-with-opentelemetry.mdx @@ -93,7 +93,7 @@ The following tools and vendors process logs, metrics, and traces with support f * [Honeycomb](https://www.honeycomb.io/) * [New Relic](https://newrelic.com/) * [Splunk](https://www.splunk.com/) -* Many more—any vendor with OpenTelemetry compatability is supported +* Many more—any vendor with OpenTelemetry compatibility is supported ### Advanced options diff --git a/docs/deployment/security/secrets.mdx b/docs/deployment/security/secrets.mdx index dd5e7c3a..89603b50 100644 --- a/docs/deployment/security/secrets.mdx +++ b/docs/deployment/security/secrets.mdx @@ -90,7 +90,7 @@ This payload is encrypted using the xkey received from the backend's `server_xke } ``` -### Get reponse payload +### Get response payload This payload is encrypted using the xkey provided in the `Wasmcloud-Host-Xkey` header as the recipient. diff --git a/docs/developer/workflow.md b/docs/developer/workflow.md index 4d7b1274..1eaa94a3 100644 --- a/docs/developer/workflow.md +++ b/docs/developer/workflow.md @@ -108,7 +108,7 @@ When run this way, `wash up` will start a single host lattice as normal, but *al ### Easily deploy a wadm application manifest continuously -If you have your host running in a seperate shell/terminal window and want to avoid having to constantly `wash app delete` in-between changes to your project and/or manifest, you can run `wash app deploy` with the `--replace` option: +If you have your host running in a separate shell/terminal window and want to avoid having to constantly `wash app delete` in-between changes to your project and/or manifest, you can run `wash app deploy` with the `--replace` option: ```console wash app deploy --replace path/to/your/wadm.yaml @@ -116,7 +116,7 @@ wash app deploy --replace path/to/your/wadm.yaml Running `wash app deploy` with the `--replace` flag makes wash attempt to delete the application before attempting to deploy it. -Combine this with a tool like [`cargo watch`][cargo-watch] (in the Rust ecosystem) and you can continously re-deploy your manifest any time your Rust project changes: +Combine this with a tool like [`cargo watch`][cargo-watch] (in the Rust ecosystem) and you can continuously re-deploy your manifest any time your Rust project changes: ```console cargo watch -- wash app deploy --replace path/to/your/wadm.yaml diff --git a/docs/ecosystem/wash/plugin-developer.md b/docs/ecosystem/wash/plugin-developer.md index a1e6e2aa..462d8d6f 100644 --- a/docs/ecosystem/wash/plugin-developer.md +++ b/docs/ecosystem/wash/plugin-developer.md @@ -105,7 +105,7 @@ but `wash` will ensure that the return code is 0 if the `run` function returns n non-zero return code if the `run` function returns with an error. A plugin is also allowed to use `wasi:cli/exit` to exit early as well, but this may cause some `wash` cleanup to not run. -A plugin has access to the following resourses while it is running: +A plugin has access to the following resources while it is running: - Stdin - Stdout @@ -168,7 +168,7 @@ variables, or command line flags) in a README or other well-known location. As n sections, all command line options will be added to the autogenerated help text for `wash`. Outside of command line flags, there are generally two ways to configure a CLI: environment -variables or configuration files (or both). Every plugin is given a list of environment varibles +variables or configuration files (or both). Every plugin is given a list of environment variables that are prefixed with `WASH_PLUGIN__`. So if you have a plugin with the id of "foo", any variable with the prefix `WASH_PLUGIN_FOO_` will be available for the plugin to consume. This means that any configuration via environment variables must be done via this naming scheme. diff --git a/docs/installation.mdx b/docs/installation.mdx index 00e191cf..3c9eb1e1 100644 --- a/docs/installation.mdx +++ b/docs/installation.mdx @@ -226,7 +226,7 @@ main () echo -n "Importing packagecloud gpg key... " # import the gpg key curl -fsSL "${gpg_key_url}" | gpg --dearmor > ${gpg_keyring_path} - # grant 644 permisions to gpg keyring path + # grant 644 permissions to gpg keyring path chmod 0644 "${gpg_keyring_path}" # move gpg key to old path if apt version is older than 1.1 @@ -234,7 +234,7 @@ main () # move to trusted.gpg.d mv ${gpg_keyring_path} ${gpg_key_path_old} - # grant 644 permisions to gpg key path + # grant 644 permissions to gpg key path chmod 0644 "${gpg_key_path_old}" # deletes the keyrings directory if it is empty @@ -388,7 +388,7 @@ finalize_yum_repo () echo echo "WARNING: " echo "The pygpgme package could not be installed. This means GPG verification is not possible for any RPM installed on your system. " - echo "To fix this, add a repository with pygpgme. Usualy, the EPEL repository for your system will have this. " + echo "To fix this, add a repository with pygpgme. Usually, the EPEL repository for your system will have this. " echo "More information: https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F" echo diff --git a/docs/reference/cloud-event-list.mdx b/docs/reference/cloud-event-list.mdx index a238b4d4..c19e6281 100644 --- a/docs/reference/cloud-event-list.mdx +++ b/docs/reference/cloud-event-list.mdx @@ -763,4 +763,4 @@ The following events are emitted on a special topic, `wasmbus.rpcevt.{lattice-id | Type | Description | | :-------------------- | :-------------------------- | | `invocation_failed` | An RPC failure notification | -| `invocation_suceeded` | An RPC success notification | +| `invocation_succeeded` | An RPC success notification | diff --git a/docs/reference/glossary.md b/docs/reference/glossary.md index 4ddf380d..7ce7f808 100644 --- a/docs/reference/glossary.md +++ b/docs/reference/glossary.md @@ -64,7 +64,7 @@ For more information, see [**Providers**](/docs/concepts/providers). ### Provider Archive -A provider archive is a compressed file containing a provider's binary (or multiple binaries if multiple architectures are supported) and any other necessary files for distrubution such as claims. Provider archives are used to distribute providers to wasmCloud hosts. +A provider archive is a compressed file containing a provider's binary (or multiple binaries if multiple architectures are supported) and any other necessary files for distribution such as claims. Provider archives are used to distribute providers to wasmCloud hosts. ### `wadm` diff --git a/docs/reference/wasi/incoming-http.md b/docs/reference/wasi/incoming-http.md index 49820060..195d3912 100644 --- a/docs/reference/wasi/incoming-http.md +++ b/docs/reference/wasi/incoming-http.md @@ -105,7 +105,7 @@ corresponding to a clock tick.

subscribe-instant: func

Create a pollable which will resolve once the specified instant -occured.

+occurred.

Params
  • when: instant
    • @@ -117,7 +117,7 @@ occured.

    subscribe-duration: func

    Create a pollable which will resolve once the given duration has elapsed, starting at the time at which this function was called. -occured.

    +occurred.

    Params
    • when: duration
      • @@ -387,7 +387,7 @@ and stream is ready for writing again.

    [method]output-stream.subscribe: func

    Create a pollable which will resolve once the output-stream -is ready for more writing, or an error has occured. When this +is ready for more writing, or an error has occurred. When this pollable is ready, check-write will return ok(n) with n>0, or an error.

    If the stream is closed, this pollable is always ready immediately.

    @@ -450,7 +450,7 @@ let _ = this.check-write(); // eliding error handling

[method]output-stream.splice: func

Read from one stream and write to another.

-

The behavior of splice is equivelant to:

+

The behavior of splice is equivalent to:

  1. calling check-write on the output-stream
  2. calling read on the input-stream with the smaller of the @@ -676,7 +676,7 @@ an input-stream and the delivery of tra and ensures that the user of this interface may only be consuming either the body contents or waiting on trailers at any given time.

    resource future-trailers

    -

    Represents a future which may eventaully return trailers, or an error.

    +

    Represents a future which may eventually return trailers, or an error.

    In the case that the incoming HTTP Request or Response did not have any trailers, this future will resolve to the empty set of trailers once the complete Request or Response body has been received.

    @@ -693,12 +693,12 @@ optional trailers) with a static function that consumes the may not write to the body contents after the body has been finished.

    If the user code drops this resource, as opposed to calling the static method finish, the implementation should treat the body as incomplete, -and that an error has occured. The implementation should propogate this +and that an error has occurred. The implementation should propagate this error to the HTTP protocol by whatever means it has available, including: corrupting the body on the wire, aborting the associated Request, or sending a late status code for the Response.

    resource future-incoming-response

    -

    Represents a future which may eventaully return an incoming HTTP +

    Represents a future which may eventually return an incoming HTTP Response, or an error.

    This resource is returned by the wasi:http/outgoing-handler interface to provide the HTTP Response corresponding to the sent Request.

    @@ -830,7 +830,7 @@ list with the same key.

  3. list<(field-key, field-value)>

    4. [method]fields.clone: func

    -

    Make a deep copy of the Fields. Equivelant in behavior to calling the +

    Make a deep copy of the Fields. Equivalent in behavior to calling the fields constructor on the return value of entries. The resulting fields is mutable.

    Params
    @@ -1041,7 +1041,7 @@ not a syntactically valid uri authority.

    The returned headers resource is immutable: set, append, and delete operations will fail with header-error.immutable.

    This headers resource is a child: it must be dropped before the parent -outgoing-request is dropped, or its ownership is transfered to +outgoing-request is dropped, or its ownership is transferred to another component by e.g. outgoing-handler.handle.

    Params
      @@ -1207,7 +1207,7 @@ This function will trap if the input-stream

    [method]future-trailers.subscribe: func

    Returns a pollable which becomes ready when either the trailers have -been received, or an error has occured. When this pollable is ready, +been received, or an error has occurred. When this pollable is ready, the get method will return some.

    Params
      @@ -1218,7 +1218,7 @@ the get method will return some.

    • own<pollable>

    [method]future-trailers.get: func

    -

    Returns the contents of the trailers, or an error which occured, +

    Returns the contents of the trailers, or an error which occurred, once the future is ready.

    The outer option represents future readiness. Users can wait on this option to become some using the subscribe method.

    @@ -1227,7 +1227,7 @@ once. It will be success on the first call in which the outer option is some, and error on subsequent calls.

    The inner result represents that either the HTTP Request or Response body, as well as any trailers, were received successfully, or that an -error occured receiving them. The optional trailers indicates whether +error occurred receiving them. The optional trailers indicates whether or not trailers were present in the body.

    When some trailers are returned by this method, the trailers resource is immutable, and a child. Use of the set, append, or @@ -1283,7 +1283,7 @@ given is not a valid http status code.

    The returned headers resource is immutable: set, append, and delete operations will fail with header-error.immutable.

    This headers resource is a child: it must be dropped before the parent -outgoing-request is dropped, or its ownership is transfered to +outgoing-request is dropped, or its ownership is transferred to another component by e.g. outgoing-handler.handle.

    Params
      @@ -1342,7 +1342,7 @@ Content-Length.

    [method]future-incoming-response.subscribe: func

    Returns a pollable which becomes ready when either the Response has -been received, or an error has occured. When this pollable is ready, +been received, or an error has occurred. When this pollable is ready, the get method will return some.

    Params
      @@ -1360,8 +1360,8 @@ the get method will return some.

      once. It will be success on the first call in which the outer option is some, and error on subsequent calls.

      The inner result represents that either the incoming HTTP Response -status and headers have recieved successfully, or that an error -occured. Errors may also occur while consuming the response body, +status and headers have received successfully, or that an error +occurred. Errors may also occur while consuming the response body, but those will be reported by the incoming-body and its output-stream child.

      Params
      diff --git a/docs/reference/wasi/interfaces.md b/docs/reference/wasi/interfaces.md index 171df898..6ded1a01 100644 --- a/docs/reference/wasi/interfaces.md +++ b/docs/reference/wasi/interfaces.md @@ -333,7 +333,7 @@ and stream is ready for writing again.

    [method]output-stream.subscribe: func

    Create a pollable which will resolve once the output-stream -is ready for more writing, or an error has occured. When this +is ready for more writing, or an error has occurred. When this pollable is ready, check-write will return ok(n) with n>0, or an error.

    If the stream is closed, this pollable is always ready immediately.

    @@ -396,7 +396,7 @@ let _ = this.check-write(); // eliding error handling

    [method]output-stream.splice: func

    Read from one stream and write to another.

    -

    The behavior of splice is equivelant to:

    +

    The behavior of splice is equivalent to:

    1. calling check-write on the output-stream
    2. calling read on the input-stream with the smaller of the diff --git a/docs/reference/wasi/wrpc-interfaces.md b/docs/reference/wasi/wrpc-interfaces.md index 6420869a..0be9351c 100644 --- a/docs/reference/wasi/wrpc-interfaces.md +++ b/docs/reference/wasi/wrpc-interfaces.md @@ -633,7 +633,7 @@ and stream is ready for writing again.

      [method]output-stream.subscribe: func

      Create a pollable which will resolve once the output-stream -is ready for more writing, or an error has occured. When this +is ready for more writing, or an error has occurred. When this pollable is ready, check-write will return ok(n) with n>0, or an error.

      If the stream is closed, this pollable is always ready immediately.

      @@ -696,7 +696,7 @@ let _ = this.check-write(); // eliding error handling

      [method]output-stream.splice: func

      Read from one stream and write to another.

      -

      The behavior of splice is equivelant to:

      +

      The behavior of splice is equivalent to:

      1. calling check-write on the output-stream
      2. calling read on the input-stream with the smaller of the diff --git a/docs/roadmap/2024-q1.md b/docs/roadmap/2024-q1.md index 5e3bd12b..1ac13a32 100644 --- a/docs/roadmap/2024-q1.md +++ b/docs/roadmap/2024-q1.md @@ -48,7 +48,7 @@ There are many smaller tasks that are included as well, such as [namespacing our ## Diagram -The diagram below shows a loose organization of critical tasks into 3 sections: Stabilizing APIs, WebAssembly standards, and wasmCloud functionality. This roadmap is unordered as each individual task can be completed indepedently, so no rigid order is necessary. The diagram is also not exhaustive, as there are many smaller tasks that are not included. You can view the full-size version [here](/docs/images/2024q1roadmap.png). +The diagram below shows a loose organization of critical tasks into 3 sections: Stabilizing APIs, WebAssembly standards, and wasmCloud functionality. This roadmap is unordered as each individual task can be completed independently, so no rigid order is necessary. The diagram is also not exhaustive, as there are many smaller tasks that are not included. You can view the full-size version [here](/docs/images/2024q1roadmap.png). ![Q1 2024 Roadmap](/docs/images/2024q1roadmap.png) diff --git a/docs/roadmap/2024-q2.md b/docs/roadmap/2024-q2.md index d860ccbd..51b1a398 100644 --- a/docs/roadmap/2024-q2.md +++ b/docs/roadmap/2024-q2.md @@ -45,7 +45,7 @@ Notable issues and RFCs to watch out for, which garnered the most attention duri ## Diagram -The diagram below shows a loose organization of critical tasks into 3 sections: Documentation, New Features and Improvements. This roadmap is unordered as each individual task can be completed indepedently, so no rigid order is necessary. The diagram is also not exhaustive, as there a few smaller tasks that are not included. You can view the full-size version [here](/docs/images/2024q2roadmap.png). This roadmap is also available as a [GitHub Project](https://github.com/orgs/wasmCloud/projects/7/views/10) for consistent updating. +The diagram below shows a loose organization of critical tasks into 3 sections: Documentation, New Features and Improvements. This roadmap is unordered as each individual task can be completed independently, so no rigid order is necessary. The diagram is also not exhaustive, as there a few smaller tasks that are not included. You can view the full-size version [here](/docs/images/2024q2roadmap.png). This roadmap is also available as a [GitHub Project](https://github.com/orgs/wasmCloud/projects/7/views/10) for consistent updating. ![Q2 2024 Roadmap](/docs/images/2024q2roadmap.png) diff --git a/docs/roadmap/2024-q3.md b/docs/roadmap/2024-q3.md index f0d5f608..c01bb07f 100644 --- a/docs/roadmap/2024-q3.md +++ b/docs/roadmap/2024-q3.md @@ -44,7 +44,7 @@ wasmCloud as a project offers the following top features: ## Diagram -This roadmap is unordered as each individual task can be completed indepedently, so no rigid order is necessary. The diagram is also not exhaustive, as there a few smaller tasks that are not included. You can view the full-size and links included version [here](https://excalidraw.com/#json=tAg5TkgH6bvrrq76YGEDb,MERSFwVkfKrrnEk6IXRh4g). This roadmap is also available as a [GitHub Project](https://github.com/orgs/wasmCloud/projects/7/views/11) for consistent updating. +This roadmap is unordered as each individual task can be completed independently, so no rigid order is necessary. The diagram is also not exhaustive, as there a few smaller tasks that are not included. You can view the full-size and links included version [here](https://excalidraw.com/#json=tAg5TkgH6bvrrq76YGEDb,MERSFwVkfKrrnEk6IXRh4g). This roadmap is also available as a [GitHub Project](https://github.com/orgs/wasmCloud/projects/7/views/11) for consistent updating. ![Q3 2024 Roadmap](/docs/images/2024q3roadmap.png) diff --git a/docs/roadmap/index.md b/docs/roadmap/index.md index 5991176e..cbd140d7 100644 --- a/docs/roadmap/index.md +++ b/docs/roadmap/index.md @@ -15,6 +15,7 @@ The 2024 Q4 Roadmap was brainstormed and planned in the [15 Jan 2025 community m ## Retrospective The [2024 Q4 roadmap](/docs/roadmap/2024-q4.md) included many issues that improved the overall experience of developing wasmCloud applications. We called it a "polish quarter" where the primary focus among maintainers and community members was holistic improvement. We made significant progress on the following goals: + - Golang support - Benchmarking and performance improvements - Autogenerated documentation @@ -23,6 +24,7 @@ The [2024 Q4 roadmap](/docs/roadmap/2024-q4.md) included many issues that improv ## Goals We are taking the first quarter of Q1 on with a feeling. This is our most ambitious roadmap yet in terms of features, improvements and documentation. We are focusing on the following goals: + - Expand the list of capability providers for wasmCloud - Simplify the deployment experience on Kubernetes with well-reasoned defaults and recommendations - Track WASI P3 development and release features for prototyping as soon as possible @@ -47,7 +49,7 @@ wasmCloud as a project offers the following top features: ## Diagram -This roadmap is unordered as each individual task can be completed indepedently, so no rigid order is necessary. The diagram is also not exhaustive, as there a few smaller tasks that are not included. This roadmap is also available as a [GitHub Project](https://github.com/orgs/wasmCloud/projects/7/views/13) for consistent updating. Compared to previous roadmaps the community only planned this roadmap using the GitHub project. +This roadmap is unordered as each individual task can be completed independently, so no rigid order is necessary. The diagram is also not exhaustive, as there a few smaller tasks that are not included. This roadmap is also available as a [GitHub Project](https://github.com/orgs/wasmCloud/projects/7/views/13) for consistent updating. Compared to previous roadmaps the community only planned this roadmap using the GitHub project. ## Contributing diff --git a/src/pages/_index/_components/what-is-wasmcloud/index.tsx b/src/pages/_index/_components/what-is-wasmcloud/index.tsx index 3aeb4879..fb9ef123 100644 --- a/src/pages/_index/_components/what-is-wasmcloud/index.tsx +++ b/src/pages/_index/_components/what-is-wasmcloud/index.tsx @@ -65,7 +65,7 @@ const SWITCHER_CONTENT: Array<{ title: 'Integrate with Existing Stacks', description: ( <> - wasmCloud has first-tier support for Kubernetes, AWS, Azure, GCP, Jenkins, Github + wasmCloud has first-tier support for Kubernetes, AWS, Azure, GCP, Jenkins, GitHub Actions, ArgoCD, Backstage, Chainguard, Databases, Messaging, and more. ), diff --git a/src/pages/privacy-policy/index.mdx b/src/pages/privacy-policy/index.mdx index dff0fb8a..98995874 100644 --- a/src/pages/privacy-policy/index.mdx +++ b/src/pages/privacy-policy/index.mdx @@ -796,7 +796,7 @@ The EDAA's opt-out platform [http://www.youronlinechoices.com/](http://www.youro * -The DAA's opt-out platform: [http://optout.aboutads.info/?c=2&lang=EN](http://optout.aboutads.info/?c=2&lang=EN) +The DATA's opt-out platform: [http://optout.aboutads.info/?c=2&lang=EN](http://optout.aboutads.info/?c=2&lang=EN) The opt out will place a cookie on Your computer that is unique to the browser You use to opt out. If you change browsers or delete the cookies saved by your browser, You will need to opt out again. diff --git a/versioned_docs/version-0.82/cli/dev.md b/versioned_docs/version-0.82/cli/dev.md index 06d8cb3c..2a98dba9 100644 --- a/versioned_docs/version-0.82/cli/dev.md +++ b/versioned_docs/version-0.82/cli/dev.md @@ -5,7 +5,7 @@ sidebar_position: 8 description: "wash dev command reference" --- -Starts a local dev loop for an actor. Takes a local `wasmcloud.toml` file to deploy the sepcified actor and accepts a host ID to specify the host to deploy on. This is an experimental feature and needs `--experimental` flag to run. +Starts a local dev loop for an actor. Takes a local `wasmcloud.toml` file to deploy the specified actor and accepts a host ID to specify the host to deploy on. This is an experimental feature and needs `--experimental` flag to run. ### Usage ``` diff --git a/versioned_docs/version-0.82/cli/new.md b/versioned_docs/version-0.82/cli/new.md index cd25741a..fedc5c2b 100644 --- a/versioned_docs/version-0.82/cli/new.md +++ b/versioned_docs/version-0.82/cli/new.md @@ -14,7 +14,7 @@ This command creates a new project from an existing template. A user may create ### `actor` When creating a new actor project, a user may select from the following templates to create a skeleton: -- hello-world-rust: A hello-world actor in Rust thay responds over an HTTP connection +- hello-world-rust: A hello-world actor in Rust that responds over an HTTP connection - hello-world-tinygo: A hello-world actor in TinyGo that responds over an HTTP connection - hello-world-typescript: A hello-world actor in TypeScript that responds over an HTTP connection - hello-world-python: A hello-world actor in Python that responds over an HTTP connection @@ -61,7 +61,7 @@ wash new interface example-project --template-name factorial-interface #### Options The following options can be used for all `wash new` subcommands: -`--git` Github repository url. Requires 'git' to be installed in PATH +`--git` GitHub repository url. Requires 'git' to be installed in PATH `--output` (Alias `-o`) Specify output format (text or json) [default: text] diff --git a/versioned_docs/version-0.82/concepts/applications.mdx b/versioned_docs/version-0.82/concepts/applications.mdx index 9f1b9060..f99eacf3 100644 --- a/versioned_docs/version-0.82/concepts/applications.mdx +++ b/versioned_docs/version-0.82/concepts/applications.mdx @@ -8,7 +8,7 @@ type: 'docs' ## Overview -Applications combine all of the previous concepts into a declarative, deployable unit. wasmCloud supports the imperative management of [actors](/docs/0.82/concepts/actors), [providers](/docs/0.82/concepts/capabilities), and [links](/docs/0.82/concepts/runtime-linking), which can be useful for experimentation or debuggging. However, these are generally considered low-level operations. wasmCloud supports complex distributed applications that can be dynamically adjusted at runtime, and managing a combination of actors, providers, links, and configuration one command at a time quickly becomes unwieldy. +Applications combine all of the previous concepts into a declarative, deployable unit. wasmCloud supports the imperative management of [actors](/docs/0.82/concepts/actors), [providers](/docs/0.82/concepts/capabilities), and [links](/docs/0.82/concepts/runtime-linking), which can be useful for experimentation or debugging. However, these are generally considered low-level operations. wasmCloud supports complex distributed applications that can be dynamically adjusted at runtime, and managing a combination of actors, providers, links, and configuration one command at a time quickly becomes unwieldy. Applications are the primary way to deploy workloads in a wasmCloud [lattice](/docs/0.82/concepts/lattice). Applications are declarative, versioned, defined using a familiar syntax (YAML or JSON), and leverage an [existing manifest standard](https://oam.dev/). Define your app, hit "deploy", and wasmCloud will take care of the rest. diff --git a/versioned_docs/version-0.82/developer/providers/consuming.md b/versioned_docs/version-0.82/developer/providers/consuming.md index 5e615b56..d85e80f7 100644 --- a/versioned_docs/version-0.82/developer/providers/consuming.md +++ b/versioned_docs/version-0.82/developer/providers/consuming.md @@ -33,7 +33,7 @@ One possible design with a better[^1] abstraction might be defining the business We could design this actor to respond to an RPC-style operation called "Checkout" that could be invoked directly by another actor in the lattice, or we could expose an HTTP server operation that handles a POST to the `/cart/{cartId}/checkout` URL, or we could use a `wasmcloud:messaging` capability provider to deliver a message from a subscription that triggers the checkout operation. -For the sake of example, let's take a look at what it might look like to respond directly to a checkout operation via actor-to-actor RPC (this is non-compiling psuedocode): +For the sake of example, let's take a look at what it might look like to respond directly to a checkout operation via actor-to-actor RPC (this is non-compiling pseudocode): ```rust /// perform checkout operation: diff --git a/versioned_docs/version-0.82/ecosystem/wadm/model.md b/versioned_docs/version-0.82/ecosystem/wadm/model.md index c571c4cd..5c28b46a 100644 --- a/versioned_docs/version-0.82/ecosystem/wadm/model.md +++ b/versioned_docs/version-0.82/ecosystem/wadm/model.md @@ -7,7 +7,7 @@ type: 'docs' sidebar_position: 2 --- -The **w**asmCloud **A**pplication **D**eployment **M**anager uses the [Open Application Model](https://oam.dev/) to define application specifications. Because this specification is extensible and platform agnostic, it makes for an ideal way to represent applications with metadata specific to wasmCloud. Don't worry if OAM seems overwhelming, you don't need to know much about it. We're using it as a way of defining application components in a flexible way that's familiar to a lot of people who have been working in the cloud space. +The **w**asmCloud **A**application **D**eployment **M**anager uses the [Open Application Model](https://oam.dev/) to define application specifications. Because this specification is extensible and platform agnostic, it makes for an ideal way to represent applications with metadata specific to wasmCloud. Don't worry if OAM seems overwhelming, you don't need to know much about it. We're using it as a way of defining application components in a flexible way that's familiar to a lot of people who have been working in the cloud space. In this model, an application `specification` is a set of metadata about the app, as well as a list of `components`. Each component within an application is decorated with various `traits`. These core building blocks allow us to make it very easy to define incredibly powerful deployments. wasmCloud defines a number of traits that are specific to our hosts, but let's go through the model from top to bottom. diff --git a/versioned_docs/version-0.82/hosts/abis/wasmbus/interfaces/code-generation.md b/versioned_docs/version-0.82/hosts/abis/wasmbus/interfaces/code-generation.md index 16c91c8e..630bc3ad 100644 --- a/versioned_docs/version-0.82/hosts/abis/wasmbus/interfaces/code-generation.md +++ b/versioned_docs/version-0.82/hosts/abis/wasmbus/interfaces/code-generation.md @@ -42,4 +42,4 @@ templates = "codegen/templates/rust" ## Specifying the name of the starting template -HTML documentation generation (guided by the `[html]` language section of the project codegen.toml) uses a template called `namespace` for the primary html page. Ypu can override the name of the template used by adding `doc_template = "mypage"` to the `[html.parameters]` section. +HTML documentation generation (guided by the `[html]` language section of the project codegen.toml) uses a template called `namespace` for the primary html page. You can override the name of the template used by adding `doc_template = "mypage"` to the `[html.parameters]` section. diff --git a/versioned_docs/version-0.82/hosts/abis/wasmbus/interfaces/tips/index.md b/versioned_docs/version-0.82/hosts/abis/wasmbus/interfaces/tips/index.md index 3f85507f..75d4727a 100644 --- a/versioned_docs/version-0.82/hosts/abis/wasmbus/interfaces/tips/index.md +++ b/versioned_docs/version-0.82/hosts/abis/wasmbus/interfaces/tips/index.md @@ -3,7 +3,7 @@ title: "Tips" draft: false --- -This section conatains some suggestions and tips for writing and debugging interface definitions. +This section contains some suggestions and tips for writing and debugging interface definitions. - [Use lint and validation tools](./lint-validate/) diff --git a/versioned_docs/version-0.82/hosts/lattice-protocols/rpc.md b/versioned_docs/version-0.82/hosts/lattice-protocols/rpc.md index fdf0d2d9..1aae6452 100644 --- a/versioned_docs/version-0.82/hosts/lattice-protocols/rpc.md +++ b/versioned_docs/version-0.82/hosts/lattice-protocols/rpc.md @@ -56,7 +56,7 @@ If you're looking to construct your own invocations manually, you'll need this h The reason we go to such lengths with the invocation is to prevent a malicious entity that has compromised enough credentials to gain access to an RPC NATS connection from actually performing any function calls. Without a valid **cluster seed** (which is injected into a host runtime at startup), an intruder cannot forge an invocation, even if they have unfettered access to NATS. -Monitoring tools could be configuted to detect faked invocations in real time and produce alerts. +Monitoring tools could be configured to detect faked invocations in real time and produce alerts. The claims data structure can be found in the [wascap](https://github.com/wasmCloud/wascap/blob/main/src/jwt.rs) crate. diff --git a/versioned_docs/version-0.82/hosts/security.md b/versioned_docs/version-0.82/hosts/security.md index 63dead0c..49848de4 100644 --- a/versioned_docs/version-0.82/hosts/security.md +++ b/versioned_docs/version-0.82/hosts/security.md @@ -19,7 +19,7 @@ Every actor in the ecosystem is a WebAssembly module that contains an embedded [ In our ecosystem, the issuer of an actor is the unique public key of an **account** (see the _Key Types_ section below), and the subject of an actor is the actor's public key. -The [wash](/docs/0.82/ecosystem/wash) tool is responsible for creating keys and extracting and embeddeding signed JWTs within actor modules. +The [wash](/docs/0.82/ecosystem/wash) tool is responsible for creating keys and extracting and embedding signed JWTs within actor modules. Each JWT embedded within an actor is cryptographically signed using the [ed25519](https://ed25519.cr.yp.to/) signature algorithm. For information on why we chose this method of security over others, please check out our [Archictural Decision Record](https://wasmcloud.github.io/adr/). @@ -53,7 +53,7 @@ In addition to the standard claims required by all [JSON Web Token (JWT)](https: Here one of the most important fields in the `wascap` object is the `caps` field, which contains an array of _capability contract IDs_. Each capability provider must conform to a single, globally unique contract identifier. This ID is typically prefixed with a namespace or vendor prefix, but is not a requirement. -The preceding token indicates that the _Key Value Counter_ actor has been granted access to the Key-Value and HTTP Server capabilities, _without regard_ for which specific provider is used to satisfy those capabilities. In other words, this actor can use _any_ key-value provider, be it Redis or Cassandra or Consul. If you want to further limit which capabilities can be used by actors at runtime, you can define and utlize an [OPA](https://www.openpolicyagent.org/) policy. +The preceding token indicates that the _Key Value Counter_ actor has been granted access to the Key-Value and HTTP Server capabilities, _without regard_ for which specific provider is used to satisfy those capabilities. In other words, this actor can use _any_ key-value provider, be it Redis or Cassandra or Consul. If you want to further limit which capabilities can be used by actors at runtime, you can define and utilize an [OPA](https://www.openpolicyagent.org/) policy. ### Managing Keys diff --git a/versioned_docs/version-0.82/installation.mdx b/versioned_docs/version-0.82/installation.mdx index db5d9e74..b14420dc 100644 --- a/versioned_docs/version-0.82/installation.mdx +++ b/versioned_docs/version-0.82/installation.mdx @@ -225,7 +225,7 @@ main () echo -n "Importing packagecloud gpg key... " # import the gpg key curl -fsSL "${gpg_key_url}" | gpg --dearmor > ${gpg_keyring_path} - # grant 644 permisions to gpg keyring path + # grant 644 permissions to gpg keyring path chmod 0644 "${gpg_keyring_path}" # move gpg key to old path if apt version is older than 1.1 @@ -233,7 +233,7 @@ main () # move to trusted.gpg.d mv ${gpg_keyring_path} ${gpg_key_path_old} - # grant 644 permisions to gpg key path + # grant 644 permissions to gpg key path chmod 0644 "${gpg_key_path_old}" # deletes the keyrings directory if it is empty @@ -387,7 +387,7 @@ finalize_yum_repo () echo echo "WARNING: " echo "The pygpgme package could not be installed. This means GPG verification is not possible for any RPM installed on your system. " - echo "To fix this, add a repository with pygpgme. Usualy, the EPEL repository for your system will have this. " + echo "To fix this, add a repository with pygpgme. Usually, the EPEL repository for your system will have this. " echo "More information: https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F" echo diff --git a/versioned_docs/version-0.82/reference/cloud-event-list.md b/versioned_docs/version-0.82/reference/cloud-event-list.md index b125d024..b8406772 100644 --- a/versioned_docs/version-0.82/reference/cloud-event-list.md +++ b/versioned_docs/version-0.82/reference/cloud-event-list.md @@ -23,7 +23,7 @@ Unless otherwise noted, the `source` field of the CloudEvent is the public key o | `actors_started` | `public_key`
        `image_ref`
        `annotations`
        `host_id`
        `count`
        `claims`(map) | A batch of actor instances successfully started. `host_id` is the same as the envelope's `source` | | `actors_start_failed` | `public_key`
        `image_ref`
        `annotations`
        `host_id`
        `error` | A batch of actor instances failed to start. `host_id` is the same as the envelope's `source` | | `actors_stopped` | `host_id`
        `public_key`
        `count`
        `remaining`
        `annotations` | A batch of actor instances stopped. `host_id` is the same as the envelope's `source` | -| `provider_started` | `public_key`
        `image_ref`
        `link_name`
        `contract_id`
        `instance_id`
        `annotations`
        `claims`(map) | A capability provider succesfully started | +| `provider_started` | `public_key`
        `image_ref`
        `link_name`
        `contract_id`
        `instance_id`
        `annotations`
        `claims`(map) | A capability provider successfully started | | `provider_start_failed` | `provider_ref`
        `link_name`
        `error` | A capability provider failed to start | | `provider_stopped` | `public_key`
        `link_name`
        `contract_id`
        `instance_id`
        `annotations`
        `reason` | A capability provider stopped | | `host_started` | `labels`
        `friendly_name`
        `uptime_seconds`
        `version` | Announced by a host after completing initialization | @@ -41,4 +41,4 @@ The following events are emitted on a special topic, `wasmbus.rpcevt.{lattice-id | Type | Fields | Description | | :-------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------- | | `invocation_failed` | **`source`** (`public_key`, `contract_id`, `link_name`)
        **`dest`** (`public_key`, `contract_id`, `link_name`)
        `operation`
        `bytes` (payload len) | An RPC failure notification | -| `invocation_suceeded` | _Same as above_ | An RPC success notification | +| `invocation_succeeded` | _Same as above_ | An RPC success notification | diff --git a/versioned_docs/version-0.82/reference/official-oci/index.md b/versioned_docs/version-0.82/reference/official-oci/index.md index 35b11aad..c48a5eba 100644 --- a/versioned_docs/version-0.82/reference/official-oci/index.md +++ b/versioned_docs/version-0.82/reference/official-oci/index.md @@ -5,4 +5,4 @@ sidebar_position: 2 draft: false --- -We maintain a list of all officially supported, continually updated, first-party images managed by the wasmcloud team in our Github repositories. Refer to the [providers directory](https://github.com/wasmCloud/wasmCloud/tree/release/v0.82.0/crates/providers) for the latest updated versions of our first party capability providers, and the [examples directory](https://github.com/wasmCloud/wasmCloud/tree/main/examples) for the latest updated versions of our example actors and providers. +We maintain a list of all officially supported, continually updated, first-party images managed by the wasmcloud team in our GitHub repositories. Refer to the [providers directory](https://github.com/wasmCloud/wasmCloud/tree/release/v0.82.0/crates/providers) for the latest updated versions of our first party capability providers, and the [examples directory](https://github.com/wasmCloud/wasmCloud/tree/main/examples) for the latest updated versions of our example actors and providers. diff --git a/versioned_docs/version-0.82/reference/wasi/incoming-http.md b/versioned_docs/version-0.82/reference/wasi/incoming-http.md index 83c6329a..9007fe1e 100644 --- a/versioned_docs/version-0.82/reference/wasi/incoming-http.md +++ b/versioned_docs/version-0.82/reference/wasi/incoming-http.md @@ -105,7 +105,7 @@ corresponding to a clock tick.

        subscribe-instant: func

        Create a pollable which will resolve once the specified instant -occured.

        +occurred.

        Params
        • when: instant
          • @@ -117,7 +117,7 @@ occured.

          subscribe-duration: func

          Create a pollable which will resolve once the given duration has elapsed, starting at the time at which this function was called. -occured.

          +occurred.

          Params
          • when: duration
            • @@ -378,7 +378,7 @@ and stream is ready for writing again.

          [method]output-stream.subscribe: func

          Create a pollable which will resolve once the output-stream -is ready for more writing, or an error has occured. When this +is ready for more writing, or an error has occurred. When this pollable is ready, check-write will return ok(n) with n>0, or an error.

          If the stream is closed, this pollable is always ready immediately.

          @@ -441,7 +441,7 @@ let _ = this.check-write(); // eliding error handling

        [method]output-stream.splice: func

        Read from one stream and write to another.

        -

        The behavior of splice is equivelant to:

        +

        The behavior of splice is equivalent to:

        1. calling check-write on the output-stream
        2. calling read on the input-stream with the smaller of the @@ -667,7 +667,7 @@ an input-stream and the delivery of tra and ensures that the user of this interface may only be consuming either the body contents or waiting on trailers at any given time.

          resource future-trailers

          -

          Represents a future which may eventaully return trailers, or an error.

          +

          Represents a future which may eventually return trailers, or an error.

          In the case that the incoming HTTP Request or Response did not have any trailers, this future will resolve to the empty set of trailers once the complete Request or Response body has been received.

          @@ -684,12 +684,12 @@ optional trailers) with a static function that consumes the may not write to the body contents after the body has been finished.

          If the user code drops this resource, as opposed to calling the static method finish, the implementation should treat the body as incomplete, -and that an error has occured. The implementation should propogate this +and that an error has occurred. The implementation should propagate this error to the HTTP protocol by whatever means it has available, including: corrupting the body on the wire, aborting the associated Request, or sending a late status code for the Response.

          resource future-incoming-response

          -

          Represents a future which may eventaully return an incoming HTTP +

          Represents a future which may eventually return an incoming HTTP Response, or an error.

          This resource is returned by the wasi:http/outgoing-handler interface to provide the HTTP Response corresponding to the sent Request.

          @@ -821,7 +821,7 @@ list with the same key.

        3. list<(field-key, field-value)>

          4. [method]fields.clone: func

          -

          Make a deep copy of the Fields. Equivelant in behavior to calling the +

          Make a deep copy of the Fields. Equivalent in behavior to calling the fields constructor on the return value of entries. The resulting fields is mutable.

          Params
          @@ -1032,7 +1032,7 @@ not a syntactically valid uri authority.

          The returned headers resource is immutable: set, append, and delete operations will fail with header-error.immutable.

          This headers resource is a child: it must be dropped before the parent -outgoing-request is dropped, or its ownership is transfered to +outgoing-request is dropped, or its ownership is transferred to another component by e.g. outgoing-handler.handle.

          Params
            @@ -1198,7 +1198,7 @@ This function will trap if the input-stream

          [method]future-trailers.subscribe: func

          Returns a pollable which becomes ready when either the trailers have -been received, or an error has occured. When this pollable is ready, +been received, or an error has occurred. When this pollable is ready, the get method will return some.

          Params
            @@ -1209,7 +1209,7 @@ the get method will return some.

          • own<pollable>

          [method]future-trailers.get: func

          -

          Returns the contents of the trailers, or an error which occured, +

          Returns the contents of the trailers, or an error which occurred, once the future is ready.

          The outer option represents future readiness. Users can wait on this option to become some using the subscribe method.

          @@ -1218,7 +1218,7 @@ once. It will be success on the first call in which the outer option is some, and error on subsequent calls.

          The inner result represents that either the HTTP Request or Response body, as well as any trailers, were received successfully, or that an -error occured receiving them. The optional trailers indicates whether +error occurred receiving them. The optional trailers indicates whether or not trailers were present in the body.

          When some trailers are returned by this method, the trailers resource is immutable, and a child. Use of the set, append, or @@ -1274,7 +1274,7 @@ given is not a valid http status code.

          The returned headers resource is immutable: set, append, and delete operations will fail with header-error.immutable.

          This headers resource is a child: it must be dropped before the parent -outgoing-request is dropped, or its ownership is transfered to +outgoing-request is dropped, or its ownership is transferred to another component by e.g. outgoing-handler.handle.

          Params
            @@ -1333,7 +1333,7 @@ Content-Length.

          [method]future-incoming-response.subscribe: func

          Returns a pollable which becomes ready when either the Response has -been received, or an error has occured. When this pollable is ready, +been received, or an error has occurred. When this pollable is ready, the get method will return some.

          Params
            @@ -1351,8 +1351,8 @@ the get method will return some.

            once. It will be success on the first call in which the outer option is some, and error on subsequent calls.

            The inner result represents that either the incoming HTTP Response -status and headers have recieved successfully, or that an error -occured. Errors may also occur while consuming the response body, +status and headers have received successfully, or that an error +occurred. Errors may also occur while consuming the response body, but those will be reported by the incoming-body and its output-stream child.

            Params
            diff --git a/versioned_docs/version-0.82/reference/wasi/interfaces.md b/versioned_docs/version-0.82/reference/wasi/interfaces.md index 6f615d16..9acdb0ca 100644 --- a/versioned_docs/version-0.82/reference/wasi/interfaces.md +++ b/versioned_docs/version-0.82/reference/wasi/interfaces.md @@ -326,7 +326,7 @@ and stream is ready for writing again.

          [method]output-stream.subscribe: func

          Create a pollable which will resolve once the output-stream -is ready for more writing, or an error has occured. When this +is ready for more writing, or an error has occurred. When this pollable is ready, check-write will return ok(n) with n>0, or an error.

          If the stream is closed, this pollable is always ready immediately.

          @@ -389,7 +389,7 @@ let _ = this.check-write(); // eliding error handling

          [method]output-stream.splice: func

          Read from one stream and write to another.

          -

          The behavior of splice is equivelant to:

          +

          The behavior of splice is equivalent to:

          1. calling check-write on the output-stream
          2. calling read on the input-stream with the smaller of the @@ -1014,7 +1014,7 @@ corresponding to a clock tick.

            subscribe-instant: func

            Create a pollable which will resolve once the specified instant -occured.

            +occurred.

            Params
            • when: instant
              • @@ -1026,7 +1026,7 @@ occured.

              subscribe-duration: func

              Create a pollable which will resolve once the given duration has elapsed, starting at the time at which this function was called. -occured.

              +occurred.

              Params
              • when: duration
                • @@ -1225,7 +1225,7 @@ an input-stream and the delivery of tra and ensures that the user of this interface may only be consuming either the body contents or waiting on trailers at any given time.

                resource future-trailers

                -

                Represents a future which may eventaully return trailers, or an error.

                +

                Represents a future which may eventually return trailers, or an error.

                In the case that the incoming HTTP Request or Response did not have any trailers, this future will resolve to the empty set of trailers once the complete Request or Response body has been received.

                @@ -1242,12 +1242,12 @@ optional trailers) with a static function that consumes the may not write to the body contents after the body has been finished.

                If the user code drops this resource, as opposed to calling the static method finish, the implementation should treat the body as incomplete, -and that an error has occured. The implementation should propogate this +and that an error has occurred. The implementation should propagate this error to the HTTP protocol by whatever means it has available, including: corrupting the body on the wire, aborting the associated Request, or sending a late status code for the Response.

                resource future-incoming-response

                -

                Represents a future which may eventaully return an incoming HTTP +

                Represents a future which may eventually return an incoming HTTP Response, or an error.

                This resource is returned by the wasi:http/outgoing-handler interface to provide the HTTP Response corresponding to the sent Request.

                @@ -1379,7 +1379,7 @@ list with the same key.

              • list<(field-key, field-value)>

              [method]fields.clone: func

              -

              Make a deep copy of the Fields. Equivelant in behavior to calling the +

              Make a deep copy of the Fields. Equivalent in behavior to calling the fields constructor on the return value of entries. The resulting fields is mutable.

              Params
              @@ -1590,7 +1590,7 @@ not a syntactically valid uri authority.

              The returned headers resource is immutable: set, append, and delete operations will fail with header-error.immutable.

              This headers resource is a child: it must be dropped before the parent -outgoing-request is dropped, or its ownership is transfered to +outgoing-request is dropped, or its ownership is transferred to another component by e.g. outgoing-handler.handle.

              Params
                @@ -1756,7 +1756,7 @@ This function will trap if the input-stream

              [method]future-trailers.subscribe: func

              Returns a pollable which becomes ready when either the trailers have -been received, or an error has occured. When this pollable is ready, +been received, or an error has occurred. When this pollable is ready, the get method will return some.

              Params
                @@ -1767,7 +1767,7 @@ the get method will return some.

                own<pollable>

              [method]future-trailers.get: func

              -

              Returns the contents of the trailers, or an error which occured, +

              Returns the contents of the trailers, or an error which occurred, once the future is ready.

              The outer option represents future readiness. Users can wait on this option to become some using the subscribe method.

              @@ -1776,7 +1776,7 @@ once. It will be success on the first call in which the outer option is some, and error on subsequent calls.

              The inner result represents that either the HTTP Request or Response body, as well as any trailers, were received successfully, or that an -error occured receiving them. The optional trailers indicates whether +error occurred receiving them. The optional trailers indicates whether or not trailers were present in the body.

              When some trailers are returned by this method, the trailers resource is immutable, and a child. Use of the set, append, or @@ -1832,7 +1832,7 @@ given is not a valid http status code.

              The returned headers resource is immutable: set, append, and delete operations will fail with header-error.immutable.

              This headers resource is a child: it must be dropped before the parent -outgoing-request is dropped, or its ownership is transfered to +outgoing-request is dropped, or its ownership is transferred to another component by e.g. outgoing-handler.handle.

              Params
                @@ -1891,7 +1891,7 @@ Content-Length.

              [method]future-incoming-response.subscribe: func

              Returns a pollable which becomes ready when either the Response has -been received, or an error has occured. When this pollable is ready, +been received, or an error has occurred. When this pollable is ready, the get method will return some.

              Params
                @@ -1909,8 +1909,8 @@ the get method will return some.

                some, and error on subsequent calls.

                The inner result represents that either the incoming HTTP Response -status and headers have recieved successfully, or that an error -occured. Errors may also occur while consuming the response body, +status and headers have received successfully, or that an error +occurred. Errors may also occur while consuming the response body, but those will be reported by the incoming-body and its output-stream child.

                Params
                diff --git a/versioned_docs/version-0.82/roadmap/index.md b/versioned_docs/version-0.82/roadmap/index.md index 73876e61..4cd2bcf1 100644 --- a/versioned_docs/version-0.82/roadmap/index.md +++ b/versioned_docs/version-0.82/roadmap/index.md @@ -51,7 +51,7 @@ There are many smaller tasks that are included as well, such as [namespacing our ## Diagram -The diagram below shows a loose organization of critical tasks into 3 sections: Stabilizing APIs, WebAssembly standards, and wasmCloud functionality. This roadmap is unordered as each individual task can be completed indepedently, so no rigid order is necessary. The diagram is also not exhaustive, as there are many smaller tasks that are not included. You can view the full-size version [here](/docs/images/2024q1roadmap.png). +The diagram below shows a loose organization of critical tasks into 3 sections: Stabilizing APIs, WebAssembly standards, and wasmCloud functionality. This roadmap is unordered as each individual task can be completed independently, so no rigid order is necessary. The diagram is also not exhaustive, as there are many smaller tasks that are not included. You can view the full-size version [here](/docs/images/2024q1roadmap.png). ![Q1 2024 Roadmap](/docs/images/2024q1roadmap.png) diff --git a/writing-styles/Microsoft/Avoid.yml b/writing-styles/Microsoft/Avoid.yml index dab7822c..a1bcbe47 100644 --- a/writing-styles/Microsoft/Avoid.yml +++ b/writing-styles/Microsoft/Avoid.yml @@ -7,8 +7,8 @@ level: error tokens: - abortion - and so on - - app(?:lication)?s? (?:developer|program) - - app(?:lication)? file + - app(?:location)?s? (?:developer|program) + - app(?:location)? file - backbone - backend - contiguous selection From 209d8613c5bd62285235b2cd28ea04a4b40670db Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Viktor=20Sz=C3=A9pe?= Date: Wed, 15 Jan 2025 20:43:46 +0000 Subject: [PATCH 2/9] Revert false positived and fix indentations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Viktor Szépe --- docs/deployment/deployment-guide/index.mdx | 2 +- docs/reference/cloud-event-list.mdx | 6 +++--- src/pages/privacy-policy/index.mdx | 2 +- versioned_docs/version-0.82/ecosystem/wadm/model.md | 2 +- versioned_docs/version-0.82/reference/cloud-event-list.md | 4 ++-- writing-styles/Microsoft/Avoid.yml | 4 ++-- 6 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/deployment/deployment-guide/index.mdx b/docs/deployment/deployment-guide/index.mdx index acb19100..73c52896 100644 --- a/docs/deployment/deployment-guide/index.mdx +++ b/docs/deployment/deployment-guide/index.mdx @@ -21,7 +21,7 @@ This page outlines platforms supported by wasmCloud with the best available depl | **Google Cloud Platform** | Google Kubernetes Engine (GKE) | Yes | [GKE Documentation](https://cloud.google.com/kubernetes-engine/docs/quickstart) | [Deploy wasmCloud on Kubernetes](/docs/deployment/k8s/index.mdx) | | | Google App Engine | Yes | [App Engine Documentation](https://cloud.google.com/appengine/docs) | [Request documentation](https://github.com/wasmCloud/wasmcloud.com/issues/new) | | **Microsoft Azure** | Azure Kubernetes Service (AKS) | Yes | [AKS Documentation](https://learn.microsoft.com/en-us/azure/aks/) | [Deploy wasmCloud on Kubernetes](/docs/deployment/k8s/index.mdx) | -| | Azure Container Instances (ACPI) | Yes | [ACPI Documentation](https://learn.microsoft.com/en-us/azure/container-instances/) | [Request documentation](https://github.com/wasmCloud/wasmcloud.com/issues/new) | +| | Azure Container Instances (ACI) | Yes | [ACI Documentation](https://learn.microsoft.com/en-us/azure/container-instances/) | [Request documentation](https://github.com/wasmCloud/wasmcloud.com/issues/new) | | | Azure App Service | Yes | [App Service Documentation](https://learn.microsoft.com/en-us/azure/app-service/) | [Request documentation](https://github.com/wasmCloud/wasmcloud.com/issues/new) | | | Azure Red Hat OpenShift | Yes | [Azure Red Hat OpenShift Documentation](https://learn.microsoft.com/en-us/azure/openshift/) | [Request documentation](https://github.com/wasmCloud/wasmcloud.com/issues/new) | | **IBM Cloud** | IBM Cloud Kubernetes Service | Yes | [IBM Cloud Kubernetes Service Documentation](https://cloud.ibm.com/docs/containers) | [Deploy wasmCloud on Kubernetes](/docs/deployment/k8s/index.mdx) | diff --git a/docs/reference/cloud-event-list.mdx b/docs/reference/cloud-event-list.mdx index c19e6281..be4052ac 100644 --- a/docs/reference/cloud-event-list.mdx +++ b/docs/reference/cloud-event-list.mdx @@ -760,7 +760,7 @@ The `host_stopped` event is emitted when a host has stopped. The following events are emitted on a special topic, `wasmbus.rpcevt.{lattice-id}` to keep the relatively chatty RPC notifications separate from the other events. -| Type | Description | -| :-------------------- | :-------------------------- | -| `invocation_failed` | An RPC failure notification | +| Type | Description | +| :--------------------- | :-------------------------- | +| `invocation_failed` | An RPC failure notification | | `invocation_succeeded` | An RPC success notification | diff --git a/src/pages/privacy-policy/index.mdx b/src/pages/privacy-policy/index.mdx index 98995874..dff0fb8a 100644 --- a/src/pages/privacy-policy/index.mdx +++ b/src/pages/privacy-policy/index.mdx @@ -796,7 +796,7 @@ The EDAA's opt-out platform [http://www.youronlinechoices.com/](http://www.youro * -The DATA's opt-out platform: [http://optout.aboutads.info/?c=2&lang=EN](http://optout.aboutads.info/?c=2&lang=EN) +The DAA's opt-out platform: [http://optout.aboutads.info/?c=2&lang=EN](http://optout.aboutads.info/?c=2&lang=EN) The opt out will place a cookie on Your computer that is unique to the browser You use to opt out. If you change browsers or delete the cookies saved by your browser, You will need to opt out again. diff --git a/versioned_docs/version-0.82/ecosystem/wadm/model.md b/versioned_docs/version-0.82/ecosystem/wadm/model.md index 5c28b46a..c571c4cd 100644 --- a/versioned_docs/version-0.82/ecosystem/wadm/model.md +++ b/versioned_docs/version-0.82/ecosystem/wadm/model.md @@ -7,7 +7,7 @@ type: 'docs' sidebar_position: 2 --- -The **w**asmCloud **A**application **D**eployment **M**anager uses the [Open Application Model](https://oam.dev/) to define application specifications. Because this specification is extensible and platform agnostic, it makes for an ideal way to represent applications with metadata specific to wasmCloud. Don't worry if OAM seems overwhelming, you don't need to know much about it. We're using it as a way of defining application components in a flexible way that's familiar to a lot of people who have been working in the cloud space. +The **w**asmCloud **A**pplication **D**eployment **M**anager uses the [Open Application Model](https://oam.dev/) to define application specifications. Because this specification is extensible and platform agnostic, it makes for an ideal way to represent applications with metadata specific to wasmCloud. Don't worry if OAM seems overwhelming, you don't need to know much about it. We're using it as a way of defining application components in a flexible way that's familiar to a lot of people who have been working in the cloud space. In this model, an application `specification` is a set of metadata about the app, as well as a list of `components`. Each component within an application is decorated with various `traits`. These core building blocks allow us to make it very easy to define incredibly powerful deployments. wasmCloud defines a number of traits that are specific to our hosts, but let's go through the model from top to bottom. diff --git a/versioned_docs/version-0.82/reference/cloud-event-list.md b/versioned_docs/version-0.82/reference/cloud-event-list.md index b8406772..afb859ee 100644 --- a/versioned_docs/version-0.82/reference/cloud-event-list.md +++ b/versioned_docs/version-0.82/reference/cloud-event-list.md @@ -23,7 +23,7 @@ Unless otherwise noted, the `source` field of the CloudEvent is the public key o | `actors_started` | `public_key`
                `image_ref`
                `annotations`
                `host_id`
                `count`
                `claims`(map) | A batch of actor instances successfully started. `host_id` is the same as the envelope's `source` | | `actors_start_failed` | `public_key`
                `image_ref`
                `annotations`
                `host_id`
                `error` | A batch of actor instances failed to start. `host_id` is the same as the envelope's `source` | | `actors_stopped` | `host_id`
                `public_key`
                `count`
                `remaining`
                `annotations` | A batch of actor instances stopped. `host_id` is the same as the envelope's `source` | -| `provider_started` | `public_key`
                `image_ref`
                `link_name`
                `contract_id`
                `instance_id`
                `annotations`
                `claims`(map) | A capability provider successfully started | +| `provider_started` | `public_key`
                `image_ref`
                `link_name`
                `contract_id`
                `instance_id`
                `annotations`
                `claims`(map) | A capability provider successfully started | | `provider_start_failed` | `provider_ref`
                `link_name`
                `error` | A capability provider failed to start | | `provider_stopped` | `public_key`
                `link_name`
                `contract_id`
                `instance_id`
                `annotations`
                `reason` | A capability provider stopped | | `host_started` | `labels`
                `friendly_name`
                `uptime_seconds`
                `version` | Announced by a host after completing initialization | @@ -41,4 +41,4 @@ The following events are emitted on a special topic, `wasmbus.rpcevt.{lattice-id | Type | Fields | Description | | :-------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------- | | `invocation_failed` | **`source`** (`public_key`, `contract_id`, `link_name`)
                **`dest`** (`public_key`, `contract_id`, `link_name`)
                `operation`
                `bytes` (payload len) | An RPC failure notification | -| `invocation_succeeded` | _Same as above_ | An RPC success notification | +| `invocation_succeeded` | _Same as above_ | An RPC success notification | diff --git a/writing-styles/Microsoft/Avoid.yml b/writing-styles/Microsoft/Avoid.yml index a1bcbe47..dab7822c 100644 --- a/writing-styles/Microsoft/Avoid.yml +++ b/writing-styles/Microsoft/Avoid.yml @@ -7,8 +7,8 @@ level: error tokens: - abortion - and so on - - app(?:location)?s? (?:developer|program) - - app(?:location)? file + - app(?:lication)?s? (?:developer|program) + - app(?:lication)? file - backbone - backend - contiguous selection From d320704d7b530d5521276044b0d1138606ac2503 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Viktor=20Sz=C3=A9pe?= Date: Wed, 15 Jan 2025 21:44:57 +0100 Subject: [PATCH 3/9] Update community/2023-09-20-community-meeting.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Eric Gregory Signed-off-by: Viktor Szépe --- community/2023-09-20-community-meeting.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community/2023-09-20-community-meeting.mdx b/community/2023-09-20-community-meeting.mdx index 8326115f..2d6af850 100644 --- a/community/2023-09-20-community-meeting.mdx +++ b/community/2023-09-20-community-meeting.mdx @@ -51,7 +51,7 @@ date: 2023-09-20 - Rust Host lost some of that introspection. - Info on number of actors providers invocations that have a particular provider or actor. - Interesting summary stats around specific resource usage: so we can more accurately scale actors up and down. - - Provider exposing metrics - counter for number of 500s/400s is pretty common. We want to be able to do the same thing in wasmCould. + - Provider exposing metrics - counter for number of 500s/400s is pretty common. We want to be able to do the same thing in wasmCloud. - Some work to do to decide how, but this is where we're leaning. - [Observability and metrics RFC](https://github.com/wasmCloud/wasmCloud/issues/664) - please get involved if you have expertise - we're excited to hear your opinions and experiences. - Check out the recording for the full discussion. From 86e5124c719e798bfb8338dd53cba24413ede8dd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Viktor=20Sz=C3=A9pe?= Date: Wed, 15 Jan 2025 21:45:41 +0100 Subject: [PATCH 4/9] Update community/2024-02-21-community-meeting.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Eric Gregory Signed-off-by: Viktor Szépe --- community/2024-02-21-community-meeting.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community/2024-02-21-community-meeting.mdx b/community/2024-02-21-community-meeting.mdx index e91f407e..2707dc6d 100644 --- a/community/2024-02-21-community-meeting.mdx +++ b/community/2024-02-21-community-meeting.mdx @@ -43,7 +43,7 @@ date: 2024-02-21 ### COMMUNITY DISCUSSION AND Q&A - Colin: Fuzzing (send random bits and see if it creates fatal errors). - - Fuzzing in rust unless you want to stand up the entire wasmCould host every time, it's hard to call a specific function without standing everything up. + - Fuzzing in rust unless you want to stand up the entire wasmCloud host every time, it's hard to call a specific function without standing everything up. - Limitations of macros on top of macros. - Mock All - most commonly used. - Anyone have any familiarity mocking/fuzzing in Rust? From 87763cb650350cf5c66305cda16a6218eb610c1f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Viktor=20Sz=C3=A9pe?= Date: Wed, 15 Jan 2025 21:49:39 +0100 Subject: [PATCH 5/9] Update community/2024-10-16-community-meeting.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Eric Gregory Signed-off-by: Viktor Szépe --- community/2024-10-16-community-meeting.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community/2024-10-16-community-meeting.mdx b/community/2024-10-16-community-meeting.mdx index 6d63e7f5..f826dcfb 100644 --- a/community/2024-10-16-community-meeting.mdx +++ b/community/2024-10-16-community-meeting.mdx @@ -26,7 +26,7 @@ title: 'Meeting Agenda - 2024-10-16' - wash dev is the major update in 1.3 which provides a way for us to review component dependencies in full. - [Release notes](https://github.com/wasmCloud/wasmCloud/releases/tag/v1.3.0) are tagged along with the 1.3 release. - Notably, we have introduced a new validation path for links. Earlier, you cauld have an http server provider forwarded to components based on a path. We used to be able to do this with the same interface without specifying a link name - this is now invalid. -- What must be present to create a link from the same source o multiple targes, you must soecufy the kink name - a unuqie idejtifier for calling a specific target at runtime, +- What must be present to create a link from the same source to multiple targets, you must specify the link name - a unique identifier for calling a specific target at runtime, - Works by extension for cap providers - htto triggered by an external handler. - Wasm component context requires additional identification layer. - Check out the recording for [Massoud's](https://github.com/wasmCloud/wasmCloud/blob/main/examples/rust/components/keyvalue-messaging/src/lib.rs) example - a great way to demo why we need this feature. In your code you can denote you're calling 2 different locations, identified with link names. From 6127a38b811b69ec34171850208d7773f41267c2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Viktor=20Sz=C3=A9pe?= Date: Wed, 15 Jan 2025 20:54:20 +0000 Subject: [PATCH 6/9] Revert old cloud-event-list MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Viktor Szépe --- versioned_docs/version-0.82/reference/cloud-event-list.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-0.82/reference/cloud-event-list.md b/versioned_docs/version-0.82/reference/cloud-event-list.md index afb859ee..e20c7de9 100644 --- a/versioned_docs/version-0.82/reference/cloud-event-list.md +++ b/versioned_docs/version-0.82/reference/cloud-event-list.md @@ -41,4 +41,4 @@ The following events are emitted on a special topic, `wasmbus.rpcevt.{lattice-id | Type | Fields | Description | | :-------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------- | | `invocation_failed` | **`source`** (`public_key`, `contract_id`, `link_name`)
                **`dest`** (`public_key`, `contract_id`, `link_name`)
                `operation`
                `bytes` (payload len) | An RPC failure notification | -| `invocation_succeeded` | _Same as above_ | An RPC success notification | +| `invocation_suceeded` | _Same as above_ | An RPC success notification | From fcc41d100a7f8524d11ebc70415c98cdd2c227ab Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Viktor=20Sz=C3=A9pe?= Date: Wed, 15 Jan 2025 20:58:18 +0000 Subject: [PATCH 7/9] Revert typos from upstream MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Viktor Szépe --- .../reference/wasi/incoming-http.md | 32 +++++++++---------- .../version-0.82/reference/wasi/interfaces.md | 32 +++++++++---------- 2 files changed, 32 insertions(+), 32 deletions(-) diff --git a/versioned_docs/version-0.82/reference/wasi/incoming-http.md b/versioned_docs/version-0.82/reference/wasi/incoming-http.md index 9007fe1e..83c6329a 100644 --- a/versioned_docs/version-0.82/reference/wasi/incoming-http.md +++ b/versioned_docs/version-0.82/reference/wasi/incoming-http.md @@ -105,7 +105,7 @@ corresponding to a clock tick.

              subscribe-instant: func

              Create a pollable which will resolve once the specified instant -occurred.

              +occured.

              Params
              • when: instant
                • @@ -117,7 +117,7 @@ occurred.

                subscribe-duration: func

                Create a pollable which will resolve once the given duration has elapsed, starting at the time at which this function was called. -occurred.

                +occured.

                Params
                • when: duration
                  • @@ -378,7 +378,7 @@ and stream is ready for writing again.

                [method]output-stream.subscribe: func

                Create a pollable which will resolve once the output-stream -is ready for more writing, or an error has occurred. When this +is ready for more writing, or an error has occured. When this pollable is ready, check-write will return ok(n) with n>0, or an error.

                If the stream is closed, this pollable is always ready immediately.

                @@ -441,7 +441,7 @@ let _ = this.check-write(); // eliding error handling

              [method]output-stream.splice: func

              Read from one stream and write to another.

              -

              The behavior of splice is equivalent to:

              +

              The behavior of splice is equivelant to:

              1. calling check-write on the output-stream
              2. calling read on the input-stream with the smaller of the @@ -667,7 +667,7 @@ an input-stream and the delivery of tra and ensures that the user of this interface may only be consuming either the body contents or waiting on trailers at any given time.

                resource future-trailers

                -

                Represents a future which may eventually return trailers, or an error.

                +

                Represents a future which may eventaully return trailers, or an error.

                In the case that the incoming HTTP Request or Response did not have any trailers, this future will resolve to the empty set of trailers once the complete Request or Response body has been received.

                @@ -684,12 +684,12 @@ optional trailers) with a static function that consumes the may not write to the body contents after the body has been finished.

                If the user code drops this resource, as opposed to calling the static method finish, the implementation should treat the body as incomplete, -and that an error has occurred. The implementation should propagate this +and that an error has occured. The implementation should propogate this error to the HTTP protocol by whatever means it has available, including: corrupting the body on the wire, aborting the associated Request, or sending a late status code for the Response.

                resource future-incoming-response

                -

                Represents a future which may eventually return an incoming HTTP +

                Represents a future which may eventaully return an incoming HTTP Response, or an error.

                This resource is returned by the wasi:http/outgoing-handler interface to provide the HTTP Response corresponding to the sent Request.

                @@ -821,7 +821,7 @@ list with the same key.

              3. list<(field-key, field-value)>

            [method]fields.clone: func

            -

            Make a deep copy of the Fields. Equivalent in behavior to calling the +

            Make a deep copy of the Fields. Equivelant in behavior to calling the fields constructor on the return value of entries. The resulting fields is mutable.

            Params
            @@ -1032,7 +1032,7 @@ not a syntactically valid uri authority.

            The returned headers resource is immutable: set, append, and delete operations will fail with header-error.immutable.

            This headers resource is a child: it must be dropped before the parent -outgoing-request is dropped, or its ownership is transferred to +outgoing-request is dropped, or its ownership is transfered to another component by e.g. outgoing-handler.handle.

            Params
              @@ -1198,7 +1198,7 @@ This function will trap if the input-stream

            [method]future-trailers.subscribe: func

            Returns a pollable which becomes ready when either the trailers have -been received, or an error has occurred. When this pollable is ready, +been received, or an error has occured. When this pollable is ready, the get method will return some.

            Params
              @@ -1209,7 +1209,7 @@ the get method will return some.

            • own<pollable>

            [method]future-trailers.get: func

            -

            Returns the contents of the trailers, or an error which occurred, +

            Returns the contents of the trailers, or an error which occured, once the future is ready.

            The outer option represents future readiness. Users can wait on this option to become some using the subscribe method.

            @@ -1218,7 +1218,7 @@ once. It will be success on the first call in which the outer option is some, and error on subsequent calls.

            The inner result represents that either the HTTP Request or Response body, as well as any trailers, were received successfully, or that an -error occurred receiving them. The optional trailers indicates whether +error occured receiving them. The optional trailers indicates whether or not trailers were present in the body.

            When some trailers are returned by this method, the trailers resource is immutable, and a child. Use of the set, append, or @@ -1274,7 +1274,7 @@ given is not a valid http status code.

            The returned headers resource is immutable: set, append, and delete operations will fail with header-error.immutable.

            This headers resource is a child: it must be dropped before the parent -outgoing-request is dropped, or its ownership is transferred to +outgoing-request is dropped, or its ownership is transfered to another component by e.g. outgoing-handler.handle.

            Params
              @@ -1333,7 +1333,7 @@ Content-Length.

            [method]future-incoming-response.subscribe: func

            Returns a pollable which becomes ready when either the Response has -been received, or an error has occurred. When this pollable is ready, +been received, or an error has occured. When this pollable is ready, the get method will return some.

            Params
              @@ -1351,8 +1351,8 @@ the get method will return some.

              once. It will be success on the first call in which the outer option is some, and error on subsequent calls.

              The inner result represents that either the incoming HTTP Response -status and headers have received successfully, or that an error -occurred. Errors may also occur while consuming the response body, +status and headers have recieved successfully, or that an error +occured. Errors may also occur while consuming the response body, but those will be reported by the incoming-body and its output-stream child.

              Params
              diff --git a/versioned_docs/version-0.82/reference/wasi/interfaces.md b/versioned_docs/version-0.82/reference/wasi/interfaces.md index 9acdb0ca..6f615d16 100644 --- a/versioned_docs/version-0.82/reference/wasi/interfaces.md +++ b/versioned_docs/version-0.82/reference/wasi/interfaces.md @@ -326,7 +326,7 @@ and stream is ready for writing again.

            [method]output-stream.subscribe: func

            Create a pollable which will resolve once the output-stream -is ready for more writing, or an error has occurred. When this +is ready for more writing, or an error has occured. When this pollable is ready, check-write will return ok(n) with n>0, or an error.

            If the stream is closed, this pollable is always ready immediately.

            @@ -389,7 +389,7 @@ let _ = this.check-write(); // eliding error handling

            [method]output-stream.splice: func

            Read from one stream and write to another.

            -

            The behavior of splice is equivalent to:

            +

            The behavior of splice is equivelant to:

            1. calling check-write on the output-stream
            2. calling read on the input-stream with the smaller of the @@ -1014,7 +1014,7 @@ corresponding to a clock tick.

              subscribe-instant: func

              Create a pollable which will resolve once the specified instant -occurred.

              +occured.

              Params
              • when: instant
                • @@ -1026,7 +1026,7 @@ occurred.

                subscribe-duration: func

                Create a pollable which will resolve once the given duration has elapsed, starting at the time at which this function was called. -occurred.

                +occured.

                Params
                • when: duration
                  • @@ -1225,7 +1225,7 @@ an input-stream and the delivery of tra and ensures that the user of this interface may only be consuming either the body contents or waiting on trailers at any given time.

                  resource future-trailers

                  -

                  Represents a future which may eventually return trailers, or an error.

                  +

                  Represents a future which may eventaully return trailers, or an error.

                  In the case that the incoming HTTP Request or Response did not have any trailers, this future will resolve to the empty set of trailers once the complete Request or Response body has been received.

                  @@ -1242,12 +1242,12 @@ optional trailers) with a static function that consumes the may not write to the body contents after the body has been finished.

                  If the user code drops this resource, as opposed to calling the static method finish, the implementation should treat the body as incomplete, -and that an error has occurred. The implementation should propagate this +and that an error has occured. The implementation should propogate this error to the HTTP protocol by whatever means it has available, including: corrupting the body on the wire, aborting the associated Request, or sending a late status code for the Response.

                  resource future-incoming-response

                  -

                  Represents a future which may eventually return an incoming HTTP +

                  Represents a future which may eventaully return an incoming HTTP Response, or an error.

                  This resource is returned by the wasi:http/outgoing-handler interface to provide the HTTP Response corresponding to the sent Request.

                  @@ -1379,7 +1379,7 @@ list with the same key.

                • list<(field-key, field-value)>

                [method]fields.clone: func

                -

                Make a deep copy of the Fields. Equivalent in behavior to calling the +

                Make a deep copy of the Fields. Equivelant in behavior to calling the fields constructor on the return value of entries. The resulting fields is mutable.

                Params
                @@ -1590,7 +1590,7 @@ not a syntactically valid uri authority.

                The returned headers resource is immutable: set, append, and delete operations will fail with header-error.immutable.

                This headers resource is a child: it must be dropped before the parent -outgoing-request is dropped, or its ownership is transferred to +outgoing-request is dropped, or its ownership is transfered to another component by e.g. outgoing-handler.handle.

                Params
                  @@ -1756,7 +1756,7 @@ This function will trap if the input-stream

                [method]future-trailers.subscribe: func

                Returns a pollable which becomes ready when either the trailers have -been received, or an error has occurred. When this pollable is ready, +been received, or an error has occured. When this pollable is ready, the get method will return some.

                Params
                  @@ -1767,7 +1767,7 @@ the get method will return some.

                  own<pollable>

                [method]future-trailers.get: func

                -

                Returns the contents of the trailers, or an error which occurred, +

                Returns the contents of the trailers, or an error which occured, once the future is ready.

                The outer option represents future readiness. Users can wait on this option to become some using the subscribe method.

                @@ -1776,7 +1776,7 @@ once. It will be success on the first call in which the outer option is some, and error on subsequent calls.

                The inner result represents that either the HTTP Request or Response body, as well as any trailers, were received successfully, or that an -error occurred receiving them. The optional trailers indicates whether +error occured receiving them. The optional trailers indicates whether or not trailers were present in the body.

                When some trailers are returned by this method, the trailers resource is immutable, and a child. Use of the set, append, or @@ -1832,7 +1832,7 @@ given is not a valid http status code.

                The returned headers resource is immutable: set, append, and delete operations will fail with header-error.immutable.

                This headers resource is a child: it must be dropped before the parent -outgoing-request is dropped, or its ownership is transferred to +outgoing-request is dropped, or its ownership is transfered to another component by e.g. outgoing-handler.handle.

                Params
                  @@ -1891,7 +1891,7 @@ Content-Length.

                [method]future-incoming-response.subscribe: func

                Returns a pollable which becomes ready when either the Response has -been received, or an error has occurred. When this pollable is ready, +been received, or an error has occured. When this pollable is ready, the get method will return some.

                Params
                  @@ -1909,8 +1909,8 @@ the get method will return some.

                  some, and error on subsequent calls.

                  The inner result represents that either the incoming HTTP Response -status and headers have received successfully, or that an error -occurred. Errors may also occur while consuming the response body, +status and headers have recieved successfully, or that an error +occured. Errors may also occur while consuming the response body, but those will be reported by the incoming-body and its output-stream child.

                  Params
                  From a30f85cc3296ab152b5ff1b7ec60e15a6e6eab6c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Viktor=20Sz=C3=A9pe?= Date: Wed, 15 Jan 2025 21:08:07 +0000 Subject: [PATCH 8/9] Revert MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Viktor Szépe --- docs/reference/wasi/incoming-http.md | 32 +++++++++++++------------- docs/reference/wasi/interfaces.md | 4 ++-- docs/reference/wasi/wrpc-interfaces.md | 4 ++-- 3 files changed, 20 insertions(+), 20 deletions(-) diff --git a/docs/reference/wasi/incoming-http.md b/docs/reference/wasi/incoming-http.md index 195d3912..49820060 100644 --- a/docs/reference/wasi/incoming-http.md +++ b/docs/reference/wasi/incoming-http.md @@ -105,7 +105,7 @@ corresponding to a clock tick.

                subscribe-instant: func

                Create a pollable which will resolve once the specified instant -occurred.

                +occured.

                Params
                • when: instant
                  • @@ -117,7 +117,7 @@ occurred.

                  subscribe-duration: func

                  Create a pollable which will resolve once the given duration has elapsed, starting at the time at which this function was called. -occurred.

                  +occured.

                  Params
                  • when: duration
                    • @@ -387,7 +387,7 @@ and stream is ready for writing again.

                  [method]output-stream.subscribe: func

                  Create a pollable which will resolve once the output-stream -is ready for more writing, or an error has occurred. When this +is ready for more writing, or an error has occured. When this pollable is ready, check-write will return ok(n) with n>0, or an error.

                  If the stream is closed, this pollable is always ready immediately.

                  @@ -450,7 +450,7 @@ let _ = this.check-write(); // eliding error handling

                [method]output-stream.splice: func

                Read from one stream and write to another.

                -

                The behavior of splice is equivalent to:

                +

                The behavior of splice is equivelant to:

                1. calling check-write on the output-stream
                2. calling read on the input-stream with the smaller of the @@ -676,7 +676,7 @@ an input-stream and the delivery of tra and ensures that the user of this interface may only be consuming either the body contents or waiting on trailers at any given time.

                  resource future-trailers

                  -

                  Represents a future which may eventually return trailers, or an error.

                  +

                  Represents a future which may eventaully return trailers, or an error.

                  In the case that the incoming HTTP Request or Response did not have any trailers, this future will resolve to the empty set of trailers once the complete Request or Response body has been received.

                  @@ -693,12 +693,12 @@ optional trailers) with a static function that consumes the may not write to the body contents after the body has been finished.

                  If the user code drops this resource, as opposed to calling the static method finish, the implementation should treat the body as incomplete, -and that an error has occurred. The implementation should propagate this +and that an error has occured. The implementation should propogate this error to the HTTP protocol by whatever means it has available, including: corrupting the body on the wire, aborting the associated Request, or sending a late status code for the Response.

                  resource future-incoming-response

                  -

                  Represents a future which may eventually return an incoming HTTP +

                  Represents a future which may eventaully return an incoming HTTP Response, or an error.

                  This resource is returned by the wasi:http/outgoing-handler interface to provide the HTTP Response corresponding to the sent Request.

                  @@ -830,7 +830,7 @@ list with the same key.

                3. list<(field-key, field-value)>

              [method]fields.clone: func

              -

              Make a deep copy of the Fields. Equivalent in behavior to calling the +

              Make a deep copy of the Fields. Equivelant in behavior to calling the fields constructor on the return value of entries. The resulting fields is mutable.

              Params
              @@ -1041,7 +1041,7 @@ not a syntactically valid uri authority.

              The returned headers resource is immutable: set, append, and delete operations will fail with header-error.immutable.

              This headers resource is a child: it must be dropped before the parent -outgoing-request is dropped, or its ownership is transferred to +outgoing-request is dropped, or its ownership is transfered to another component by e.g. outgoing-handler.handle.

              Params
                @@ -1207,7 +1207,7 @@ This function will trap if the input-stream

              [method]future-trailers.subscribe: func

              Returns a pollable which becomes ready when either the trailers have -been received, or an error has occurred. When this pollable is ready, +been received, or an error has occured. When this pollable is ready, the get method will return some.

              Params
                @@ -1218,7 +1218,7 @@ the get method will return some.

              • own<pollable>

              [method]future-trailers.get: func

              -

              Returns the contents of the trailers, or an error which occurred, +

              Returns the contents of the trailers, or an error which occured, once the future is ready.

              The outer option represents future readiness. Users can wait on this option to become some using the subscribe method.

              @@ -1227,7 +1227,7 @@ once. It will be success on the first call in which the outer option is some, and error on subsequent calls.

              The inner result represents that either the HTTP Request or Response body, as well as any trailers, were received successfully, or that an -error occurred receiving them. The optional trailers indicates whether +error occured receiving them. The optional trailers indicates whether or not trailers were present in the body.

              When some trailers are returned by this method, the trailers resource is immutable, and a child. Use of the set, append, or @@ -1283,7 +1283,7 @@ given is not a valid http status code.

              The returned headers resource is immutable: set, append, and delete operations will fail with header-error.immutable.

              This headers resource is a child: it must be dropped before the parent -outgoing-request is dropped, or its ownership is transferred to +outgoing-request is dropped, or its ownership is transfered to another component by e.g. outgoing-handler.handle.

              Params
                @@ -1342,7 +1342,7 @@ Content-Length.

              [method]future-incoming-response.subscribe: func

              Returns a pollable which becomes ready when either the Response has -been received, or an error has occurred. When this pollable is ready, +been received, or an error has occured. When this pollable is ready, the get method will return some.

              Params
                @@ -1360,8 +1360,8 @@ the get method will return some.

                once. It will be success on the first call in which the outer option is some, and error on subsequent calls.

                The inner result represents that either the incoming HTTP Response -status and headers have received successfully, or that an error -occurred. Errors may also occur while consuming the response body, +status and headers have recieved successfully, or that an error +occured. Errors may also occur while consuming the response body, but those will be reported by the incoming-body and its output-stream child.

                Params
                diff --git a/docs/reference/wasi/interfaces.md b/docs/reference/wasi/interfaces.md index 6ded1a01..171df898 100644 --- a/docs/reference/wasi/interfaces.md +++ b/docs/reference/wasi/interfaces.md @@ -333,7 +333,7 @@ and stream is ready for writing again.

              [method]output-stream.subscribe: func

              Create a pollable which will resolve once the output-stream -is ready for more writing, or an error has occurred. When this +is ready for more writing, or an error has occured. When this pollable is ready, check-write will return ok(n) with n>0, or an error.

              If the stream is closed, this pollable is always ready immediately.

              @@ -396,7 +396,7 @@ let _ = this.check-write(); // eliding error handling

              [method]output-stream.splice: func

              Read from one stream and write to another.

              -

              The behavior of splice is equivalent to:

              +

              The behavior of splice is equivelant to:

              1. calling check-write on the output-stream
              2. calling read on the input-stream with the smaller of the diff --git a/docs/reference/wasi/wrpc-interfaces.md b/docs/reference/wasi/wrpc-interfaces.md index 0be9351c..6420869a 100644 --- a/docs/reference/wasi/wrpc-interfaces.md +++ b/docs/reference/wasi/wrpc-interfaces.md @@ -633,7 +633,7 @@ and stream is ready for writing again.

                [method]output-stream.subscribe: func

                Create a pollable which will resolve once the output-stream -is ready for more writing, or an error has occurred. When this +is ready for more writing, or an error has occured. When this pollable is ready, check-write will return ok(n) with n>0, or an error.

                If the stream is closed, this pollable is always ready immediately.

                @@ -696,7 +696,7 @@ let _ = this.check-write(); // eliding error handling

                [method]output-stream.splice: func

                Read from one stream and write to another.

                -

                The behavior of splice is equivalent to:

                +

                The behavior of splice is equivelant to:

                1. calling check-write on the output-stream
                2. calling read on the input-stream with the smaller of the From 39a4089337fabfca20ebb8571b10d475dd07f8eb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Viktor=20Sz=C3=A9pe?= Date: Wed, 15 Jan 2025 21:20:55 +0000 Subject: [PATCH 9/9] Revert CLI docs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Viktor Szépe --- docs/cli/wash.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/cli/wash.mdx b/docs/cli/wash.mdx index a3d2337b..d0b9825b 100644 --- a/docs/cli/wash.mdx +++ b/docs/cli/wash.mdx @@ -1426,7 +1426,7 @@ Generate a wasmCloud component project ###### **Options:** -- `--git ` — GitHub repository url. Requires 'git' to be installed in PATH +- `--git ` — Github repository url. Requires 'git' to be installed in PATH - `--subfolder ` — Optional subfolder of the git repository - `--branch ` — Optional github branch. Defaults to "main" - `-p`, `--path ` — Optional path for template project (alternative to --git) @@ -1448,7 +1448,7 @@ Generate a new capability provider project ###### **Options:** -- `--git ` — GitHub repository url. Requires 'git' to be installed in PATH +- `--git ` — Github repository url. Requires 'git' to be installed in PATH - `--subfolder ` — Optional subfolder of the git repository - `--branch ` — Optional github branch. Defaults to "main" - `-p`, `--path ` — Optional path for template project (alternative to --git) @@ -2087,7 +2087,7 @@ Update a component running in a host to a newer version ###### **Arguments:** - `` — Unique ID of the component to update -- `` — Component reference to replace the current running component with, e.g. the absolute file path or OCI URL +- `` — Component reference to replace the current running comonent with, e.g. the absolute file path or OCI URL ###### **Options:**