github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 02:48:13 -05:00
Code Issues 1.1k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #24245] Dashboard shows stale data after lab report upload #58908

New Issue
Closed
opened 2026-05-06 00:25:29 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-06 00:25:29 -05:00
Owner
Copy Link

Originally created by @har33sh on GitHub (Apr 29, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24245

Problem

After a Patient uploads a Health Document, the Processing Agent runs synchronously (awaited inline), but the Wiki Agent and UI Agent run asynchronously via asyncio.ensure_future. If the Patient opens the dashboard immediately after upload, they see stale data (or nothing on first upload).

Code reference: web-ui/backend/open_webui/routers/wiki_lab_reports.py lines ~270-300

Options

  1. Make the whole chain synchronous (slower upload response, dashboard always fresh)
  2. Keep async but add a trackable Processing Status the frontend can poll

Context

Found during grill session on CONTEXT.md — the example dialogue implies a fully sequential flow, which doesn't match the actual implementation.

Originally created by @har33sh on GitHub (Apr 29, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/24245 ## Problem After a Patient uploads a Health Document, the Processing Agent runs synchronously (awaited inline), but the Wiki Agent and UI Agent run asynchronously via `asyncio.ensure_future`. If the Patient opens the dashboard immediately after upload, they see stale data (or nothing on first upload). **Code reference**: `web-ui/backend/open_webui/routers/wiki_lab_reports.py` lines ~270-300 ## Options 1. Make the whole chain synchronous (slower upload response, dashboard always fresh) 2. Keep async but add a trackable **Processing Status** the frontend can poll ## Context Found during grill session on CONTEXT.md — the example dialogue implies a fully sequential flow, which doesn't match the actual implementation.
GiteaMirror commented 2026-05-06 00:25:33 -05:00
Author
Owner
Copy Link

@pr-validator-bot commented on GitHub (Apr 29, 2026):

⚠️ Missing Issue Title Prefix

@har33sh, your issue title is missing a prefix (e.g., bug:, feat:, docs:).

Please update your issue title to include one of the following prefixes:

  • bug: Bug report or error you've encountered
  • feat: Feature request or enhancement suggestion
  • docs: Documentation issue or improvement request
  • question: Question about usage or functionality
  • help: Request for help or support

Example: bug: Login fails when using special characters in password

<!-- gh-comment-id:4346192370 --> @pr-validator-bot commented on GitHub (Apr 29, 2026): # ⚠️ Missing Issue Title Prefix @har33sh, your issue title is missing a prefix (e.g., `bug:`, `feat:`, `docs:`). Please update your issue title to include one of the following prefixes: - **bug**: Bug report or error you've encountered - **feat**: Feature request or enhancement suggestion - **docs**: Documentation issue or improvement request - **question**: Question about usage or functionality - **help**: Request for help or support Example: `bug: Login fails when using special characters in password`
GiteaMirror commented 2026-05-06 00:25:37 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Apr 29, 2026):

????????????????????????????????????????????????????

<!-- gh-comment-id:4346375861 --> @Classic298 commented on GitHub (Apr 29, 2026): ????????????????????????????????????????????????????
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#58908
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?