bytecodealliance / bytecodealliance/wasm-tools

Component instance limit blocks an extension-heavy Python component

Open
#2,656 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
1.8k
Forks
351
Avg merge
16h 57m
Merged PRs (30d)
38

Description

I’m building a Python component with Eryx 0.7.2 using [this site-packages layer](https://github.com/EmbeddedLLM/wasi-python-layer/releases/download/v1.0.0/python-site-packages-cp314-wasm32-wasip2.tar.gz), which contains 246 native extensions. With wasmparser 0.259, component encoding fails:
```text
failed to validate component output:
instances count exceeds limit of 1000
```

Our older downstream build worked around this by raising `MAX_WASM_INSTANCES` to 4096, but I’d prefer not to carry a patched wasmparser.

Is there a supported way to opt into a higher limit? If not, would you prefer a higher fixed limit or a configurable one? I can help test against this layer.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.