bump wasmedge-sdk from 0.13.2 to 0.14.0

[CaptainVincent]

The corresponding WasmEdge lib release is 0.14.1.

[jprendes]

@CaptainVincent , do you know why the returned exit_code is different from the expected value?

[CaptainVincent]

Not sure yet, I'm still looking into this part.

[jprendes]

I've been looking into this.
Exit code 11 is usually related to a segmentation fault.

The code reaches the vm.run_func call, and aborts inside that function.
Furthermore, inside of run_func, the code reaches the executor.call_func call, and aborts inside that function.
Furthermore, inside of call_func, the code reaches the ffi::WasmEdge_ExecutorInvoke call, and aborts inside that function.

I'm not sure what could be leading to a segmentation fault inside the C++ codebase.

[CaptainVincent]

I have tried to simplify the part where I integrate WasmEdge and run it in a pure environment. Based on cross-validation, it seems that some configurations are missing in the integration part. I will fix the exit code issue as soon as possible. The Windows part is more complicated, and I'm not sure if the issue is related to the FFI generated by bindgen, because based on my inspection, there doesn’t seem to be much difference in the headers for the release across different platforms.

[jprendes]

I think the windows issue is due to the wrong WasmEdge version installed in CI.
Unlike Linux, the standalone feature doesn't work on Windows, requiring us to install it manually in CI.

[jprendes]

@CaptainVincent , do you know what changed? Why is it working now?

[CaptainVincent]

To avoid crashes, I temporarily removed the following:

PluginManager::load(None)?;
PluginManager::auto_detect_plugins()?;

I will submit a separate PR to add support for the plugin feature. Currently, I am still debugging this functionality, which is needed to support plugins like wasi_nn and similar.

--

Additionally, I modified the setup-windows.sh script, but it still doesn’t seem to work for windows ci. Could it be that some caching mechanisms are causing the issue to persist? Because the Windows lint is working.

[CaptainVincent]

The previous force push failure related to Windows really seems to be about the cached issue. After I rebase it, it's all good now.

[Mossaka]

LGTM!

[jprendes]

LGTM