QuantumNous / QuantumNous/new-api
请教think2Content的问题
Open
Nobody has claimed this yet.
bug
stale
- Dominant language
- Go
- Stars
- 48.5k
- Forks
- 11.6k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 58
Description
例行检查
- 我已确认目前没有类似 issue
- 我已确认我已升级到最新版本
- 我已完整查看过项目 README，尤其是常见问题部分
- 我理解并愿意跟进此 issue，协助测试和提供反馈
- 我理解并认可上述内容，并理解项目维护者精力有限，不遵循规则的 issue 可能会被无视或直接关闭
问题描述
发现代码里think2Content部分只对流式生效，想问下为什么非流的情况不进行转换
复现步骤
预期结果
相关截图
如果没有的话，请删除此节。
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the think2Content handling entry point in the Go code and compare how streaming and non-streaming responses are processed. Confirm the current behavior for both paths, then clarify the expected non-stream conversion and add or update coverage if the relevant test location can be identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100