langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Test external knowledge base retrieval, the console reports an error in v0.15.0 #7629

New Issue
Closed
opened 2026-02-21 18:21:33 -05:00 by yindo · 7 comments
yindo commented 2026-02-21 18:21:33 -05:00
Owner
Copy Link
Copy Source

Originally created by @SpringWindInTheDrizzle on GitHub (Jan 9, 2025).

Originally assigned to: @WTW0313 on GitHub.

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

v0.15.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. Create an external knowledge base
  2. Recall test

✔️ Expected Behavior

When I downgraded to v0.14.1, it worked

❌ Actual Behavior

Page error：Application error: a client-side exception has occurred (see the browser console for more information).

console: TypeError: Cannot read properties of undefined (reading 'name')

Problems may occur in the path: web/app/components/datasets/hit-testing/components/result-item.tsx

const extension = document.name.split('.').slice(-1)[0] as FileAppearanceTypeEnum
Originally created by @SpringWindInTheDrizzle on GitHub (Jan 9, 2025). Originally assigned to: @WTW0313 on GitHub. ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version v0.15.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. Create an external knowledge base 2. Recall test ### ✔️ Expected Behavior When I downgraded to v0.14.1, it worked ### ❌ Actual Behavior Page error：`Application error: a client-side exception has occurred (see the browser console for more information).` console: `TypeError: Cannot read properties of undefined (reading 'name')` Problems may occur in the path: `web/app/components/datasets/hit-testing/components/result-item.tsx` ``` const extension = document.name.split('.').slice(-1)[0] as FileAppearanceTypeEnum ```
yindo added the 🐞 buggood first issue labels 2026-02-21 18:21:33 -05:00
yindo closed this issue 2026-02-21 18:21:33 -05:00
yindo commented 2026-02-21 18:21:33 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 9, 2025):

Hello @SpringWindInTheDrizzle! I'm here to help you with any bugs, questions, or contributions you have in mind. Let's work together to resolve any issues you're facing.

I found a similar open issue related to a client-side exception in Dify. The suggested solution is to check if your version includes the fix for the issue titled "Minified React error #31 - Application error: a client-side exception has occurred" and see if there are any updates available that address this issue. Additionally, reviewing the browser console for more detailed error messages could provide further insights into the problem [1].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot[bot] commented on GitHub (Jan 9, 2025): <!-- Greeting --> Hello @SpringWindInTheDrizzle! I'm here to help you with any bugs, questions, or contributions you have in mind. Let's work together to resolve any issues you're facing. <!-- Answer --> I found a similar open issue related to a client-side exception in Dify. The suggested solution is to check if your version includes the fix for the issue titled "Minified React error #31 - Application error: a client-side exception has occurred" and see if there are any updates available that address this issue. Additionally, reviewing the browser console for more detailed error messages could provide further insights into the problem <sup>[[1]](https://github.com/langgenius/dify/issues/12532)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/cb9095b5-cd9e-4611-b73e-bb6c18cd9a8d?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/cb9095b5-cd9e-4611-b73e-bb6c18cd9a8d?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/cb9095b5-cd9e-4611-b73e-bb6c18cd9a8d?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/cb9095b5-cd9e-4611-b73e-bb6c18cd9a8d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/cb9095b5-cd9e-4611-b73e-bb6c18cd9a8d?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/cb9095b5-cd9e-4611-b73e-bb6c18cd9a8d?feedback_type=other)</sup>
yindo commented 2026-02-21 18:21:34 -05:00
Author
Owner
Copy Link
Copy Source

@CellMook commented on GitHub (Jan 10, 2025):

Has this issue been resolved? I'm encountering the same problem. I suspect it's caused by the structure of the content returned by the external knowledge base not being consistent with Dify's knowledge base structure. However, I don't know how to resolve this issue. I'm using the Ragflow knowledge base.

@CellMook commented on GitHub (Jan 10, 2025): Has this issue been resolved? I'm encountering the same problem. I suspect it's caused by the structure of the content returned by the external knowledge base not being consistent with Dify's knowledge base structure. However, I don't know how to resolve this issue. I'm using the Ragflow knowledge base.
yindo commented 2026-02-21 18:21:34 -05:00
Author
Owner
Copy Link
Copy Source

