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

[Bug]: Whole System Broke after parsing a 100 line table #2860

Closed
1 task done
yw2598 opened this issue Oct 16, 2024 · 6 comments
Closed
1 task done

[Bug]: Whole System Broke after parsing a 100 line table #2860

yw2598 opened this issue Oct 16, 2024 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@yw2598
Copy link

yw2598 commented Oct 16, 2024

Is there an existing issue for the same bug?

  • I have checked the existing issues.

Branch name

main

Commit ID

current

Other environment information

Ubuntu 2204 Docker V0.12

Actual behavior

After parsing the a 100 line table, chat will only respond one message even if I disable the table document or change to a different chat.
This will only be resolved after a whole deletion of every knowledge base.

Expected behavior

No response

Steps to reproduce

Parse a table with 100 rows, 

sample row: 
编号 定义 速度 备注 
F0-01 低压端子 3 none

Additional information

No response

@yw2598 yw2598 added the bug Something isn't working label Oct 16, 2024
@KevinHuSh
Copy link
Collaborator

Could you specify the error message?

@yw2598
Copy link
Author

yw2598 commented Oct 17, 2024

There is no error message, but in the chat dialogue, no matter what I input, regardless of the knowledge base, embedding model, or llm model used, the assistant will only reply with the same message, a message contains a dozens of rows for the table I parsed, and even reference to documents that has been deleted. Also, I add keywords to every chunk of the parsed table, the keywords are product codes, such as RS32, ragflow seems cannot detect error codes or product codes, which are combinations or letters and numbers, is this a problem with embedding or something else?

@KevinHuSh
Copy link
Collaborator

What about using General as the parsing method.

@yw2598
Copy link
Author

yw2598 commented Oct 17, 2024

it seams like once the excel is parsed, there is no other way to delete it, except deleting all the knowledge bases. I will try General method with a fresh build docker image on my another machine to avoid contaminating my running server.

@yuzhichang
Copy link
Member

@yw2598 I cannot reproduce this issue with v0.14.1. Can you upload the excel which cause the issue?

@yuzhichang yuzhichang self-assigned this Dec 2, 2024
@yuzhichang
Copy link
Member

Close due to no response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants