You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
With a fresh environment on my computer, my flow raises an error with the tool promptflow_vectordb.tool.common_index_lookup.search.
The function _get_custom_dimensions inside promptflow_vectordb\tool\common_index_lookup.py cannot get a build_number because the environment variable BUILD_INFO is not set.
How To Reproduce the bug
Steps to reproduce the behavior, how frequent can you experience the bug:
Create a conda environment with python=3.11
Install the lastest version of promptflow (1.16.1), promptflow-tools (1.4.0) and promptflow-vectordb (0.2.13)
Create a flow using promptflow_vectordb.tool.common_index_lookup.search with a FAISS index from Azure ML (I didn't test with other options)
Run the flow
Expected behavior
The index lookup has to work without the BUILD_INFO. It has to have fallback build_number if the environment variable is not set.
Running Information(please complete the following information):
Describe the bug
With a fresh environment on my computer, my flow raises an error with the tool
promptflow_vectordb.tool.common_index_lookup.search
.The function
_get_custom_dimensions
insidepromptflow_vectordb\tool\common_index_lookup.py
cannot get abuild_number
because the environment variableBUILD_INFO
is not set.How To Reproduce the bug
Steps to reproduce the behavior, how frequent can you experience the bug:
promptflow_vectordb.tool.common_index_lookup.search
with a FAISS index from Azure ML (I didn't test with other options)Expected behavior
The index lookup has to work without the
BUILD_INFO
. It has to have fallbackbuild_number
if the environment variable is not set.Running Information(please complete the following information):
pf -v
:python --version
: python==3.11.10Additional context
There are discussions at #3632 with this error, but it was not the main topic and the issue is closed.
The text was updated successfully, but these errors were encountered: