github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 19:08:59 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[PR #20927] [CLOSED] Estável-- #25836

New Issue
Closed
opened 2026-04-20 06:08:53 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 06:08:53 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/20927
Author: @ulrichtesteapi5-wq
Created: 1/25/2026
Status: ❌ Closed

Base: main ← Head: Estável--

📝 Commits (7)

  • 74ae895 chore: add latency logging to middleware for diagnosis
  • a4380c3 feat: implement data integrity lock for chat histories
  • 19e0c15 feat(orchestration): Polish MoA UX and error handling
  • 62147fc feat(orchestration): harden server-side orchestration with distributed locks, latency tracking, and improved resilience
  • a80825d feat: improve resilience for slow models (increased timeouts, enabled server-side orchestration, and added request retry logic)
  • 7b852d3 Refactor: Disable Server-Side Orchestration and implement Smart Retry logic to fix 'Request Error' and prevent session leaks.
  • 9014ebc Refactor: Broaden retry logic to include all errors (including 400-level) as requested.

📊 Changes

20 files changed (+1142 additions, -308 deletions)

View changed files

➕ EXECUTION_PLAN_SERVER_SIDE_ORCHESTRATION.md (+51 -0)
➕ analyze_json.py (+44 -0)
📝 backend/open_webui/config.py (+6 -0)
📝 backend/open_webui/constants.py (+2 -0)
📝 backend/open_webui/env.py (+6 -2)
📝 backend/open_webui/main.py (+7 -90)
📝 backend/open_webui/models/chats.py (+140 -32)
📝 backend/open_webui/routers/chats.py (+7 -1)
📝 backend/open_webui/routers/ollama.py (+88 -59)
📝 backend/open_webui/routers/openai.py (+66 -41)
📝 backend/open_webui/socket/main.py (+15 -0)
📝 backend/open_webui/utils/chat.py (+313 -4)
📝 backend/open_webui/utils/middleware.py (+72 -0)
📝 backend/open_webui/utils/misc.py (+15 -2)
➕ backend/tests/check_import.py (+13 -0)
➕ backend/tests/test_integrity_lock.py (+127 -0)
➕ convert_chat.py (+50 -0)
📝 src/lib/apis/index.ts (+12 -16)
📝 src/lib/components/chat/Chat.svelte (+93 -54)
📝 src/lib/components/chat/Messages.svelte (+15 -7)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.

This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.

Before submitting, make sure you've checked the following:

  • Target branch: Verify that the pull request targets the dev branch. Not targeting the dev branch will lead to immediate closure of the PR.
  • Description: Provide a concise description of the changes made in this pull request down below.
  • Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
  • Documentation: If necessary, update relevant documentation Open WebUI Docs like environment variables, the tutorials, or other documentation sources.
  • Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
  • Testing: Perform manual tests to verify the implemented fix/feature works as intended AND does not break any other functionality. Take this as an opportunity to make screenshots of the feature/fix and include it in the PR description.
  • Agentic AI Code: Confirm this Pull Request is not written by any AI Agent or has at least gone through additional human review AND manual testing. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR.
  • Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
  • Title Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
    • BREAKING CHANGE: Significant changes that may affect compatibility
    • build: Changes that affect the build system or external dependencies
    • ci: Changes to our continuous integration processes or workflows
    • chore: Refactor, cleanup, or other non-functional code changes
    • docs: Documentation update or addition
    • feat: Introduces a new feature or enhancement to the codebase
    • fix: Bug fix or error correction
    • i18n: Internationalization or localization changes
    • perf: Performance improvement
    • refactor: Code restructuring for better maintainability, readability, or scalability
    • style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
    • test: Adding missing tests or correcting existing tests
    • WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

  • [Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)]

Added

  • [List any new features, functionalities, or additions]

Changed

  • [List any changes, updates, refactorings, or optimizations]

Deprecated

  • [List any deprecated functionality or features that have been removed]

Removed

  • [List any removed features, files, or functionalities]

Fixed

  • [List any fixes, corrections, or bug fixes]

Security

  • [List any new or updated security-related changes, including vulnerability fixes]

Breaking Changes

  • BREAKING CHANGE: [List any breaking changes affecting compatibility or functionality]

Additional Information

  • [Insert any additional context, notes, or explanations for the changes]
    • [Reference any related issues, commits, or other relevant information]

Screenshots or Videos

  • [Attach any relevant screenshots or videos demonstrating the changes]

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

