Lann

Ah, you are correct. That explains why I couldn't figure out where this would be happening...

As a workaround you could point two components at the same wasm module and give them different `environment` or `config` values to differentiate between them. Edit: Though if you're trying...

I think ignoring the warning is appropriate. I have updated this issue's title to be slightly more discoverable if someone else is annoyed by the warning.

> the critical question of how to manage the Spin world versioning Notably, this is basically the entire focus of WASI 0.2.1 and afaik we still haven't even completely figured...

You should be able to plug it into a microphone port and run the script. That said, I haven't looked at this in over 5 years and don't remember exactly...

If you are using OSX or Linux, python should already be installed, in which case you can run: `python main.py` If you are using Windows then you would need to...

(As discovered by @calebschoepp) Disabling metrics fixes this. Seems probable that this is an upstream `tracing-opentelemetry` or `opentelemetry` bug.

Sorry, missed your previous update. > Is there some sort of queuing of requests because this does not seem to me a Wasm issue. Yes, there is implicit queuing of...

Only via the generic `Prefix` method, e.g. `.Select("*").Prefix("WITH ...")` -> `WITH ... SELECT *`

Probably not. From the readme: > Squirrel is "complete". > > Bug fixes will still be merged (slowly). Bug reports are welcome, but I will not necessarily > respond to...