mirror of
https://github.com/open-webui/open-webui.git
synced 2026-09-16 23:43:03 +00:00
0313ea0238
Pressing Stop on a chat that has more than one running task (a multi-model response, or a follow-up sent from another tab or device while a response is still streaming) reported success but only cancelled the first task. The survivors kept streaming and kept executing tool calls until the iteration limit, which is the runaway reported in the issue. Without Redis the stop loop iterates the live task-id list of the chat. Each awaited cancellation runs that task's cleanup, which removes its id from the same list mid-iteration, so the loop runs out one element early and the last task is never cancelled. Returning a snapshot of the list to callers keeps the loop on the ids it started with. Redis deployments already got a fresh list from the set and were not affected. Verified against a mock upstream that calls a tool on every turn: with three tasks on one chat, stop left one or two alive before the change and cancels all of them after it. Fixes #29816 |
||
|---|---|---|
| .. | ||
| data | ||
| open_webui | ||
| .dockerignore | ||
| .gitignore | ||
| dev.sh | ||
| requirements-slim.txt | ||
| requirements.txt | ||
| start.sh | ||
| start_windows.bat | ||