I have read and followed all the instructions provided in the README.md.
I am on the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
Expected Behavior:
Clicking it will output the Merged Response correctly.
Actual Behavior:
After clicking, the web page is stuck
Description
Bug Summary:
Merged Response is not available in v0.5.3.
Additional Information
It's worth mentioning that after clicking, my backend feedback shows that the task model has actually completed the input and output, but the web frontend indeed has no response. Even after refreshing, the loading component remains the same. Perhaps this is a bug introduced by the async response feature?
Thanks in advance. BTW, it would be even better if the merge operation, like title generation, could also expose a prompt for the user to modify
Originally created by @GrayXu on GitHub (Jan 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8263
# Bug Report
## Important Notes
## Installation Method
docker
## Environment
- **Open WebUI Version:** v0.5.3
- **Operating System:** Windows 11
- **Browser (if applicable)**: Chrome
**Confirmation:**
- [x] I have read and followed all the instructions provided in the README.md.
- [x] I am on the latest version of both Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
## Expected Behavior:
Clicking it will output the Merged Response correctly.
## Actual Behavior:
After clicking, the web page is stuck
## Description
**Bug Summary:**
Merged Response is not available in v0.5.3.
## Additional Information
It's worth mentioning that after clicking, my backend feedback shows that the task model has actually completed the input and output, but the web frontend indeed has no response. Even after refreshing, the loading component remains the same. Perhaps this is a bug introduced by the async response feature?
Thanks in advance. BTW, it would be even better if the merge operation, like title generation, could also expose a prompt for the user to modify
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 @GrayXu on GitHub (Jan 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8263
Bug Report
Important Notes
Installation Method
docker
Environment
Open WebUI Version: v0.5.3
Operating System: Windows 11
Browser (if applicable): Chrome
Confirmation:
Expected Behavior:
Clicking it will output the Merged Response correctly.
Actual Behavior:
After clicking, the web page is stuck
Description
Bug Summary:
Merged Response is not available in v0.5.3.
Additional Information
It's worth mentioning that after clicking, my backend feedback shows that the task model has actually completed the input and output, but the web frontend indeed has no response. Even after refreshing, the loading component remains the same. Perhaps this is a bug introduced by the async response feature?
Thanks in advance. BTW, it would be even better if the merge operation, like title generation, could also expose a prompt for the user to modify
@gabriel-ecegi commented on GitHub (Jan 2, 2025):
generate_moa_response is sending "chat_id" in payload.
causing error
{
"error": {
"message": "Unrecognized request argument supplied: chat_id",
"type": "invalid_request_error",
"param": null,
"code": null
}
openai generate_chat_completion should delete it, if so
@tjbck commented on GitHub (Jan 2, 2025):
Good catch, Fixed on dev!