Mark McCaskey
Mark McCaskey
Hello! I've run a lot of a AssemblyScript Wasm modules while working on Wasmer's WASI implementation and noticed that AssemblyScript doesn't seem to do the same kind of filesystem setup...
Release script may fail to publish crate but then move on to publish the next one. We should track which crates have failed and report it at the end. Additionally...
We are currently testing WASI with our own test suite at https://github.com/wasmerio/wasi-tests We should ensure that Wasmer is passing tests on other test suites and perhaps run them in CI...
#1687 fixes a bug that is most easily observable with dynamic memory. Unfortunately the Wasmer API does not have a direct way to get access to a dynamic memory (it's...
Hello! I ran into an issue with libwasm.dylib not working with the latest wasm.h when testing out some code I wrote against the Wasm C API so I tried to...
The Wapm update notification will display the wrong thing if the value stored there is out of date. For example if the value in the `$WASMER_DIR/.wapm_update.json` is `1.0.0-alpha3` and we're...
In the init command and possibly elsewhere, we assume WASI `0.0.0-unstable` we should default to the latest published (the new interface `0.1.0-unstable`) or support detecting the it from the Wasm...
Reported in https://github.com/wasmerio/wasmer/issues/1340 ; even if it can't be reproduced we should structure things such that it works despite any possible network errors.
It'd be nice to be able to install globally from a local package, something like `wapm install --path .` or something. Suggested by @torch2424
@torch2424 ran into an issue with `source` being a relative path that started with `../..` and was outside the manifest directory. The error message they got was vague enough that...