Pavel Agafonov

Hi. I have made a PR https://github.com/pgcentralfoundation/pgrx/pull/2078 to solve this problem, maybe it will be accepted or another suitable solution will be found.

> I have same problem. In windows 11 enviroment. How can I solve this? I'll make PR. For now, you can check the `Beta: Use Unicode UTF-8 for worldwide language...

`from_utf8_lossy` will help avoid crashes from panic. The fact that `REPLACEMENT_CHARACTER`s will be displayed is a different problem imo. I could solve the encoding issue with a third-party crate, but...

Ok, I'll fix the Windows encoding problem then.

@ricochet Could you restart pipelines? Fix is out: https://blog.rust-lang.org/2025/11/10/Rust-1.91.1/#linker-and-runtime-errors-on-wasm

There is no mention of provider wadm here https://github.com/wasmCloud/wasmCloud/blob/7fe7b231a9abc9b97c7b5bfe468a2175f022c5be/.github/workflows/wasmcloud.yml#L258-L277

> If you wanted to test with this, you should be able to build this provider with `wash build -p ./src/bin/wadm-provider`. [@LUK3ARK](https://github.com/LUK3ARK) might have some tips if he's actually running...

> What container registry are you using? If Artifactory, what version? I use registry:2.8 in docker

``` wash inspect target/wasm32-wasip2/debug/graph_executor.wasm 2025-09-02T07:33:36.816352Z INFO loading component from file component_reference="target/wasm32-wasip2/debug/graph_executor.wasm" Failed to decode component ``` ``` wasm-tools -V wasm-tools 1.238.0 wasm-tools validate target/wasm32-wasip2/debug/graph_executor.wasm --features cm-async error: invalid leading byte...

I tested the component call without binding to the provider's span. Old behaviour: New behaviour: