FWIW find out which code load .env into os.environ

[mkhludnev]

I were troubleshoot some environment issues.
import

kotaemon/libs/kotaemon/kotaemon/storages/vectorstores/milvus.py

Line 4 in 069f0f3

from llama_index.vector_stores.milvus import MilvusVectorStore as LIMilvusVectorStore

causes a little bit invasive footprint on os.environ https://github.com/milvus-io/pymilvus/blob/87da0f100bf9078b4e5dcf8400eb79ed4956b88e/pymilvus/settings.py#L9
The possible drawback:

• kotaemon calls graphrag as subprocess. I'm not sure, but loaded .env might be propagated to graphrag. Not sure it might be a problem
• a user might rely on this behavior, but it might be broken if .env is renamed

Just FYI/

[taprosoft]

Noted. This is an issue with pymilvus implementation and we will check if it affects GraphRAG env settings.