type mismatch for import `wasi:http/types@0.2.0`

[vdice]

With the latest/canary version of this plugin and the latest Spin release as of writing (3.2.0), I am seeing the following when I run spin test:

error: failed to compose Spin app, test, and virtualized Spin environment

Caused by:
   0: failed to encode composition
   1: encoding produced a component that failed validation
   2: type mismatch for import `wasi:http/types@0.2.0`
type mismatch in instance export `input-stream`
resource types are not the same (ResourceId { globally_unique_id: 4, contextually_unique_id: 165 } vs. ResourceId { globally_unique_id: 4, contextually_unique_id: 20 }) (at offset 0x6a9698)
make: *** [spin-test] Error 1

Full repro/details: spinframework/spin-fileserver#63

[petersalomonsen]

I also experience this.

[rylev]

Sorry for taking so long to take a look at this. The fix for this is to update the wit definitions. I've been first looking into updating all the dependencies for this project since it's been a while since we've done that. That process is taking longer than I had hoped, but I should hopefully be done soon. Once that's done, I'll update the wit definitions.

[lann]

I think the implementation of WebAssembly/component-model#536 will help here.

[github-matthieu-wipliez]

Hi @rylev is there any news on this topic?