diff options
| author | Andrew Clayton <a.clayton@nginx.com> | 2024-09-05 16:43:14 +0100 |
|---|---|---|
| committer | Andrew Clayton <a.clayton@nginx.com> | 2024-09-05 16:43:14 +0100 |
| commit | 92ffa9a80c4dbcaa6ee5c82f5c642038f26810d5 (patch) | |
| tree | e2f2c45191721819bcc9dcbb237390e0bacf0bde /LICENSE | |
| parent | 3e0fa223fd8f82d2e518a178f7d02262c99c1e03 (diff) | |
| download | project_blackbird-92ffa9a80c4dbcaa6ee5c82f5c642038f26810d5.tar.gz project_blackbird-92ffa9a80c4dbcaa6ee5c82f5c642038f26810d5.tar.bz2 | |
w-h/0.2.0/echo-request: Update for wasmtime v24.0.0
It seems at some point between wasmtime v17 and v24 the setting of
wasi_http_types_result_own_outgoing_response_error_code_t's val.ok
member became mandatory.
I was seeing an error like
error: hyper::Error(User(Service), guest never invoked `response-outparam::set` method: error while executing at wasm backtrace:
0: 0x313b5 - wit-component:shim!indirect-wasi:http/types@0.2.0-[static]response-outparam.set
1: 0x4f9a - module.wasm!wasi_http_types_static_response_outparam_set
2: 0x6253 - module.wasm!exports_wasi_http_incoming_handler_handle
3: 0x54e4 - module.wasm!__wasm_export_exports_wasi_http_incoming_handler_handle
Caused by:
unknown handle index 0)
Thanks to <https://github.com/cdmurph32> who it seems somehow found this
code and had updated it accordingly.
Link: <https://github.com/cdmurph32/pdf-text-example/blob/main/hello_world.c#L173>
Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
Diffstat (limited to 'LICENSE')
0 files changed, 0 insertions, 0 deletions