http-response wasip3 test fails after toolchain, wit-bindgen, wasmtime update

[wingo]

This was working before when run on wasmtime / ubuntu but not any more. Noting it here.

wasmtime -Wcomponent-model-async -Sp3,http tests/rust/testsuite/wasm32-wasip3/http-response.wasm

thread 'main' (1) panicked at ~/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/wit-bindgen-0.48.1/src/rt/async_support/waitable.rs:193:13:
assertion failed: !task.is_null()
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: failed to run main module `tests/rust/testsuite/wasm32-wasip3/http-response.wasm`

Caused by:
    0: failed to invoke `run` function
    1: error while executing at wasm backtrace:
           0:  0x29fbb - http_response-d4a95fc181e65bf8.wasm!abort
           1:  0x250a1 - http_response-d4a95fc181e65bf8.wasm!std[beec1ff74d5a319]::sys::pal::wasip2::helpers::abort_internal
           2:  0x24198 - http_response-d4a95fc181e65bf8.wasm!std[beec1ff74d5a319]::process::abort
           3:  0x24791 - http_response-d4a95fc181e65bf8.wasm!__rustc[9859e6116a3aec88]::__rust_abort
           4:  0x2293d - http_response-d4a95fc181e65bf8.wasm!__rustc[9859e6116a3aec88]::__rust_start_panic
           5:  0x245a8 - http_response-d4a95fc181e65bf8.wasm!__rustc[9859e6116a3aec88]::rust_panic
           6:  0x23968 - http_response-d4a95fc181e65bf8.wasm!std[beec1ff74d5a319]::panicking::panic_with_hook
           7:  0x234f5 - http_response-d4a95fc181e65bf8.wasm!std[beec1ff74d5a319]::panicking::panic_handler::{closure#0}
           8:  0x23488 - http_response-d4a95fc181e65bf8.wasm!std[beec1ff74d5a319]::sys::backtrace::__rust_end_short_backtrace::<std[beec1ff74d5a319]::panicking::panic_handler::{closure#0}, !>
           9:  0x24874 - http_response-d4a95fc181e65bf8.wasm!__rustc[9859e6116a3aec88]::rust_begin_unwind
          10:  0x2af1a - http_response-d4a95fc181e65bf8.wasm!core[33dee4f7fc19f5e5]::panicking::panic_fmt
          11:  0x2ae8d - http_response-d4a95fc181e65bf8.wasm!core[33dee4f7fc19f5e5]::panicking::panic
          12:   0x2389 - http_response-d4a95fc181e65bf8.wasm!<wit_bindgen[883b1e0655282489]::rt::async_support::waitable::WaitableOperation<wit_bindgen[883b1e0655282489]::rt::async_support::future_support::FutureWriteOp<&wit_bindgen[883b1e0655282489]::rt::async_support::future_support::FutureVtable<core[33dee4f7fc19f5e5]::result::Result<core[33dee4f7fc19f5e5]::option::Option<http_response[d277b285c5cd3b9f]::wasi::http::types::Fields>, http_response[d277b285c5cd3b9f]::wasi::http::types::ErrorCode>>>>>::register_waker
          13:   0x2210 - http_response-d4a95fc181e65bf8.wasm!<wit_bindgen[883b1e0655282489]::rt::async_support::waitable::WaitableOperation<wit_bindgen[883b1e0655282489]::rt::async_support::future_support::FutureWriteOp<&wit_bindgen[883b1e0655282489]::rt::async_support::future_support::FutureVtable<core[33dee4f7fc19f5e5]::result::Result<core[33dee4f7fc19f5e5]::option::Option<http_response[d277b285c5cd3b9f]::wasi::http::types::Fields>, http_response[d277b285c5cd3b9f]::wasi::http::types::ErrorCode>>>>>::poll_complete_with_code
          14:   0x1ce6 - http_response-d4a95fc181e65bf8.wasm!<wit_bindgen[883b1e0655282489]::rt::async_support::waitable::WaitableOperation<wit_bindgen[883b1e0655282489]::rt::async_support::future_support::FutureWriteOp<&wit_bindgen[883b1e0655282489]::rt::async_support::future_support::FutureVtable<core[33dee4f7fc19f5e5]::result::Result<core[33dee4f7fc19f5e5]::option::Option<http_response[d277b285c5cd3b9f]::wasi::http::types::Fields>, http_response[d277b285c5cd3b9f]::wasi::http::types::ErrorCode>>>>>::poll_complete
          15:  0x14281 - http_response-d4a95fc181e65bf8.wasm!<wit_bindgen[883b1e0655282489]::rt::async_support::future_support::RawFutureWrite<&wit_bindgen[883b1e0655282489]::rt::async_support::future_support::FutureVtable<core[33dee4f7fc19f5e5]::result::Result<core[33dee4f7fc19f5e5]::option::Option<http_response[d277b285c5cd3b9f]::wasi::http::types::Fields>, http_response[d277b285c5cd3b9f]::wasi::http::types::ErrorCode>>> as core[33dee4f7fc19f5e5]::future::future::Future>::poll
          16:  0x13b97 - http_response-d4a95fc181e65bf8.wasm!<<wit_bindgen[883b1e0655282489]::rt::async_support::future_support::RawFutureWriter<_>>::write_and_forget::DeferredWrite<&wit_bindgen[883b1e0655282489]::rt::async_support::future_support::FutureVtable<core[33dee4f7fc19f5e5]::result::Result<core[33dee4f7fc19f5e5]::option::Option<http_response[d277b285c5cd3b9f]::wasi::http::types::Fields>, http_response[d277b285c5cd3b9f]::wasi::http::types::ErrorCode>>> as alloc[a9355aac28f1dd52]::task::Wake>::wake
          17:  0x1395e - http_response-d4a95fc181e65bf8.wasm!<wit_bindgen[883b1e0655282489]::rt::async_support::future_support::RawFutureWriter<&wit_bindgen[883b1e0655282489]::rt::async_support::future_support::FutureVtable<core[33dee4f7fc19f5e5]::result::Result<core[33dee4f7fc19f5e5]::option::Option<http_response[d277b285c5cd3b9f]::wasi::http::types::Fields>, http_response[d277b285c5cd3b9f]::wasi::http::types::ErrorCode>>>>::write_and_forget
          18:   0x63f2 - http_response-d4a95fc181e65bf8.wasm!<wit_bindgen[883b1e0655282489]::rt::async_support::future_support::FutureWriter<core[33dee4f7fc19f5e5]::result::Result<core[33dee4f7fc19f5e5]::option::Option<http_response[d277b285c5cd3b9f]::wasi::http::types::Fields>, http_response[d277b285c5cd3b9f]::wasi::http::types::ErrorCode>> as core[33dee4f7fc19f5e5]::ops::drop::Drop>::drop
          19:   0x631d - http_response-d4a95fc181e65bf8.wasm!core[33dee4f7fc19f5e5]::ptr::drop_in_place::<wit_bindgen[883b1e0655282489]::rt::async_support::future_support::FutureWriter<core[33dee4f7fc19f5e5]::result::Result<core[33dee4f7fc19f5e5]::option::Option<http_response[d277b285c5cd3b9f]::wasi::http::types::Fields>, http_response[d277b285c5cd3b9f]::wasi::http::types::ErrorCode>>>
          20:   0x72e9 - http_response-d4a95fc181e65bf8.wasm!http_response[d277b285c5cd3b9f]::main
          21:   0x6a26 - http_response-d4a95fc181e65bf8.wasm!<fn() as core[33dee4f7fc19f5e5]::ops::function::FnOnce<()>>::call_once
          22:  0x1f8b7 - http_response-d4a95fc181e65bf8.wasm!std[beec1ff74d5a319]::sys::backtrace::__rust_begin_short_backtrace::<fn(), ()>
          23:   0x574e - http_response-d4a95fc181e65bf8.wasm!std[beec1ff74d5a319]::rt::lang_start::<()>::{closure#0}
          24:  0x24dcc - http_response-d4a95fc181e65bf8.wasm!std[beec1ff74d5a319]::rt::lang_start_internal
          25:   0x5714 - http_response-d4a95fc181e65bf8.wasm!std[beec1ff74d5a319]::rt::lang_start::<()>
          26:   0x7456 - http_response-d4a95fc181e65bf8.wasm!__main_void
          27:   0x1741 - http_response-d4a95fc181e65bf8.wasm!_start
          28: 0x3e5f9a - <unknown>!wasi:cli/run@0.2.6#run
       note: using the `WASMTIME_BACKTRACE_DETAILS=1` environment variable may show more debugging information
    2: wasm trap: wasm `unreachable` instruction executed

[wingo]

This appears to be due to a wit-bindgen update in which dropping a the writer side of a wit_future will attempt to write a tombstone on the channel, but then it panics because there is no task to receive the value being written. It's not a WASI or component-model requirement. See bytecodealliance/wit-bindgen#1456.

To be fair, in rust you really want to be in an async context when working with this interface, so perhaps it's not an unreasonable requirement. And in the context of these tests, perhaps it's being in an async fn is not too thick of a layer on top of WASI so as to obscure what is being tested. Will poke.