not implemented: wasi::platform_clock_time_get(wasi::Clockid::ProcessCputimeId, ..)', lib\wasi\src\syscalls\windows.rs:45:13

[koduki]

Describe the bug

I executed WASM generated from ruby, it works on Linux. But it doesn't work on Windows 11 and wasmer 3.1.0.
I might similar #3384, same WASM doesn't work on Linux and 3.0.2, and it was fixed on linux and 3.1.0.

echo "`wasmer -V` | `rustc -V` | `uname -m`"

Steps to reproduce

Same with below.
ruby/ruby.wasm#116

Expected behavior

Success run.

$ wasmer run ./my-ruby-app.wasm -- /src/my_app.rb
Hello

Actual behavior

C:\Users\koduki\git\example-wasm>wasmer run ./my-ruby-app.wasm -- /src/my_app.rb
thread 'main' panicked at 'not implemented: wasi::platform_clock_time_get(wasi::Clockid::ProcessCputimeId, ..)', lib\wasi\src\syscalls\windows.rs:45:13
stack backtrace:
0: 0x7ff6bcc7d14f -
1: 0x7ff6bcca4a4a -
2: 0x7ff6bcc72729 -
3: 0x7ff6bcc7fc1b -
4: 0x7ff6bcc7f89b -
5: 0x7ff6bcc801c9 -
6: 0x7ff6bcc800cd -
7: 0x7ff6bcc7dd87 -
8: 0x7ff6bcc7fda9 -
9: 0x7ff6bdf1a585 -
10: 0x7ff6bc26f3cc -
11: 0x7ff6bbc20b88 -
12: 0x7ff6bbcae288 -
13: 0x7ff6bbcb9fb8 -
14: 0x7ff6bbd997cd -
15: 0x7ff6bc70e6f2 -
16: 0x7ff6bbd7898b -
17: 0x7ff6bbba467b -
18: 0x15f170c5349 -
19: 0x15f1709061b -
20: 0x15f15d33da5 -
21: 0x15f170fa6b4 -
22: 0x15f170fe33a -
23: 0x7ff6bc70b971 -
24: 0x7ff6bc70b2f8 -
25: 0x7ff6bc70b32c -
26: 0x7ff6bc70e77b -
27: 0x7ff6bc707ce0 -
28: 0x7ff6bbd29ecf -
29: 0x7ff6bbbc278e -
30: 0x7ff6bbbc4c43 -
31: 0x7ff6bbbc20bc -
32: 0x7ff6bbbc7a11 -
33: 0x7ff6bbb4e2fd -
34: 0x7ff6bbb4db57 -
35: 0x7ff6bbb31006 -
36: 0x7ff6bbb3105c -
37: 0x7ff6bcc67ea1 -
38: 0x7ff6bbb31047 -
39: 0x7ff6bdec87e8 -
40: 0x7ff988135550 - BaseThreadInitThunk
41: 0x7ff9886e485b - RtlUserThreadStart

Additional context

[Michael-F-Bryan]

Thanks for finding this @koduki! This will probably be implemented when #3422 is merged.

CC: @theduke

[koduki]

Thank you for your comment! I'm look forward to that merge.

[theduke]

Also related, for future reference: #3388

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

Feel free to reopen the issue if it has been closed by mistake.