Munjal A Patel

> run into the same error `def` -> memory leak `async def` -> no memory leak thanks @curtiscook @delijati @curtiscook is the fix literally changing `def fn_name` to `async def...

Thanks @delijati I'll do some experiments with this as well. We are using `amd64/pypy:3.7` if that matters. This is a serious issue for us where every `FastAPI` based pods eventually...

Just verified that for us moving functions to `async` still doesn't app. For example, this pod has almost all methods as `async` and we still see memory creeping. 

Any plans to enhance this feature to properly understand instance type?

I am also having the same exact issue. Just can't get it to work after spending days debugging it. Both client and server are on `v1.7.0` @telemac were you able...

@telemac Well, for me, the `client` is `nil` even after sleep. Both `err` and `client` are `nil`.

I am also running into the same issue. Any updates here?

Yeah, I think two things are missing: 1. Error / Exception Management 2. Authentication / Metadata support

@apepkuss @hydai we are also looking for this as discussed here: https://github.com/tessi/wasmex/issues/358

I am having the same issue. I am using `nutx3` with `pnpm` if that matters.