Open Falumpaset opened 1 year ago
This sounds like the same issue I ran into here: https://bytecodealliance.zulipchat.com/#narrow/stream/407292-cargo-component/topic/Component.20composition.20confusion/near/396244085
Thanks for sharing that! I will try and go back to pre resource WITs then.
If I understand correctly (big if 😛) then this may be a manifestation of https://github.com/bytecodealliance/wasm-tools/issues/1253, which would be resolved once https://github.com/bytecodealliance/wasm-tools/pull/1252 (impl of https://github.com/WebAssembly/component-model/pull/248) lands.
Someone with a better understanding and more sleep please feel free to correct me!
Hello!
I'd be thrilled if you could help me resolve my issue with
wasm compose
.I want to build an application that is composed of two components. Both components are made with cargo component, and I use the wit deps out of the wasmtime 14 branch.
The application has one
application
component, the root component. This component imports thebackend
components interface.When composing with
I encountered this error:
My config:
I understand that both components import the wasi:io/streams interface. However, they seem to be conflicting.
I´ve looked into the composing logic, and the error seems to originate from the process of merging the two wasi:io interfaces. Hence, I´ve looked into the translated components and compared the two wasi:io/stream imports. It occurs to me that one instance is entirely different from the other.
Within the backend component, I notice that the wasi:io interface also exports elements from the wasi:http world. Is this intended?
If not, how can I resolve this issue?
The backend component
Its world after building:
The application component
The world:
The WAT:
I hope this finds you well, and thanks in advance!