Find answers from the community

Updated 4 months ago

Ci testing pipelines failing due to import error

At a glance

The community members are experiencing an issue with their CI testing pipelines using Llama index, where they are encountering an ImportError while importing the test module. The error is related to the inability to import the 'Base' class from the 'llama_cloud.types.base' module. The community members have provided the specific versions of the llama-index libraries they are using, which are the latest versions. However, they are still unsure why the 'llama_cloud' library is being imported, as it is not mentioned in the provided library versions. The issue was eventually resolved, but the community members are concerned about the potential impact on live applications that may have been installing the 'llama-cloud' library during the time the issue was present.

Our CI testing pipelines using Llama index are suddenly failing:

Plain Text
ImportError while importing test module '/home/runner/work/xxx/test_prompts.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/opt/hostedtoolcache/Python/3.12.4/x64/lib/python3.12/importlib/__init__.py:90: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
test_prompts.py:10: in <module>
    from index import add_documents_to_index
../../index.py:22: in <module>
    from llama_cloud import FilterCondition
/opt/hostedtoolcache/Python/3.12.4/x64/lib/python3.12/site-packages/llama_cloud/__init__.py:3: in <module>
    from .types import (
/opt/hostedtoolcache/Python/3.12.4/x64/lib/python3.12/site-packages/llama_cloud/types/__init__.py:21: in <module>
    from .base import Base
E   ImportError: cannot import name 'Base' from 'llama_cloud.types.base' 


Anyone has an idea why?
W
N
L
12 comments
Are you using fixed version for some llama-index libraries?
llama-index==0.11.17
llama-index-embeddings-openai==0.2.5
llama-index-embeddings-azure-openai==0.2.5
llama-index-llms-openai==0.2.13
llama-index-program-openai==0.2.0
llama-index-vector-stores-postgres==0.2.6
llama-index-llms-azure-openai==0.2.2
Should all be on the latest versions to be honest
Yeah i think there could be some conflict with older versions
Sorry, I meant these are already the latest versions
It is throwing error for llamacloud, And as per your libraries mentioned llamacloud is not there. I wonder how it is being roped in
Thats also a mystery to me
Tests are passing again tho..
Yea somehow a version of llama-cloud client got published with a missing file. Was quickly fixed
πŸ‘πŸ»
Was there any chance this was also impacting live applications?
If an application
  • was installing llama-cloud during the 30 mins the package was published
  • was installing llama-cloud with dependenices that were pinned in a way to allow a new version to install
Add a reply
Sign up and join the conversation on Discord