Closed liudonghua123 closed 1 year ago
Hey @liudonghua123 thanks a lot for the interest and reporting this.
The problem comes form wasmer
not being fully compliant to the latest preview1
ABI.
sock_accept
got added some time after the initial preview1
release and is already supported by latest versions of major runtimes like wasmtime
, wamr
, wazero
, node,js
(listed in order I tried them).
We built python.wasm
on top of wasi-libc
which depends on this method.
As I see this has been fixed for the latest wasmer (and you have also verified it) - https://github.com/wasmerio/wasmer/issues/3170
Therefore I will be closing this issue.
Is your feature request related to a problem? Please describe.
I tried to execute
python-3.11.3.wasm
download from https://github.com/vmware-labs/webassembly-language-runtimes/releases/tag/python%2F3.11.3%2B20230428-7d1b259 within my wasmer, but it failed with the following errors.And I read https://wasmlabs.dev/articles/python-wasm32-wasi/, and it seems
python-3.11.3.wasm
can be run onwasmtime
only andpython-3.11.3-wasmedge.wasm
can be run onwasmedge
.I have also problems when running on wasmedge on windows for --dir option. see https://github.com/WasmEdge/WasmEdge/issues/1918.
Is there any plans to support wasmer.
Describe the solution you'd like
N.A.
Describe alternatives you've considered
No response
Additional context
No response