-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Dashscope service causing :ValueError: too many values to unpack (expected 11) #1367
Comments
Thanks for your report. Could you please submit a pull request with your proposed changes? |
xiaoxiaoimg
pushed a commit
to xiaoxiaoimg/MetaGPT
that referenced
this issue
Jul 16, 2024
…urned by _get_protocol_params
xiaoxiaoimg
pushed a commit
to xiaoxiaoimg/MetaGPT
that referenced
this issue
Jul 16, 2024
…urned by _get_protocol_params
xiaoxiaoimg
pushed a commit
to xiaoxiaoimg/MetaGPT
that referenced
this issue
Jul 16, 2024
…urned by _get_protocol_params
xiaoxiaoimg
pushed a commit
to xiaoxiaoimg/MetaGPT
that referenced
this issue
Aug 22, 2024
…urned by _get_protocol_params
xiaoxiaoimg
pushed a commit
to xiaoxiaoimg/MetaGPT
that referenced
this issue
Sep 12, 2024
…urned by _get_protocol_params
xiaoxiaoimg
pushed a commit
to xiaoxiaoimg/MetaGPT
that referenced
this issue
Sep 23, 2024
…urned by _get_protocol_params
xiaoxiaoimg
pushed a commit
to xiaoxiaoimg/MetaGPT
that referenced
this issue
Sep 24, 2024
xiaoxiaoimg
pushed a commit
to xiaoxiaoimg/MetaGPT
that referenced
this issue
Sep 24, 2024
…it to CompletionUsage
@dahaipeng |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
MetaGPT/metagpt/provider/dashscope_api.py
Line 51 in 9f8f0a2
When using DashScope service, in this line, the
_get_protocol_params
method returns 13 values but the unpack logic assumes that 11 values are returned, causing the ValueError: too many values to unpack (expected 11).A proper way that works for me is adding another two values in the unpacking logic:
The version of dashscope package is
1.19.3
The text was updated successfully, but these errors were encountered: