[PR #17110] [CLOSED] fix: fix docs parse from uploadWeb #24330

New Issue

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

GiteaMirror commented

2026-04-20 05:20:53 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/17110
Author: @ShirasawaSama
Created: 9/1/2025
Status: ❌ Closed

Base: dev ← Head: patch-11

📝 Commits (1)

bda8df4 fix: fix docs parse from uploadWeb

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 backend/open_webui/retrieval/utils.py (+1 -1)

📄 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

Currently, documents added via the uploadWeb function are of type ‘doc’, but the backend does not perform any processing, resulting in the document content not being passed to the LLM. For example, documents loaded by adding the URL query parameter load-url=http://example.com/a.txt are not processed at all. Therefore, I treat documents with the type name ‘doc’ as ‘text’ documents for processing.

https://github.com/open-webui/open-webui/blob/main/src/lib/components/chat/Chat.svelte#L674

https://github.com/open-webui/open-webui/blob/main/src/lib/components/chat/Chat.svelte#L703

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

fix docs parse from uploadWeb

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

Please note: I have only tested my modified code, and the uploadWeb function works correctly when passing a text document.

I have not tested whether the uploadYoutubeTranscription function or other scenarios function properly.

I'd appreciate it if Tim @tjbck could test for other scenarios.

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/17110 **Author:** [@ShirasawaSama](https://github.com/ShirasawaSama) **Created:** 9/1/2025 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `patch-11` --- ### 📝 Commits (1) - [`bda8df4`](https://github.com/open-webui/open-webui/commit/bda8df4bc69294f7e4ba563f168ffd7ae323dc55) fix: fix docs parse from uploadWeb ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/retrieval/utils.py` (+1 -1) </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:** - [x] **Target branch:** Please verify that the pull request targets the `dev` branch. - [x] **Description:** Provide a concise description of the changes made in this pull request. - [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [x] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [x] **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? - [x] **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? - [x] **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 - Currently, documents added via the `uploadWeb` function are of type `‘doc’`, but the backend does not perform any processing, resulting in the document content not being passed to the LLM. For example, documents loaded by adding the URL query parameter `load-url=http://example.com/a.txt` are not processed at all. Therefore, I treat documents with the type name `‘doc’` as `‘text’` documents for processing. https://github.com/open-webui/open-webui/blob/main/src/lib/components/chat/Chat.svelte#L674 https://github.com/open-webui/open-webui/blob/main/src/lib/components/chat/Chat.svelte#L703 ### 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 - fix docs parse from `uploadWeb` ### 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 **Please note: I have only tested my modified code, and the `uploadWeb` function works correctly when passing a text document.** I have not tested whether the `uploadYoutubeTranscription` function or other scenarios function properly. I'd appreciate it if Tim @tjbck could test for other scenarios. ### 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:20:53 -05:00

GiteaMirror closed this issue

2026-04-20 05:20:54 -05:00

GiteaMirror referenced this issue

2026-05-06 00:29:57 -05:00

[GH-ISSUE #24330] issue: Uvicorn worker crash loop on chat completion when tool servers are unreachable causes CPU exhaustion and system unresponsiveness #58935

Sign in to join this conversation.