Stream: git-wasmtime

Topic: wasmtime / issue #6212 [wasmtime-fiber] Cancel an async f...

Wasmtime GitHub notifications bot (Apr 14 2023 at 07:31):

apepkuss opened issue #6212:

I experimented with the async task cancellation when the given time's out. The following panic message is thrown:

thread 'tokio-runtime-worker' panicked at 'fiber dropped without finishing', /root/.cargo/registry/src/mirrors.tuna.tsinghua.edu.  cn-df7c3c540f42cdbd/wasmtime-fiber-6.0.1/src/lib.rs:164:9

By following the panic message, I found the line 162-166 in wasmedge-fiber use debug_assert! to catch the yields during execution. Is there any more friendly way to deal with such cases? Thanks!

Wasmtime GitHub notifications bot (Apr 14 2023 at 15:13):

pchickey commented on issue #6212:

Thanks for the report. I need more information to reproduce this, can you make a small test case that shows the sort of cancellation that reaches this panic?

Wasmtime GitHub notifications bot (Jul 28 2025 at 20:50):

alexcrichton closed issue #6212:

I experimented with the async task cancellation when the given time's out. The following panic message is thrown:

thread 'tokio-runtime-worker' panicked at 'fiber dropped without finishing', /root/.cargo/registry/src/mirrors.tuna.tsinghua.edu.  cn-df7c3c540f42cdbd/wasmtime-fiber-6.0.1/src/lib.rs:164:9

By following the panic message, I found the line 162-166 in wasmedge-fiber use debug_assert! to catch the yields during execution. Is there any more friendly way to deal with such cases? Thanks!

Wasmtime GitHub notifications bot (Jul 28 2025 at 20:50):

alexcrichton commented on issue #6212:

I'm going to close this as it's an old issue without a follow up, but can of course reopen with a follow-up.

Last updated: Dec 13 2025 at 19:03 UTC