-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't write .lock file when loading from an existing collection #765
Comments
Hi @jonas-nothnagel, sorry for the late response I am not an expert of gradio, but if it works in a similar way to streamlit, then you would either have a shared object, which is created only once or you can use If the former approach is possible, I think it would be preferable |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have stored a
qdrant
collection locally on my computer to access it for testing purposes. I am building a chatbot app in gradio and it requires to load theapp.py
many times to develop it in iterations.However, every time I load the collection a
.lock
file is automatically created which I have to manually delete each time when loading app again for my application. Otherwise I run into following error:RuntimeError: Storage folder qdrant/ is already accessed by another instance of Qdrant client. If you require concurrent access, use Qdrant server instead.
The code to load the collection is as follows:
I would like to either automatically delete the
.lock
file or to not create it at all in the first place. Is this possible within Qdrant or do I have to build a manual work around?I know I could simply add something like a
os.remove("qdrant/.lock")
but it seems not very intuitive.The text was updated successfully, but these errors were encountered: