Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Instantiate wasm in pre-checking #7218

@eskimor

Description

@eskimor

We will be able to catch more issues if we instantiated the wasm after compiling it, so we should do that in pre-checking.

Concrete recent example:

Successfully fetched PoV for 0xf6a6ba49fc14432eedbd8b7c43bf38cb21b67d4d7748ca809d162ec4e3b30c5f, para_id=2123
Using cached Pvf 0x9bb8ab583eaf6a4caa1b0c57c123a697b0dfe7a5935ffff7726b9f359ccc59ad
PoV size: 13kb
Pvf prechecking...
Pvf preparation took 4479ms
Pvf execution...
Error: InvalidCandidate(WorkerReportedError("execute: execute error: RuntimeConstruction(Other(\"failed to instantiate a new WASM module instance: Insufficient resources: memory minimum size of 2090 pages exceeds memory limits\"))"))

Metadata

Metadata

Assignees

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