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] [Agent] Request error #1464

Closed
4 of 15 tasks
Dingzhen778 opened this issue Apr 24, 2024 · 2 comments · Fixed by #1478
Closed
4 of 15 tasks

[Bug] [Agent] Request error #1464

Dingzhen778 opened this issue Apr 24, 2024 · 2 comments · Fixed by #1478
Labels
bug Something isn't working Waiting for reply

Comments

@Dingzhen778
Copy link

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

GPU:A6000

Models information

LLM:Qwen-72B-Chat
models:text2vec-large-chinese

What happened

when I create a new agent,a error happened(I don't set anything,only in DB-GPT0.5.4)
request-error
Request error
1 validation errors: {'type': 'string_type', "loc’:('response', 'data"), 'msg': 'Input should be avalid string', "input':['power_llm_meta_platform"]}

What you expected to happen

create a new Agent successfully

How to reproduce

use DB-GPT-0.5.4,create a new Agent

Additional context

No response

Are you willing to submit PR?

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

this problem only happened in ver0.5.4

@xiaoshuichong
Copy link

I upgrade to 0.5.5, still happen

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.

2 participants