-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
[Bug]: Frontend crashes when opening chunk page generated by Knowledge Graph #4180
Closed
1 task done
Labels
bug
Something isn't working
Comments
KevinHuSh
added a commit
that referenced
this issue
Dec 23, 2024
### What problem does this PR solve? #4180 ### Type of change - [x] Bug Fix (non-breaking change which fixes an issue)
cike8899
added a commit
to cike8899/ragflow
that referenced
this issue
Dec 23, 2024
…ame as the combo ID infiniflow#4180
baifachuan
pushed a commit
to baifachuan/ragflow
that referenced
this issue
Dec 26, 2024
### What problem does this PR solve? infiniflow#4180 ### Type of change - [x] Bug Fix (non-breaking change which fixes an issue)
baifachuan
pushed a commit
to baifachuan/ragflow
that referenced
this issue
Dec 26, 2024
…ame as the combo ID infiniflow#4180 (infiniflow#4191) ### What problem does this PR solve? Fix: Fixed the issue that the page crashed when the node ID was the same as the combo ID infiniflow#4180 ### Type of change - [x] Bug Fix (non-breaking change which fixes an issue)
cike8899
added a commit
to cike8899/ragflow
that referenced
this issue
Dec 31, 2024
1 task
Thank you very much |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for the same bug?
RAGFlow workspace code commit ID
a5cf6fc
RAGFlow image version
v0.15.0
Other environment information
No response
Actual behavior
利用knowlege Graph生成的chunk,前端打开chunk页面崩溃。
result.json
Expected behavior
No response
Steps to reproduce
just open page, link like this:http://127.0.0.1/knowledge/dataset/chunk?id=xxxx&doc_id=xxx。
Additional information
No response
The text was updated successfully, but these errors were encountered: