Daniel Vigovszky
Daniel Vigovszky
Closing as we are going to delete the Rib based API gateway
Not working with cargo-component 0.7.0, recheck after update: ```toml [package.metadata.component.registries] wasi = "https://wasi.wa.dev" [package.metadata.component.target] path = "wit" [package.metadata.component.target.dependencies] "wasi:sockets" = { version = "0.2.0", registry = "wasi" } "wasi:io" =...
With the app manifest based compilation this does not matter anymore - even if we could fetch the WITs using cargo-component's dependency support it is not enough because we need...
There is proper feedback now in the CLI output about updates, and it is even possible to await until it's done.
To be revisited after the wRPC migration and the other benchmark investigations
This is no longer the case, see: ``` [2025-10-31T10:24:56.340Z] [INVOKE ] STARTED chatroom:room-exports/chatroom-room-api.{join} (7b26aee2-0f90-4aea-aa5f-99a1b8aef145) [2025-10-31T10:24:56.340Z] [INVOKE ] FINISHED chatroom:room-exports/chatroom-room-api.{join} (7b26aee2-0f90-4aea-aa5f-99a1b8aef145) [2025-10-31T10:25:01.749Z] [INVOKE ] STARTED chatroom:room-exports/chatroom-room-api.{send} (c4228a9d-9363-4626-821a-43cb1c0e8127) [2025-10-31T10:25:01.756Z] [STDOUT ] Fowarding...
Tested with golem 1.3 (https://github.com/mschuwalow/golem-hackathon-17.03.25/pull/6)
Fixed upstream: https://github.com/bytecodealliance/ComponentizeJS/issues/126
I think this is fixed by https://github.com/golemcloud/jco/pull/9
This is probably only possible if `TypeAnnotatedValue` in `wasm-rpc` is converted back to a non-protobuf generated type.