LlamaIndex
Log in

Find answers from the community

Updated 2 years ago

The error that I encountered was

NNoble
·
The error that I encountered was -
Plain Text
FAILED tests/indices/test_utils.py::test_expand_tokens_with_subtokens - LookupError:
FAILED tests/indices/keyword_table/test_utils.py::test_expand_tokens_with_subtokens - LookupError:
FAILED tests/indices/query/test_compose.py::test_recursive_query_table_list - LookupError:
FAILED tests/indices/query/test_compose.py::test_recursive_query_list_table - LookupError:
FAILED tests/indices/query/test_compose_vector.py::test_recursive_query_vector_table - LookupError:
FAILED tests/indices/query/test_compose_vector.py::test_recursive_query_vector_table_query_configs - LookupError:
FAILED tests/indices/query/test_compose_vector.py::test_recursive_query_vector_table_async - LookupError:
ERROR tests/llm_predictor/vellum/test_predictor.py::test_predict__basic - ModuleNotFoundError: No module named 'vellum'
ERROR tests/llm_predictor/vellum/test_predictor.py::test_predict__callback_manager - ModuleNotFoundError: No module named 'vellum'
ERROR tests/llm_predictor/vellum/test_predictor.py::test_stream__basic - ModuleNotFoundError: No module named 'vellum'
ERROR tests/llm_predictor/vellum/test_predictor.py::test_stream__callback_manager - ModuleNotFoundError: No module named 'vellum'
ERROR tests/llm_predictor/vellum/test_prompt_registry.py::test_from_prompt__new - ModuleNotFoundError: No module named 'vellum'
ERROR tests/llm_predictor/vellum/test_prompt_registry.py::test_from_prompt__existing - ModuleNotFoundError: No module named 'vellum'
ERROR tests/llm_predictor/vellum/test_prompt_registry.py::test_get_compiled_prompt__basic - ModuleNotFoundError: No module named 'vellum'
L
N
4 comments
LLogan M
I've never had the LookupErrors locally, but the vellum errors are normal (because you don't have vellum installed, it's not a core dependency since it's for a specific integration)
LLogan M
But yea, it passes on CI so all is well 🙂
NNoble
Is it not expected to be installed as part of the requirement installation or is that something that got missed out on the requirements file ?
I also realised that certain dependencies were not captured on the requirements file. I started with a new virtualenv and I could see missing dependencies. If this is a bug, then Iam interested in resolving this issue 🙂
NNoble
Okay understood, since this isn't a core dependency it was not included in the requirements.txt. Got it.
Add a reply
Sign up and join the conversation on Discord