@Serious-H commented on GitHub (Jan 10, 2025):

Has this issue been resolved? I'm encountering the same problem. I suspect it's caused by the structure of the content returned by the external knowledge base not being consistent with Dify's knowledge base structure. However, I don't know how to resolve this issue. I'm using the Ragflow knowledge base.@CellMook

image

I am also using the Ragflow knowledge base. Initially, I used Dify version 0.15.0 and encountered this error. However, after downgrading to version 0.14.2, it displayed correctly. I noticed that the data returned during the error was normal, but the web display failed. I suspect it might be an issue with the Dify frontend code.

@Serious-H commented on GitHub (Jan 10, 2025): > Has this issue been resolved? I'm encountering the same problem. I suspect it's caused by the structure of the content returned by the external knowledge base not being consistent with Dify's knowledge base structure. However, I don't know how to resolve this issue. I'm using the Ragflow knowledge base.@CellMook ![image](https://github.com/user-attachments/assets/a85d1d66-ccf3-4db2-9585-26afb786f961) I am also using the Ragflow knowledge base. Initially, I used Dify version 0.15.0 and encountered this error. However, after downgrading to version 0.14.2, it displayed correctly. I noticed that the data returned during the error was normal, but the web display failed. I suspect it might be an issue with the Dify frontend code.
yindo commented 2026-02-21 18:21:34 -05:00
Author
Owner
Copy Link
Copy Source

@WTW0313 commented on GitHub (Jan 20, 2025):

Our team went on a vacation last week and today is the first day we come back to work. The pull request is now under review. The issue #12564 will soon be resolved. Appreciated for your patience. @SpringWindInTheDrizzle @Serious-H @CellMook

@WTW0313 commented on GitHub (Jan 20, 2025): Our team went on a vacation last week and today is the first day we come back to work. The pull request is now under review. The issue #12564 will soon be resolved. Appreciated for your patience. @SpringWindInTheDrizzle @Serious-H @CellMook
yindo commented 2026-02-21 18:21:34 -05:00
Author
Owner
Copy Link
Copy Source

@Patientrookie commented on GitHub (Mar 11, 2025):

Hello, may I ask if this problem has been solved now? I found this problem again in 0.15.3

Image

@Patientrookie commented on GitHub (Mar 11, 2025): Hello, may I ask if this problem has been solved now? I found this problem again in 0.15.3 ![Image](https://github.com/user-attachments/assets/a4363686-bdd1-47b7-8bea-6238dee4c299)
yindo commented 2026-02-21 18:21:34 -05:00
Author
Owner
Copy Link
Copy Source

@WTW0313 commented on GitHub (Mar 11, 2025):

Hello, may I ask if this problem has been solved now? I found this problem again in 0.15.3

Image

Hello, @Patientrookie. This problem should have been solved in PR #12612. Would you kindly provide more details, such as the data structure returned by Ragflow Knowledge API. Thank you for your assistance.

@WTW0313 commented on GitHub (Mar 11, 2025): > Hello, may I ask if this problem has been solved now? I found this problem again in 0.15.3 > > ![Image](https://github.com/user-attachments/assets/a4363686-bdd1-47b7-8bea-6238dee4c299) Hello, @Patientrookie. This problem should have been solved in PR #12612. Would you kindly provide more details, such as the data structure returned by Ragflow Knowledge API. Thank you for your assistance.
yindo commented 2026-02-21 18:21:34 -05:00
Author
Owner
Copy Link
Copy Source

@Patientrookie commented on GitHub (Mar 11, 2025):

@WTW0313 I just tried to delete the previous front-end docker image and then re-pull the latest version of the front-end image, and the problem was solved，Thank you very much for your reply.

@Patientrookie commented on GitHub (Mar 11, 2025): @WTW0313 I just tried to delete the previous front-end docker image and then re-pull the latest version of the front-end image, and the problem was solved，Thank you very much for your reply.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label good first issue 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#7629
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?