binary-husky / binary-husky/gpt_academic

[Bug]: 通义千问请配置 DASHSCOPE_API_KEY

Open
#1,899 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
71.3k
Forks
8.3k
PR merge metrics
No merged PRs in 30d

Description

### Installation Method | 安装方法与平台

Anaconda (I used latest requirements.txt)

### Version | 版本

Latest | 最新版

### OS | 操作系统

Windows

### Describe the bug | 简述

我在config_private.py添加了api_key`API_KEY = "sk-fxxxxxxxxxxxxxxxxab"`;模型选择添加了通义千问
```
LLM_MODEL = "qwen-turbo" # 可选 ↓↓↓
AVAIL_LLM_MODELS = ["qwen-turbo", "qwen-plus", "qwen-max", "qwen-local",
"gpt-4-1106-preview", "gpt-4-turbo-preview", "gpt-4-vision-preview",
"gpt-4o", "gpt-4-turbo", "gpt-4-turbo-2024-04-09",
"gpt-3.5-turbo-1106", "gpt-3.5-turbo-16k", "gpt-3.5-turbo", "azure-gpt-3.5",
"gpt-4", "gpt-4-32k", "azure-gpt-4", "glm-4", "glm-4v", "glm-3-turbo",
"gemini-pro", "chatglm3"
]
```
此外,我再电脑环境变量新建了DASHSCOPE_API_KEY
当我开始对话的时候还是说**请配置 DASHSCOPE_API_KEY**

### Screen Shot | 有帮助的截图

![image](https://github.com/user-attachments/assets/97d84e2f-2d8a-48d3-90ca-ec60bae892eb)

![image](https://github.com/user-attachments/assets/cb5b4917-8330-4fa3-99cf-6bc535dc995a)

### Terminal Traceback & Material to Help Reproduce Bugs | 终端traceback(如有) + 帮助我们复现的测试材料样本(如有)

![image](https://github.com/user-attachments/assets/5d370284-85ca-4f03-95e4-bf05286bec30)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by checking config_private.py and the model-selection settings in the latest requirements.txt setup, then trace how the qwen-turbo conversation reads DASHSCOPE_API_KEY on Windows. Reproduce the reported prompt and confirm that a correctly configured key allows the conversation to start without the configuration error.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ai
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.