You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this is opened against wasm-tools. The original issue, against cargo-component, included the zip file to allow easy reproduction of the problem.
The importer.wasm file that is created seems to be the raw wasm file: importer.wasm.gz
And here is the command line that could reproduce the problem.
wasm-tools component new ~/Downloads/importer.wasm --adapt ./wasi_snapshot_preview1.reactor.wasm
The error message:
error: failed to encode a component from module
Caused by:
0: failed to validate component output
1: export name `[static]my-resource.get-static` is not valid
static resource name is not known in this context (at offset 0xb)
The text was updated successfully, but these errors were encountered:
alexcrichton
added a commit
to alexcrichton/wasm-tools
that referenced
this issue
May 3, 2024
Previously the resource itself wasn't imported which meant that the
`[static]` function did not pass validation. This commit updates the
liveness of these functions to include the resource that the static
function is attached to which ensures that the type is emitted during
component construction.
Closesbytecodealliance#1529
Previously the resource itself wasn't imported which meant that the
`[static]` function did not pass validation. This commit updates the
liveness of these functions to include the resource that the static
function is attached to which ensures that the type is emitted during
component construction.
Closes#1529
Per the Zulip discussion this afternoon,
this is opened against wasm-tools. The original issue, against
cargo-component
, included the zip file to allow easy reproduction of the problem.The importer.wasm file that is created seems to be the raw wasm file:
importer.wasm.gz
And here is the command line that could reproduce the problem.
The error message:
The text was updated successfully, but these errors were encountered: