|
Revision tags: dev, v36.0.9, v44.0.1, v43.0.2, v36.0.8, v24.0.8, v44.0.0, v43.0.1, v42.0.2, v36.0.7, v24.0.7, v43.0.0, v42.0.1, v41.0.4, v42.0.0, v40.0.4, v36.0.6, v24.0.6, v41.0.3, v41.0.2, v41.0.1, v36.0.5, v40.0.3, v41.0.0, v36.0.4, v39.0.2, v40.0.2 |
|
| #
1cc0bcff |
| 13-Jan-2026 |
Bailey Hayes <[email protected]> |
feat(p3)!: vendor 0.3.0-rc-2026-01-06 (#12250)
* feat(p3)!: vendor 0.3.0-rc-2026-01-06
Update wasmtime's WASI implementation from version
0.3.0-rc-2025-09-16 to 0.3.0-rc-2026-01-06, using wkg for W
feat(p3)!: vendor 0.3.0-rc-2026-01-06 (#12250)
* feat(p3)!: vendor 0.3.0-rc-2026-01-06
Update wasmtime's WASI implementation from version
0.3.0-rc-2025-09-16 to 0.3.0-rc-2026-01-06, using wkg for WIT vendoring.
This involves API changes in clocks and HTTP.
* Handle some review comments
* Update WASI implementations to avoid `as`
This can have a loss in precision so this shuffles around some types to
ensure that `try_into` and friends are always used instead of `as`. This
changes the source-of-truth for timestamps to be `i64` seconds so WASIp2
is the odd-one-out that can't represent negative timestamps.
* Flag expected WASI failures
* Get wasi:http tests working again
* Rename `proxy` module to `service` to reflect the WIT world.
* Adjust the middleware test to using the `middleware` world.
---------
Co-authored-by: Alex Crichton <[email protected]>
show more ...
|
|
Revision tags: v40.0.1, v40.0.0, v39.0.1, v39.0.0, v38.0.4, v37.0.3, v36.0.3, v24.0.5, v38.0.3, v38.0.2, v38.0.1, v37.0.2 |
|
| #
7e39c25e |
| 06-Oct-2025 |
Joel Dice <[email protected]> |
move `ConcurrentState` from `ComponentInstance` to `Store` (#11796)
* move `ConcurrentState` from `ComponentInstance` to `Store`
This has a few benefits:
- No need to specify an instance when crea
move `ConcurrentState` from `ComponentInstance` to `Store` (#11796)
* move `ConcurrentState` from `ComponentInstance` to `Store`
This has a few benefits:
- No need to specify an instance when creating or piping from a stream or future.
- No need to track the instance in an `Accessor`.
- You may now execute tasks for multiple instances in a single event loop.
The main drawback is that, if one of several instances within a single store
traps, it effectively means all instances have trapped, and the store can't be
used to create new instances. The way to avoid that is to use separate stores
for instances which must be isolated from others.
As a result of this change, a lot of code had to move from e.g. `impl Instance`
to e.g. `impl StoreOpaque`, so the diff is pretty huge, but the changes
themselves are almost entirely non-functional.
Fixes #11226
Signed-off-by: Joel Dice <[email protected]>
* fix non-component-model-async build
Signed-off-by: Joel Dice <[email protected]>
* fix outdated doc comment
Signed-off-by: Joel Dice <[email protected]>
* address review feedback
- restore `ComponentStoreData` encapsulation
- avoid conditional code duplication in `LiftContext::new`
Signed-off-by: Joel Dice <[email protected]>
---------
Signed-off-by: Joel Dice <[email protected]>
show more ...
|
| #
ad027ea1 |
| 01-Oct-2025 |
Joel Dice <[email protected]> |
check for host-body-wrapped-in-guest-body when creating requests (#11775)
This is a follow-up to https://github.com/bytecodealliance/wasmtime/pull/11763,
where we did this for responses, but I didn'
check for host-body-wrapped-in-guest-body when creating requests (#11775)
This is a follow-up to https://github.com/bytecodealliance/wasmtime/pull/11763,
where we did this for responses, but I didn't think to do it for requests as
well. Now we do it for both, and test the scenario where a proxy component
forwards a inbound request body to an outbound request and then exits before
that body has finished streaming, in which case the stream should continue
flowing (assuming the embedder _wants_ it to).
Signed-off-by: Joel Dice <[email protected]>
show more ...
|