Component instance limit blocks an extension-heavy Python component

[noobHappylife]

I’m building a Python component with Eryx 0.7.2 using this site-packages layer, which contains 246 native extensions. With wasmparser 0.259, component encoding fails:

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.

[alexcrichton]

For this the initial set of limits in limits.rs are intended to be somewhat conservative so we could get experience with them over time, but for other limits we've just increased the limits once they've gotten hit. In that sense I think the best change here would be to just update the limit -- would you be up for sending a PR for that?

[noobHappylife]

Hi @alexcrichton , thanks for replying. I've opened a PR#2661 on this.