Skip to content
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

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

Closed
5 tasks done
SpringWindInTheDrizzle opened this issue Jan 9, 2025 · 4 comments · Fixed by #12612
Closed
5 tasks done
Assignees
Labels
🐞 bug Something isn't working good first issue Good first issue for newcomers

Comments

@SpringWindInTheDrizzle
Copy link

SpringWindInTheDrizzle commented Jan 9, 2025

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
@dosubot dosubot bot added the 🐞 bug Something isn't working label Jan 9, 2025
Copy link

dosubot bot commented 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

@crazywoola crazywoola added the good first issue Good first issue for newcomers label Jan 9, 2025
@CellMook
Copy link

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.

@Serious-H
Copy link

Serious-H commented 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.

@WTW0313
Copy link
Collaborator

WTW0313 commented Jan 21, 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

iamjoel pushed a commit that referenced this issue Jan 21, 2025
Scorpion1221 added a commit to yybht155/dify that referenced this issue Jan 21, 2025
* commit '6db3ae9b8ec2f8491e2c9355056a8693ecd67f47': (22 commits)
  chore: remove webapp ga (langgenius#12909)
  fix: variable panel scrollable (langgenius#12769)
  fix: OpenAI o1 Bad Request Error (langgenius#12839)
  Update deepseek model configuration (langgenius#12899)
  fix: external dataset hit test display issue(langgenius#12564) (langgenius#12612)
  add deepseek-reasoner (langgenius#12898)
  chore(fix): Invalid quotes for using Array[String] in HTTP request node as JSON body (langgenius#12761)
  fix: Issues related to the deletion of conversation_id (langgenius#12488) (langgenius#12665)
  chore(lint): fix quotes for f-string formatting by bumping ruff to 0.9.x (langgenius#12702)
  feat:Support Minimax-Text-01 (langgenius#12763)
  fix: serply credential check query might return empty records (langgenius#12784)
  feat: allow updating chunk settings for the existing documents (langgenius#12833)
  fix: SparkLite API Auth error (langgenius#12781) (langgenius#12790)
  fix: "parmas" spelling mistake. (langgenius#12875)
  Fix suggested_question_prompt (langgenius#12738)
  fix(i18n): correct typo in zh-Hant translation (langgenius#12852)
  chore: fix chinese translation for 'recall' (langgenius#12772)
  fix: DeepSeek API Error with response format active (text and json_object)  (langgenius#12747)
  feat: enhance credential extraction logic based on configurate method (langgenius#12853)
  fix: Fix rerank model switching issue (langgenius#12721)
  ...

# Conflicts:
#	api/core/tools/utils/message_transformer.py
#	api/poetry.lock
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working good first issue Good first issue for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants