[BUG] Chat gets re-downloaded every 2 seconds while a response is streaming
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 60/100
Research direction
Start with streaming_helper.dart, especially scheduleTerminalCompletionRecovery, and trace when its timer is armed and re-armed relative to socket events. Check the existing streaming and recovery tests before changing behavior. Done means a healthy socket delivering events does not trigger repeated full-chat fetches, while recovery still works when the socket goes quiet or reconnects.
Written by the indexing model from the issue text.
Description
App Version
4.3.1
Platform
- Android
- iOS
How you installed it
GitHub Releases
What happened?
While a response is streaming, Conduit calls GET /api/v1/chats/{id} about every 2 seconds until the message is done, even when the socket is healthy.
On an 11-minute tool loop in a 2–3 MB chat that was 162 full-chat downloads, about 347 MB. On cellular that's a lot of data and battery for content the socket already delivers.
It looks like scheduleTerminalCompletionRecovery in streaming_helper.dart starts right after the /api/chat/completions POST returns and re-arms its 2 s timer until the message is done.
What should have happened?
No full-chat fetches while the socket is delivering events. Maybe poll only when the socket goes quiet or after a reconnect, and pause in the background.
How to reproduce
- Watch the Open WebUI access log (mine is 0.13.3).
- Send a message that takes a while to answer.
- See
GET /api/v1/chats/{id}about every 2 seconds until it finishes.
Does this happen every time?
Yes, every time
When did this start?
Not sure, noticed it today.
Screenshots
No response
Logs
No response
- Dominant language
- Dart
- Stars
- 2.4k
- Forks
- 280
- Avg merge
- 23h 57m
- Merged PRs (30d)
- 191
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cogwheel0/conduit
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cogwheel0/conduit#1122 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cogwheel0/conduit#1121 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cogwheel0/conduit#1070 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
cogwheel0/conduit#535 · 4 reactions ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 58/100
cogwheel0/conduit#1109 · 1 comment ·
Maintainers usually reply within 1 day
All issues in cogwheel0/conduit
Similar issues
-
bug enhancement needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
bug from-telegram platform:windows
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hiddify/hiddify-app#2592 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bannzai/shoppinglist#779 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day