mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-16 14:39:31 -05:00
[GH-ISSUE #11204] RAG reference source id always 0 #16143
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#16143
Reference in New Issue
Block a user
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?
Originally created by @ericXu08 on GitHub (Mar 5, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/11204
Bug Report
Installation Method
anaconda pip install
Environment
Open WebUI Version: [v0.5.18]
Ollama (if applicable): [0.5.7]
Operating System: [Windows 10]
Browser (if applicable): [Chrome 135.0.7039.0]
Confirmation:
Expected Behavior:
when i use rag to ask question, the response should return the keypoint with the correct reference souce name(in this case it should be file name)
Actual Behavior:
when i use rag to ask question, the response return the keypoint always with souce id =0,which always indicator the first file.
Description
Bug Summary:
RAG reference source id always 0
Reproduction Details
Steps to Reproduce:
[Outline the steps to reproduce the bug. Be as detailed as possible.]
1、configure the document embedding
2、create KB
3、use model as deepseek-R1
4、ask question and response
the response content is correct but reference source is wrong, actually it should reference the second file
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots/Screen Recordings (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
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!
@ericXu08 commented on GitHub (Mar 5, 2025):
please help me to look this issue, really appreciate that.