Originally created by @oe3gwu on GitHub (Sep 27, 2024).
Is your feature request related to a problem? Please describe.
open-webui with vLLM backend raises issues because vLLM doesnt support memories yet.
INFO: 172.21.196.115:0 - "POST /api/v1/memories/query HTTP/1.1" 500 Internal Server Error
This ends in a bailout of the UI and it doesnt generate an answer. I can disable it per user but not central in the admin settings
Describe the solution you'd like
I would like to have an environment parameter I can addres in a docker-compose to disable the memories function and also maybe in the UI Admin panel to centralize this option. Not a per user basis!
Describe alternatives you've considered
There are none because I have no influence to the vLLM project.
Additional context
Currently I have no screenshots, because I disabled it for me. It is a production system in our company. If you really need one, please tell me and I create Demo user where I can recreate this.
Originally created by @oe3gwu on GitHub (Sep 27, 2024).
**Is your feature request related to a problem? Please describe.**
open-webui with vLLM backend raises issues because vLLM doesnt support memories yet.
INFO: 172.21.196.115:0 - "POST /api/v1/memories/query HTTP/1.1" 500 Internal Server Error
This ends in a bailout of the UI and it doesnt generate an answer. I can disable it per user but not central in the admin settings
**Describe the solution you'd like**
I would like to have an environment parameter I can addres in a docker-compose to disable the memories function and also maybe in the UI Admin panel to centralize this option. Not a per user basis!
**Describe alternatives you've considered**
There are none because I have no influence to the vLLM project.
**Additional context**
Currently I have no screenshots, because I disabled it for me. It is a production system in our company. If you really need one, please tell me and I create Demo user where I can recreate this.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @oe3gwu on GitHub (Sep 27, 2024).
Is your feature request related to a problem? Please describe.
open-webui with vLLM backend raises issues because vLLM doesnt support memories yet.
INFO: 172.21.196.115:0 - "POST /api/v1/memories/query HTTP/1.1" 500 Internal Server Error
This ends in a bailout of the UI and it doesnt generate an answer. I can disable it per user but not central in the admin settings
Describe the solution you'd like
I would like to have an environment parameter I can addres in a docker-compose to disable the memories function and also maybe in the UI Admin panel to centralize this option. Not a per user basis!
Describe alternatives you've considered
There are none because I have no influence to the vLLM project.
Additional context
Currently I have no screenshots, because I disabled it for me. It is a production system in our company. If you really need one, please tell me and I create Demo user where I can recreate this.