[PR #17857] [MERGED] feat: add backend handling for unarchiving all chats #24577

New Issue

GiteaMirror · 2026-04-20T05:28:24-05:00

GiteaMirror commented

2026-04-20 05:28:24 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/17857
Author: @silentoplayz
Created: 9/28/2025
Status: ✅ Merged
Merged: 9/28/2025
Merged by: @tjbck

Base: dev ← Head: feat-bulk-unarchive

📝 Commits (1)

a572cf4 feat: add backend handling for unarchiving all chats

📊 Changes

4 files changed (+77 additions, -9 deletions)

View changed files

📝 backend/open_webui/models/chats.py (+9 -0)
📝 backend/open_webui/routers/chats.py (+10 -0)
📝 src/lib/apis/chats/index.ts (+32 -0)
📝 src/lib/components/layout/ArchivedChatsModal.svelte (+26 -9)

📄 Description

Pull Request Checklist

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

This pull request introduces a new backend endpoint to handle bulk unarchiving of all chats for a user. The frontend has been updated to use this new endpoint, which resolves a performance issue where each chat was being unarchived individually, potentially overloading the server.

Added

New backend endpoint /chats/unarchive/all to unarchive all of a user's chats in a single request.
New unarchive_all_chats_by_user_id method in the Chats database model.
New unarchiveAllChats API function in the frontend to call the new backend endpoint.

Changed

The unarchiveAllHandler function in ArchivedChatsModal.svelte now calls the new unarchiveAllChats API function instead of looping through and unarchiving chats one by one.

Removed

The client-side loop for unarchiving all chats in ArchivedChatsModal.svelte.

Fixed

A performance issue that could cause a large number of requests to be sent to the server when unarchiving all chats.

Additional Information

This change addresses the problem of potential server overload from excessive individual unarchive requests.
Related comment provided by maintainer about the previous implementation attempt of mine to speed up the process of un-archiving all archived chats - https://github.com/open-webui/open-webui/pull/17831#issuecomment-3343868719

Screenshots and Videos

Time to unarchive all archived chats previously (MANY REQUESTS, COSTLY, SLOW):

Time to unarchive all archived chats with these changes applied (99% LESS REQUESTS, >1MB, FAST):

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/17857 **Author:** [@silentoplayz](https://github.com/silentoplayz) **Created:** 9/28/2025 **Status:** ✅ Merged **Merged:** 9/28/2025 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `feat-bulk-unarchive` --- ### 📝 Commits (1) - [`a572cf4`](https://github.com/open-webui/open-webui/commit/a572cf48426f607548f1f3da350bcf2fe143eb0e) feat: add backend handling for unarchiving all chats ### 📊 Changes **4 files changed** (+77 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/models/chats.py` (+9 -0) 📝 `backend/open_webui/routers/chats.py` (+10 -0) 📝 `src/lib/apis/chats/index.ts` (+32 -0) 📝 `src/lib/components/layout/ArchivedChatsModal.svelte` (+26 -9) </details> ### 📄 Description # Pull Request Checklist - [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? - [X] **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 - This pull request introduces a new backend endpoint to handle bulk unarchiving of all chats for a user. The frontend has been updated to use this new endpoint, which resolves a performance issue where each chat was being unarchived individually, potentially overloading the server. ### Added - New backend endpoint `/chats/unarchive/all` to unarchive all of a user's chats in a single request. - New `unarchive_all_chats_by_user_id` method in the Chats database model. - New `unarchiveAllChats` API function in the frontend to call the new backend endpoint. ### Changed - The `unarchiveAllHandler` function in `ArchivedChatsModal.svelte` now calls the new `unarchiveAllChats` API function instead of looping through and unarchiving chats one by one. ### Removed - The client-side loop for unarchiving all chats in `ArchivedChatsModal.svelte`. ### Fixed - A performance issue that could cause a large number of requests to be sent to the server when unarchiving all chats. ### Additional Information - This change addresses the problem of potential server overload from excessive individual unarchive requests. - Related comment provided by maintainer about the previous implementation attempt of mine to speed up the process of un-archiving all archived chats - https://github.com/open-webui/open-webui/pull/17831#issuecomment-3343868719 ### Screenshots and Videos <img width="970" height="568" alt="image" src="https://github.com/user-attachments/assets/c003f166-c5e3-4501-983b-05339a79fad8" /> <img width="409" height="112" alt="image" src="https://github.com/user-attachments/assets/a4e333c0-2e67-4f90-ac9d-6cf382b4beef" /> ### Time to unarchive all archived chats previously (MANY REQUESTS, COSTLY, SLOW): <img width="2560" height="537" alt="image" src="https://github.com/user-attachments/assets/557a5f81-064d-42c1-8409-7cbd052322f5" /> ### Time to unarchive all archived chats with these changes applied (99% LESS REQUESTS, >1MB, FAST): <img width="2560" height="537" alt="image" src="https://github.com/user-attachments/assets/ff2870e1-3ce8-4d29-967e-e5002eee9559" /> ### 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. --- <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:28:24 -05:00

GiteaMirror closed this issue

2026-04-20 05:28:24 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#24577