Daniel Vigovszky
Daniel Vigovszky
It is also possible that all the dependency constraints are defined so that it works with our versions and then this is a no-op.
A new wrpc version has been released, depending on wasmtime v33.0, so this ticket is going to be about updating Golem to wasmtime v33 instead of updating wrpc.
Note also that some auto-generated environment variables may already change during the lifetime of a worker (at least the component version). And during replay, this needs to be handled properly.
Now that we have per-component environment variables that can be applied to workers by updating them, I think it makes sense to support changing the per-worker environment variables too at...
@mschuwalow you've done this right?
I said multiple times that I verified this and it works as it has to.
I'm going to review this fully a bit later
Related: https://github.com/WebAssembly/component-model/blob/main/design/mvp/WIT.md#binary-format - tooling encodes WIT as a component-model WASM and puts the whole thing in a custom section of the real component model WASM - we can somehow map...
We now have the whole WIT interface stored in the component metadata
See https://github.com/golemcloud/golem-cloud/issues/1027 for previous discussion