Tomáš Olvecký

Thanks for response. > What if your code always panics while handling the message? Broker has to hold the message forever because the user code is wrong? There is already...

Thank you for your response. We can probably agree that the spec leaves some room for interpretation, ultimately it is the application's responsibility to decide what's the correct behavior for...

Thanks for the quick response. I am not familiar with the issue you are mentioning, can you please provide a pointer? Is it only related to async execution?

I'm also wondering what's the difference between `package.metadata.component.dependencies` and ~~package.metadata.component.dependencies~~ `package.metadata.component.target.dependencies`. The former is modified using `cargo component add`, but unless I add the dependency to the latter I get...

@peterhuene Sorry for the confusion, yeah that's what I meant (I've edited the comment). Thanks for the explanation, the difference is now clear.

Hi, I've taken a stab at the issue. The fix only works for manifests with single binaries. Note that the above mentioned `git-mob-tool` switched to using `package.metadata.binstall` recently, so to...

I wasn’t sure either, but started exploring it and ended up completing it. No pressure, totally understand if it’s not the right fit.I'll add tests running on `wasmtime`.

The tests fit nicely, essentially I just replaced an annotation. The whole change that enables `wasip2` is in `call` and it uses most of other modules like `response_body`, `body_stream` etc....

gRPC proper isn't currently supported in WASI, see [this issue](https://github.com/WebAssembly/wasi-http/issues/128) for context. While it's technically possible to send gRPC messages over HTTP/1, that requires non-standard server configs. Even once full...

I also don't understand how to build the CLI with the exact same dependencies without a lockfile.