One other issue I'm noticing after

At a glance

One other issue I'm noticing after migration to 0.10.X is that I get this error asyncio.run() cannot be called from a running event loop in my API call. This wasna't the case during 0.9.X. I wasn't using nestio previously too.

8 comments

LLogan M

Something must be nested async in the features you are using 🤷‍♂️ Just add

Plain Text

import nest_asyncio
nest_asyncio.apply()

cchantlong

I didn't need to use nest_asyncio previously in 0.9.X
Is this something I apply in the API?

cchantlong

I'm using Django btw.

cchantlong

after some more digging without using nest_asyncio.apply()
interestingly, I noticed this error pops up only if I kept use_async True in the from_vector_store method

Plain Text

vector_store = QdrantVectorStore(
                aclient=aclient,
                collection_name=QDRANT_CLOUD_COLLECTION_NAME
            )
base_index = VectorStoreIndex.from_vector_store(
                vector_store=vector_store,
                embed_model=embeddings,
                callback_manager=callback_manager,
                use_async=True
            )

if I remove it it works.
I'm already using use_async=True in query engines and stuff but those don't raise error. This only happens on 0.10.X
is there any idea as to why that is the case?

LLogan M

Yes -- that will cause the embeddings to be calculated with multiple async requests. Maybe this feature wasn't working properly in a past version and is now fixed

LLogan M

yea nest_asyncio.apply() is just something I would throw into the top of my file

cchantlong

i see. Yeah I tried doing nest_asyncio.apply() in my django request but it ended up giving the error that it cannot patch a uvloop :/

LLogan M

I know fastapi let's you set the loop type to asyncio. Not sure if Django has a similar option

Add a reply

Find answers from the community

One other issue I'm noticing after