-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Issues
is:issue state:open
is:issue state:open
Issue creation is restricted in this repository
Search results
- Status: Open.#13745 In bytecodealliance/wasmtime;
- Status: Open.#13744 In bytecodealliance/wasmtime;
- Status: Open.#13733 In bytecodealliance/wasmtime;
- Status: Open.#13732 In bytecodealliance/wasmtime;
p3_cli_stdout_flushtest might be flakybugIncorrect behavior in the current implementation that needs fixingIncorrect behavior in the current implementation that needs fixingStatus: Open.#13720 In bytecodealliance/wasmtime;- Status: Open.#13714 In bytecodealliance/wasmtime;
Create a macro to define
VM*types, their layout and offsets, and alias-region helperscleanupLabel to track issues for small clean-ups.Label to track issues for small clean-ups.craneliftIssues related to the Cranelift code generatorIssues related to the Cranelift code generatorwasmtimeIssues about wasmtime that don't fall into another labelIssues about wasmtime that don't fall into another labelStatus: Open.#13707 In bytecodealliance/wasmtime;- Status: Open.#13705 In bytecodealliance/wasmtime;
async: missing "in waitable set" trap in sync {stream,future}.cancel-{read,write} and subtask.cancel
bugIncorrect behavior in the current implementation that needs fixingIncorrect behavior in the current implementation that needs fixingStatus: Open.#13690 In bytecodealliance/wasmtime;component-model-error-context: Buggy (?) host can trigger incorrect reference counting
wasm-proposal:component-modelIssues related to the WebAssembly Component Model proposalIssues related to the WebAssembly Component Model proposalwasm-proposal:component-model-error-contextRelated to the error-context feature of componentsRelated to the error-context feature of componentsStatus: Open.#13652 In bytecodealliance/wasmtime;- Status: Open.#13622 In bytecodealliance/wasmtime;
- Status: Open.#13611 In bytecodealliance/wasmtime;