Use `Waker::noop` from Rust 1.85 (#10804)

Now possible after #10785

Initial implementation of Wasi-tls (Transport Layer Security) (#10249)

* Initial implementation of wasi-tls

This crate provides the Wasmtime host implementation for the [wasi-tls] API.
The [wasi-t

Initial implementation of Wasi-tls (Transport Layer Security) (#10249)

* Initial implementation of wasi-tls

This crate provides the Wasmtime host implementation for the [wasi-tls] API.
The [wasi-tls] world allows WebAssembly modules to perform SSL/TLS operations,
such as establishing secure connections to servers. TLS often relies on other wasi networking systems
to provide the stream so it will be common to enable the [wasi:cli] world as well with the networking features enabled.

The initial implemntation is using rustls.

Signed-off-by: James Sturtevant <[email protected]>

* Remove configuration object for now

Signed-off-by: James Sturtevant <[email protected]>

* Update cargo patch to use temp branch

Signed-off-by: James Sturtevant <[email protected]>

* Rename tcp streams to wasistreams to be more generic

Signed-off-by: James Sturtevant <[email protected]>

* gate the wasi-tls ctx behind a feature

Signed-off-by: James Sturtevant <[email protected]>

* cleanup and clippy fixes

Signed-off-by: James Sturtevant <[email protected]>

* Fix issue when another pollable cancels

Signed-off-by: James Sturtevant <[email protected]>

* prtest:full

Signed-off-by: James Sturtevant <[email protected]>

* Skip test on riscv64/s390x

Signed-off-by: James Sturtevant <[email protected]>

* Drop debug info to support tests on pulley based platforms

Signed-off-by: James Sturtevant <[email protected]>

* Update signature of `close-notify`

* Use draft version

Signed-off-by: James Sturtevant <[email protected]>

* Remove patches

Signed-off-by: James Sturtevant <[email protected]>

* Ungate tls on riscv64 and s390x

* Un-gate wais-http on riscv64/s390x as well

* Add wasmtime-wasi-tls to publish list

* Add wasmtime-wasi-tls to public API crate list

* Revert some changes to Cargo.lock

---------

Signed-off-by: James Sturtevant <[email protected]>
Signed-off-by: James Sturtevant <[email protected]>
Co-authored-by: badeend <[email protected]>
Co-authored-by: Alex Crichton <[email protected]>

show more ...

Fix typo (#9991)

Leverage Rust 1.79, 1.80 (#9498)

This commit is a follow-up to #9496 to leverage various APIs that the
workspace now has access to. For example most dependencies on the
`once_cell` crate are now rem

Leverage Rust 1.79, 1.80 (#9498)

This commit is a follow-up to #9496 to leverage various APIs that the
workspace now has access to. For example most dependencies on the
`once_cell` crate are now removed in favor of the types stabilized in
the standard library: `LazyLock` and `LazyCell`. One dependency remains
in the `wasmtime` crate due to the `get_or_try_init` not being stable
yet.

Some additional helper methods on raw pointer slices are also available
for removing a few minor `unsafe` blocks.

show more ...

wasi-sockets: Fix `shutdown` bugs (#9225)

* Rename:
LastWrite -> WriteState,
Done -> Ready,
Waiting -> Writing

* Wrap the TCP streams inside a mutex.
And rename `abort_wait` to `cancel`

* Move shu

wasi-sockets: Fix `shutdown` bugs (#9225)

* Rename:
LastWrite -> WriteState,
Done -> Ready,
Waiting -> Writing

* Wrap the TCP streams inside a mutex.
And rename `abort_wait` to `cancel`

* Move shutdown into the stream types

* Fix Linux-specific peculiarity where `recv` continues to work even after `shutdown(sock, SHUT_RD)` has been called.

* Refactor poll_cancel

* Fix data loss issue.
Calling `shutdown` _after_ data has been accepted by `write`, but _before_ it has been fully flushed, caused the in-flight data to be lost.

* Simplify poll_cancel

* Use tokio::sync::Mutex instead of std::sync::Mutex so I can revert to regular async code

show more ...

wasi-filesystem: Implement `HostInputStream` & `HostOutputStream` (#9129)

* Add the ability to generate async drop methods for resources.

In the component model, `resource.drop` is a canonical buil

wasi-filesystem: Implement `HostInputStream` & `HostOutputStream` (#9129)

* Add the ability to generate async drop methods for resources.

In the component model, `resource.drop` is a canonical built-in without a proper name. So I invented a custom naming scheme for the component bindgen config. I went with:
`"[drop]{resource-name}"` where `{resource-name}` is the name as defined in WIT. e.g. `"[drop]input-stream"`.

This shouldn't conflict with anything existing in the wild as WIT identifiers are not allowed to contain square brackets.

* Make `input-stream::drop` & `output-stream::drop` async

* Prevent the guest from (inadvertently) spawning an unlimited amount of background tasks through the FileOutputStream

* Properly clean up background tasks for even more types of I/O streams.
Unlike FileOutputStream, the background tasks of these stream types are truly async. So aborting _without_ awaiting them was probably already good enough in practice. Nonetheless, waiting for the background to actually shut down just seems like good resource management "hygiene" to me.

* Let HostInput/OutputStream provide specialized blocking_* implementations.

* Rename filesystem's `spawn_blocking` -> `run_blocking`

* Implement specialized `blocking_write_and_flush` for FileOutputStream.

- `write` now always spawns the syscall on a background task, regardless of `allow_blocking_current_thread`.
- `blocking_write_and_flush` is newly overridden and continues to do the `allow_blocking_current_thread` trickery that `write` used to do.

* Implement `HostInputStream` for `FileInputStream`.
- `read` always spawns the syscall on a background task, regardless of `allow_blocking_current_thread`.
- `blocking_read` performs the `run_blocking`/`allow_blocking_current_thread` trickery.

* In Preview1 adapter: ignore BlockingMode and always perform blocking I/O, as that's what preview1 did.

* Remove special case for FileInputStream and change InputStream enum to be a type alias, just like OutputStream

* Remove `[method]output-stream.forward` from bindgen config. It does not exist.

* Refactor `blocking_splice` to take advantage of specialized `blocking_read` & `blocking_write_and_flush` implementations

* Defer to regular `read` from within `blocking_read` to reduce duplication of logic.

show more ...

wasmtime-wasi-http: provide Debug impls in all pub types (#8979)

* wasmtime-wasi: derive(Debug) on AbortOnDropJoinHandle

* wasmtime_wasi_http: derive(Debug) on all pub types and their contents

Use a multi-threaded Tokio runtime as a fallback (#8229)

This commit fixes a bug that was introduced in #8190 and brought up on
[Zulip]. In #8190 there was a subtle change in how Tokio and the CLI a

Use a multi-threaded Tokio runtime as a fallback (#8229)

This commit fixes a bug that was introduced in #8190 and brought up on
[Zulip]. In #8190 there was a subtle change in how Tokio and the CLI are
managed, namely that a Tokio runtime is installed at the start of the
CLI to avoid entering/exiting the runtime on each blocking call. This
had a small performance improvement relative to entering/exiting on each
blocking call. This meant, though, that calls previously blocked with
`Runtime::block_on` and now block with `Handle::block_on`. The
[documentation of `Handle::block_on`][doc] has a clause that says that
for single-threaded runtimes I/O and timers won't work.

To fix this issue I've switch the fallback runtime to a multi-threaded
runtime to ensure that I/O and timers continue to work.

[Zulip]: https://bytecodealliance.zulipchat.com/#narrow/stream/219900-wasi/topic/Wasi-http.20requests.20hang/near/429187256
[doc]: https://docs.rs/tokio/latest/tokio/runtime/struct.Handle.html#method.block_on

show more ...

wasmtime-wasi: move bindings to its own file, move runtime to its own mod (#8045)

* move bindings to its own file, move runtime to its own mod

* fix