hydai
hydai
The PR #4340 has been merged into the master branch. All milestones in this issue are completed. Closing it.
We currently don't support these kinds of statistics, but a PR is welcome.
> [@CaptainVincent](https://github.com/CaptainVincent) I have reproduced the issue. I'm new to this, can't we add a null spdlog check in the wasi_logging plugin ? The problem is not just a null...
Blocked with the same issue: https://github.com/WasmEdge/WasmEdge/issues/3828
@ibmibmibm Can we check the LLVM version first? If it is less than 19, then use the old method. Otherwise, proceed with the new method.
It looks like a bug when we are implementing the networking-related features in the WASI component. I think it could be resolved if we change how the macOS-related system calls...
It's not assigned before, but it's yours now :-).
1. Use the reported example to reproduce the situation. 2. If the non-blocking IO keeps the CPU at 100%, then you need to investigate which function is stuck. 3. Once...
I don't know; maybe you can try to reproduce the same workload to see if it is resolved or not.
Hi @vatsalkeshav Please raise an issue to the related repository.