Note

Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/20927 **Author:** [@ulrichtesteapi5-wq](https://github.com/ulrichtesteapi5-wq) **Created:** 1/25/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `Estável--` --- ### 📝 Commits (7) - [`74ae895`](https://github.com/open-webui/open-webui/commit/74ae89597ad39f7d0a4b1ecb92a722221ddf6c28) chore: add latency logging to middleware for diagnosis - [`a4380c3`](https://github.com/open-webui/open-webui/commit/a4380c31f22a86361219f0a5fe62cf773cb9a6c2) feat: implement data integrity lock for chat histories - [`19e0c15`](https://github.com/open-webui/open-webui/commit/19e0c154a033d827030a1b1e3aa40788a7e33dbb) feat(orchestration): Polish MoA UX and error handling - [`62147fc`](https://github.com/open-webui/open-webui/commit/62147fc05123878f8e933ebfd68ff0f596535c28) feat(orchestration): harden server-side orchestration with distributed locks, latency tracking, and improved resilience - [`a80825d`](https://github.com/open-webui/open-webui/commit/a80825d3ce1878203a9fff66a030f3904c0db52f) feat: improve resilience for slow models (increased timeouts, enabled server-side orchestration, and added request retry logic) - [`7b852d3`](https://github.com/open-webui/open-webui/commit/7b852d3421f92fbfdd8f84c9313326e2b3fd49b5) Refactor: Disable Server-Side Orchestration and implement Smart Retry logic to fix 'Request Error' and prevent session leaks. - [`9014ebc`](https://github.com/open-webui/open-webui/commit/9014ebc905c5a9194481bc0cf28947378de02cf5) Refactor: Broaden retry logic to include all errors (including 400-level) as requested. ### 📊 Changes **20 files changed** (+1142 additions, -308 deletions) <details> <summary>View changed files</summary> ➕ `EXECUTION_PLAN_SERVER_SIDE_ORCHESTRATION.md` (+51 -0) ➕ `analyze_json.py` (+44 -0) 📝 `backend/open_webui/config.py` (+6 -0) 📝 `backend/open_webui/constants.py` (+2 -0) 📝 `backend/open_webui/env.py` (+6 -2) 📝 `backend/open_webui/main.py` (+7 -90) 📝 `backend/open_webui/models/chats.py` (+140 -32) 📝 `backend/open_webui/routers/chats.py` (+7 -1) 📝 `backend/open_webui/routers/ollama.py` (+88 -59) 📝 `backend/open_webui/routers/openai.py` (+66 -41) 📝 `backend/open_webui/socket/main.py` (+15 -0) 📝 `backend/open_webui/utils/chat.py` (+313 -4) 📝 `backend/open_webui/utils/middleware.py` (+72 -0) 📝 `backend/open_webui/utils/misc.py` (+15 -2) ➕ `backend/tests/check_import.py` (+13 -0) ➕ `backend/tests/test_integrity_lock.py` (+127 -0) ➕ `convert_chat.py` (+50 -0) 📝 `src/lib/apis/index.ts` (+12 -16) 📝 `src/lib/components/chat/Chat.svelte` (+93 -54) 📝 `src/lib/components/chat/Messages.svelte` (+15 -7) </details> ### 📄 Description # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request. This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR. **Before submitting, make sure you've checked the following:** - [ ] **Target branch:** Verify that the pull request targets the `dev` branch. **Not targeting the `dev` branch will lead to immediate closure of the PR.** - [ ] **Description:** Provide a concise description of the changes made in this pull request down below. - [ ] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** If necessary, update relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs) like environment variables, the tutorials, or other documentation sources. - [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [ ] **Testing:** Perform manual tests to **verify the implemented fix/feature works as intended AND does not break any other functionality**. Take this as an opportunity to **make screenshots of the feature/fix and include it in the PR description**. - [ ] **Agentic AI Code:** Confirm this Pull Request is **not written by any AI Agent** or has at least **gone through additional human review AND manual testing**. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR. - [ ] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [ ] **Title Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description - [Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)] ### Added - [List any new features, functionalities, or additions] ### Changed - [List any changes, updates, refactorings, or optimizations] ### Deprecated - [List any deprecated functionality or features that have been removed] ### Removed - [List any removed features, files, or functionalities] ### Fixed - [List any fixes, corrections, or bug fixes] ### Security - [List any new or updated security-related changes, including vulnerability fixes] ### Breaking Changes - **BREAKING CHANGE**: [List any breaking changes affecting compatibility or functionality] --- ### Additional Information - [Insert any additional context, notes, or explanations for the changes] - [Reference any related issues, commits, or other relevant information] ### Screenshots or Videos - [Attach any relevant screenshots or videos demonstrating the changes] ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. > [!NOTE] > Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-20 06:08:53 -05:00
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 pull-request
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#25836
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?