[PR #15550] [CLOSED] Dev local original #23868

New Issue

GiteaMirror · 2026-04-20T05:05:33-05:00

GiteaMirror commented

2026-04-20 05:05:33 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/15550
Author: @ipdeepdive
Created: 7/6/2025
Status: ❌ Closed

Base: main ← Head: dev-local-original

📝 Commits (3)

b4868eb ready for deploy version
63d4b45 ready for deploy version
e22a82b Merge branch 'main' of github.com:ipdeepdive/open-webui into dev-local-original

📊 Changes

53 files changed (+4323 additions, -2605 deletions)

View changed files

➕ .github/workflows/sync-and-build.yml (+159 -0)
➖ CHANGELOG.md (+0 -2194)
➖ CODE_OF_CONDUCT.md (+0 -99)
➕ CUSTOM_BUILD.md (+132 -0)
➕ Dockerfile.custom (+56 -0)
➕ Dockerfile.local-assets (+48 -0)
➕ Dockerfile.patch-runtime (+37 -0)
➕ Dockerfile.patched (+26 -0)
➕ Dockerfile.simple (+18 -0)
➕ Dockerfile.xynthor-final (+61 -0)
➕ Dockerfile.xynthor-fixed (+9 -0)
➕ Dockerfile.xynthor-logo (+61 -0)
➕ Dockerfile.xynthor-v3 (+63 -0)
➕ Dockerfile.xynthor-v4 (+86 -0)
➕ Dockerfile.xynthor-v5 (+91 -0)
➕ Dockerfile.xynthor-v6 (+65 -0)
➕ Dockerfile.xynthor-v7 (+65 -0)
➕ Dockerfile.xynthor-v8 (+73 -0)
➕ FIX_REMOTES.md (+81 -0)
➕ FORK_SAFETY_GUIDE.md (+267 -0)

...and 33 more files

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.

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

Target branch: Please verify that the pull request targets the dev branch.
Description: Provide a concise description of the changes made in this pull request.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Have you written and run sufficient tests to validate the changes?
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?
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.

_{🔄 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/15550 **Author:** [@ipdeepdive](https://github.com/ipdeepdive) **Created:** 7/6/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `dev-local-original` --- ### 📝 Commits (3) - [`b4868eb`](https://github.com/open-webui/open-webui/commit/b4868eb2634dd4abe9f7d9cabc51b27add99d5ec) ready for deploy version - [`63d4b45`](https://github.com/open-webui/open-webui/commit/63d4b454324977036ffef9c7fe7a287feba473fa) ready for deploy version - [`e22a82b`](https://github.com/open-webui/open-webui/commit/e22a82ba19c204f6da2bad208bc0cb81bb1d8b20) Merge branch 'main' of github.com:ipdeepdive/open-webui into dev-local-original ### 📊 Changes **53 files changed** (+4323 additions, -2605 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/sync-and-build.yml` (+159 -0) ➖ `CHANGELOG.md` (+0 -2194) ➖ `CODE_OF_CONDUCT.md` (+0 -99) ➕ `CUSTOM_BUILD.md` (+132 -0) ➕ `Dockerfile.custom` (+56 -0) ➕ `Dockerfile.local-assets` (+48 -0) ➕ `Dockerfile.patch-runtime` (+37 -0) ➕ `Dockerfile.patched` (+26 -0) ➕ `Dockerfile.simple` (+18 -0) ➕ `Dockerfile.xynthor-final` (+61 -0) ➕ `Dockerfile.xynthor-fixed` (+9 -0) ➕ `Dockerfile.xynthor-logo` (+61 -0) ➕ `Dockerfile.xynthor-v3` (+63 -0) ➕ `Dockerfile.xynthor-v4` (+86 -0) ➕ `Dockerfile.xynthor-v5` (+91 -0) ➕ `Dockerfile.xynthor-v6` (+65 -0) ➕ `Dockerfile.xynthor-v7` (+65 -0) ➕ `Dockerfile.xynthor-v8` (+73 -0) ➕ `FIX_REMOTES.md` (+81 -0) ➕ `FORK_SAFETY_GUIDE.md` (+267 -0) _...and 33 more files_ </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) and describe your changes before submitting a pull request. **Before submitting, make sure you've checked the following:** - [ ] **Target branch:** Please verify that the pull request targets the `dev` branch. - [ ] **Description:** Provide a concise description of the changes made in this pull request. - [ ] **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:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [ ] **Testing:** Have you written and run sufficient tests to validate the changes? - [ ] **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? - [ ] **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)](/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <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 05:05:33 -05:00

GiteaMirror closed this issue

2026-04-20 05:05:36 -05:00

GiteaMirror referenced this issue

2026-04-20 07:03:35 -05:00

[PR #23868] fix: always rAF-throttle markdown parsing during streaming #27414

GiteaMirror referenced this issue

2026-04-25 14:45:35 -05:00

[PR #23868] [MERGED] fix: always rAF-throttle markdown parsing during streaming #43046

GiteaMirror referenced this issue

2026-04-30 03:10:58 -05:00

[PR #23868] [MERGED] fix: always rAF-throttle markdown parsing during streaming #50464