-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sweep: chat history pagination (infinite scroll) #2
Comments
🚀 Here's the PR! #3💎 Sweep Pro: You have unlimited Sweep issues
Actions
Step 1: 🔎 SearchingHere are the code search results. I'm now analyzing these search results to write the PR. Relevant files (click to expand). Mentioned files will always appear here.open-webui/src/lib/components/layout/Sidebar.svelte Lines 1 to 749 in d43ee0f
Step 2: ⌨️ Coding
|
Add tests |
Add tests |
Bug Report
Description
Bug Summary:
When importing and loading a large number of chat sessions into Open WebUI, the application experiences significant performance degradation, causing the interface to freeze temporarily. This issue seems related to the side-panel attempting to load all chat sessions simultaneously.
Steps to Reproduce:
Expected Behavior:
The interface should remain responsive and load chat sessions smoothly without causing the entire application to freeze, regardless of the number of chats being loaded.
Actual Behavior:
The interface freezes temporarily when trying to load a large number of chat sessions at once, significantly affecting user experience and accessibility.
Environment
Open WebUI Version: 0.1.123
Ollama (if applicable): 0.1.32
Operating System: Debian 12
Browser (if applicable): Floorp 11.12.2 (64-Bit)
Reproduction Details
Confirmation:
Additional Information
One possible improvement could be the implementation of pagination or lazy loading for the chat sessions to avoid overwhelming the browser's capabilities by attempting to load extensive data simultaneously.
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!
The text was updated successfully, but these errors were encountered: