spinframework / spinframework/spin
Use `YieldCustom` / `tokio::task::yield_now()` for epoch interruption
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
See https://github.com/bytecodealliance/wasmtime/issues/10667
Bonus points for verifying that a thread can currently be blocked by a CPU-busy guest (calling no host imports; sleep doesn't cut it!) before making this change, as a confirmation and regression test.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Wasmtime issue and investigate whether a CPU-busy guest that makes no host imports can currently block a thread; use that scenario as the regression test. Then evaluate the proposed YieldCustom or tokio::task::yield_now() approach, with done meaning epoch interruption handles the case and the test confirms the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100