QuantumNous / QuantumNous/new-api

大小写引起的已绑定渠道匹配异常

Open
#1,990 1 comment 1 reaction 0 assignees View on GitHub

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 可能会被无视或直接关闭

问题描述
模型名称大小写引起的模型管理中已绑定渠道无法正确匹配
复现步骤
我的deepseek-ai/DeepSeek-V3.1-Terminus配置了两个供应商,一个是硅基流动,一个是英伟达
根据上游的官方文档
硅基流动中模型名称为大写的deepseek-ai/DeepSeek-V3.1-Terminus

Image Image

英伟达中模型名称为小写的deepseek-ai/deepseek-v3.1-terminus

Image Image

deepseek-ai/DeepSeek-V3.1-Terminus和deepseek-ai/deepseek-v3.1-terminus两种名称被视为同一个模型无法重复设置
当模型管理中该模型名称设置为deepseek-ai/deepseek-v3.1-terminus的时候会显示英伟达

Image

当模型管理中该模型名称设置为deepseek-ai/DeepSeek-V3.1-Terminus的时候会显示硅基流动

Image

当模型小写时该模型会依旧处于未配置模型页面,但是配置时会提示已有相同名称模型
预期结果
在已绑定模型中一个模型显示两个渠道(大小写应该会影响上游请求吧,如果可以合并成同一个模型的时候希望向上游请求的时候会根据实际渠道的设置使用大小写)或者大小写视为不同的模型分别对应不同的已绑定渠道

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files or tests are named in the issue. Reproduce the model-management behavior with the two case variants, then trace the matching and bound-channel entry points in the Go backend. Done should be defined by whether case variants are distinct or merged, with channel-specific upstream casing preserved if they are merged, and regression coverage for the selected behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.