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] split knowledge timeout of 60000ms exceeded #1541

Closed
3 of 15 tasks
cm04918 opened this issue May 20, 2024 · 1 comment · Fixed by #1548
Closed
3 of 15 tasks

[Bug] split knowledge timeout of 60000ms exceeded #1541

cm04918 opened this issue May 20, 2024 · 1 comment · Fixed by #1548
Labels
bug Something isn't working Waiting for reply

Comments

@cm04918
Copy link

cm04918 commented May 20, 2024

Search before asking

  • I had searched in the issues and found no similar issues.

Operating system information

Linux

Python version information

=3.11

DB-GPT version

main

Related scenes

  • Chat Data
  • Chat Excel
  • Chat DB
  • Chat Knowledge
  • Model Management
  • Dashboard
  • Plugins

Installation Information

Device information

Intel(R) Xeon(R) Gold 5218 CPU @ 2.30GHz * 2
2个物理CPU,16个物理核心,64个逻辑核心

Models information

bge-reranker-base
text2vec-large-chinese

What happened

在添加knowledge 内容时提示超时,后台分割正常没错误提示,就是这个对话框在这不动了。也不是次次都有。

What you expected to happen

在添加knowledge 内容时提示超时

How to reproduce

在添加knowledge 内容时

Additional context

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!
@cm04918 cm04918 added bug Something isn't working Waiting for reply labels May 20, 2024
@cm04918
Copy link
Author

cm04918 commented May 20, 2024

1
2

@Aries-ckt Aries-ckt changed the title [Bug] 分割knowledge 提示timeout of 60000ms exceeded [Bug] split knowledge timeout of 60000ms exceeded May 20, 2024
Aries-ckt added a commit to Aries-ckt/DB-GPT that referenced this issue May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Waiting for reply
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant