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

feat: Support retry for 'Chat Data' #1419

Merged
merged 3 commits into from
Apr 15, 2024

Conversation

fangyinc
Copy link
Collaborator

Description

In some scenarios, we need to call the LLM in parallel, select the successful result, or retry in case of failure.

How Has This Been Tested?

  1. Modify .env
# Non-streaming scene retries
DBGPT_APP_SCENE_NON_STREAMING_RETRIES_BASE=2
# Non-streaming scene parallelism
DBGPT_APP_SCENE_NON_STREAMING_PARALLELISM_BASE=2
  1. Restart DB-GPT
  2. Use "Chat Data" to perform some error-prone problems, and you will find that the success rate increases.

Snapshots:

Include snapshots for easier review.

Checklist:

  • My code follows the style guidelines of this project
  • I have already rebased the commits and make the commit message conform to the project standard.
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • Any dependent changes have been merged and published in downstream modules

@github-actions github-actions bot added the enhancement New feature or request label Apr 15, 2024
Copy link
Collaborator

@csunny csunny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

r+

Copy link
Collaborator

@Aries-ckt Aries-ckt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

r+

@Aries-ckt Aries-ckt merged commit 461607e into eosphoros-ai:main Apr 15, 2024
5 checks passed
@chuangzhidan
Copy link

chuangzhidan commented Aug 12, 2024

# Non-streaming scene retries
DBGPT_APP_SCENE_NON_STREAMING_RETRIES_BASE=2
# Non-streaming scene parallelism
DBGPT_APP_SCENE_NON_STREAMING_PARALLELISM_BASE=2

supports chat_data in scene of chat_db autoexcute?
error feedback will be included and feed back to llm?

Hopshine pushed a commit to Hopshine/DB-GPT that referenced this pull request Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants