https://github.com/WasmEdge/WasmEdge summary

[jaykchen]

Installer does not work on Fish shell https://github.com/WasmEdge/WasmEdge/issues/2749 Issue: Installer does not work on Fish shell

The issue is that a backward incompatible change has been introduced in a commit, breaking the installation for shells different from bash and zsh, which were previously working successfully. The user expects a successful installation.

Potential solutions:

• The user has raised the issue and is awaiting a response from the developers.
• User '.alabulei1' has tagged the developers and requested their attention.

• It is implied that the developers, 'SAtacker' and 'hydai', need to investigate and fix the issue.

                  this result is generated by flows.network. Triggered by @jaykchen

[jaykchen]

Wasmedge may have a performance error when handling a non-WASI wasm binary. https://github.com/WasmEdge/WasmEdge/issues/2748 The central problem discussed in the issue is that Wasmedge, when processing a non-WASI wasm binary, is slower compared to other runtimes like wasmtime and wasmer. The user provided a wasm binary file as an example. The main solutions proposed or agreed upon are not mentioned in the post.

                    this result is generated by flows.network. Triggered by @jaykchen

[jaykchen]

Abortion report on the instruction memory.grow https://github.com/WasmEdge/WasmEdge/issues/2745 The central problem discussed in the issue is an abortion report on the instruction memory.grow in the WasmEdge project. The user provides the current state and expected behavior, along with the steps to reproduce the issue. Another user comments that they cannot reproduce the issue on their testing platform. The main solutions proposed or agreed upon are not explicitly mentioned in the issue content.

                    this result is generated by flows.network. Triggered by @jaykchen

[jaykchen]

Crash report about the instruction table.init https://github.com/WasmEdge/WasmEdge/issues/2744 The central problem discussed in the issue is a crash report related to the instruction table.init. The user expects an exception indicating "OOB" (out of bounds) to be raised instead of a segmentation fault. The main solution proposed is for an internal handler to catch this error and prevent the segmentation fault.

                    this result is generated by flows.network. Triggered by @jaykchen

[jaykchen]

Crash report about the instruction memory.init https://github.com/WasmEdge/WasmEdge/issues/2743 The central problem discussed in the issue is a crash report related to the instruction memory.init in the WasmEdge project. The user expects an exception indicating "OOB" (out-of-bounds) to be raised instead of a segmentation fault. The hardware architecture is amd64, and the operating system is Ubuntu 20.04. One suggested solution is for the crash to be caught by an internal handler rather than triggering a segmentation fault.

                    this result is generated by flows.network. Triggered by @jaykchen

[jaykchen]

Do not terminate while executing the given testcase https://github.com/WasmEdge/WasmEdge/issues/2733 The central problem discussed in the issue is that while executing a given testcase, WasmEdge hangs and does not terminate. Other wasm runtimes like Wasmer, Wasmtime, and Wasmi also have issues with this testcase. The expected result is unclear due to a lack of understanding of WebAssembly. The main suggested solution is for the maintainer (@hydai) to investigate the problem.

                    this result is generated by flows.network. Triggered by @jaykchen

[jaykchen]

feat: LFX create a ffmpeg plugin https://github.com/WasmEdge/WasmEdge/issues/2689 Issue: feat: LFX create a ffmpeg plugin Label: LFX Mentorship

The issue discusses the need to improve the performance of the mediapipe-rs project, which currently uses Wasm-compiled ffmpeg functions. The proposed solution is to create a ffmpeg plugin for WasmEdge, allowing Wasm applications to call native ffmpeg functions. The expected outcomes include developing the plugin, a Rust SDK for Wasm programs to access ffmpeg functions, and refactoring the mediapipe-rs project. The deliverables should cover at least 80% of all ffmpeg functions and have comprehensive unit tests and documentation. The recommended skills include C

                    this result is generated by flows.network. Triggered by @jaykchen

[jaykchen]

OSPP: Enabling WasmEdge Compilation with MSVC Toolchain https://github.com/WasmEdge/WasmEdge/issues/2629 The central problem discussed in the issue is enabling WasmEdge compilation with the MSVC toolchain. The main solutions proposed include fixing compilation errors, modifying the code to avoid designated initializers, rewriting SIMD-related instructions with unrolling, and creating a workflow for MSVC build.

                    this result is generated by flows.network. Triggered by @jaykchen

[jaykchen]

[Feature] [binding-java] Publish java to maven repository https://github.com/WasmEdge/WasmEdge/issues/2596 Issue: '[Feature] [binding-java] Publish java to maven repository' User 'liangyuanpeng' opened this issue to propose the addition of a feature to publish Java for WasmEdge to the Maven repository. The motivation behind this is to make it easier for users to use WasmEdge.

@sarthaksarthak9 requested more details regarding the issue, and @Hrushi20 showed interest in working on it. They suggested the following solutions:

1. Registering WasmEdge with Sonatype to create a namespace.
2. Creating PGP keys for signing.

3. Adding the feature to the pipelines

                   this result is generated by flows.network. Triggered by @jaykchen

[jaykchen]

LFX Workspace: A stream log processing framework for WasmEdge https://github.com/WasmEdge/WasmEdge/issues/2552 The central problem discussed in the issue is the development of a stream log processing framework for WasmEdge. The goal is to provide a framework that can collect, transform, and route logs from various services. The main solutions proposed include designing and implementing the components of the framework such as collectors, transformers, dispatchers, and routers. The use of custom events and event routing is also discussed. Additionally, there are suggestions to explore options for custom transformers, add support for log collection from files, and investigate the possibility of creating a WasmEdge plugin for filesystem notifications.

                    this result is generated by flows.network. Triggered by @jaykchen

[jaykchen]

LFX Workspace: Support Tensorflow and PyTorch in WasmEdge’s Python runtime https://github.com/WasmEdge/WasmEdge/issues/2545 The central problem discussed in the issue is the need to support Tensorflow and PyTorch in WasmEdge's Python runtime for lightweight deployment of AI applications. The proposed solution includes incorporating WasmEdge's NN extensions into the Python interpreter, creating CPython wrappers for host functions, and creating high-level Python wrapper functions. The aim is to create a demoable solution at the end of each milestone and provide detailed documentation and tutorials.

                    this result is generated by flows.network. Triggered by @jaykchen

[jaykchen]

Support "Named Models" in WASI NN https://github.com/WasmEdge/WasmEdge/issues/2504 The central problem discussed in the issue is the lack of a way to deregister registered models in the Named Models feature of WASI NN. The main solution proposed is to implement an extension function to address this limitation. Additionally, there is mention of implementing a superset of the official spec and waiting for the release of wasi-nn before opening a PR for review.

                    this result is generated by flows.network. Triggered by @jaykchen

[jaykchen]

https://github.com/WasmEdge/WasmEdge summary https://github.com/jaykchen/a-test/issues/68 Issue: 'https://github.com/WasmEdge/WasmEdge summary'

1. Installer does not work on Fish shell. Potential solutions include awaiting a response from developers and requesting their attention.
2. Wasmedge has a performance error when handling a non-WASI wasm binary. Proposed solutions are not mentioned.
3. Abortion report on the instruction memory.grow. Reproduction steps provided, but no explicit solutions mentioned.
4. Crash report about the instruction table.init. Solution proposed is for an internal handler to catch the error.

5. Crash report about the instruction memory.init. Solution proposed is for an internal handler to

       this result is generated by flows.network. Triggered by @jaykchen