Classic298andGitHub dd514ee20b fix: persist upstream streaming error lines by awaiting the message upsert (#27365) ...

The branch that normalizes plain JSON error lines from streaming upstreams (lines without the SSE data: prefix) called Chats.upsert_message_to_chat_by_id_and_message_id without await. The coroutine was never executed, so the error was never written to the chat and Python emitted a "coroutine was never awaited" RuntimeWarning instead. The frontend still received the error event, but after a reload the message showed no trace of the failure.

The parallel error-persist branch further down the same handler already awaits the call; this aligns the two.

2026-07-23 17:49:18 -05:00

..

data

…

open_webui

fix: persist upstream streaming error lines by awaiting the message upsert (#27365)

2026-07-23 17:49:18 -05:00

.dockerignore

…

.gitignore

…

dev.sh

refac

2026-03-24 19:43:30 -05:00

requirements-min.txt

perf: 40% LESS CPU usage: cut per-instance CPU cost of shared socket.io Redis pub/sub channel (#27282)

2026-07-23 12:11:38 -04:00

requirements.txt

perf: 40% LESS CPU usage: cut per-instance CPU cost of shared socket.io Redis pub/sub channel (#27282)

2026-07-23 12:11:38 -04:00

start_windows.bat

refac

2026-06-17 03:01:11 +02:00

start.sh

refac

2026-06-17 03:01:11 +02:00