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
After making this change, running Streamlit returns an error, which makes it difficult to adjust num_concurrency values dynamically.
Thank you for your time and attention to this issue! 😊
Thank you:) !! ..
The text was updated successfully, but these errors were encountered:
jimin0
changed the title
reranking KeyError with quantization_type=none and --skip-reranking Option + num_concurrency Configuration Issue in Streamlit
Reranking KeyError with quantization_type=none and --skip-reranking Option + num_concurrency Configuration Issue in Streamlit
Nov 4, 2024
Thanks for @Sheharyar570 's professional, prompt, and enthusiastic assistance. The Reranking KeyError has been fixed in PR: #401 .
@jimin0v0.0.16 has been released, and you can update the code to the latest version for testing. If you have any questions, please feel free to reach out to us.
Hi....
Bug Description
There appears to be an issue where
reranking
configuration is required even when:quantization-type
is set to 'none'--skip-reranking
CLI option is usedThe code throws KeyError: 'reranking' regardless of these settings.
Error log
Steps to Reproduce
or
-> Both attempts result in the following error: KeyError: 'reranking'
Additional Question:
Could the
num_concurrency
configuration be reviewed as well? The current issues include:UI Control: Need Streamlit UI controls to adjust
num_concurrency
range.Configuration Error: An error occurs when attempting to modify
num_concurrency
inVectorDBBench/vectordb_bench/__init__.py
as follows:After making this change, running Streamlit returns an error, which makes it difficult to adjust
num_concurrency
values dynamically.Thank you for your time and attention to this issue! 😊
Thank you:) !! ..
The text was updated successfully, but these errors were encountered: