Skip to content

wasm-compose creating an ill formed wasm component #986

@rylev

Description

@rylev

I'm still seeing issues after #977 has been fixed. This is what I'm seeing:

$ wasm-tools component wit broken-composed.wasm

Error: failed to decode WIT document

Caused by:
    0: failed to decode WIT from export `inbound-http`
    1: failed to register type export 'request'
    2: failed to convert unaliased type
    3: failed to convert record field 'method'
    4: unexpected unnamed type of kind 'enum'

Perhaps the issue comes from the following subcomponent in the composed component:

 (component (;0;)
      (alias outer 1 22 (type (;0;)))
      (import "import-handle-request" (func (;0;) (type 0)))
      (alias outer 1 23 (type (;1;)))
      (export (;2;) "request" (type 1))
      (alias outer 1 24 (type (;3;)))
      (export (;4;) "response" (type 3))
      (type (;5;) (func (param "req" 2) (result 4)))
      (export (;1;) "handle-request" (func 0) (func (type 5)))
    )

You'll notice that that request is being exported based on an outer alias. Could it be that this brings request into scope but the types that request relies on like method are still not in scope? Still trying to wrap my head around outer aliases so I might be getting lost here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions