[Bug] Custom models do not support containing @, such as the claude-3-5-sonnet@20240620 model on Vertex

[rxliuli]

📦 部署方式

Vercel

📌 软件版本

2.14.2

💻 系统环境

macOS

📌 系统版本

14.4.1

🌐 浏览器

Chrome

📌 浏览器版本

127.0.6533.122

🐛 问题描述

📷 复现步骤

No response

🚦 期望结果

No response

📝 补充信息

No response

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Title: [Bug] Custom models do not support containing @, such as the claude-3-5-sonnet@20240620 model on Vertex

[QAbot-zh]

我提过类似的 pr，但还没有被合并：
#5243

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

I mentioned a similar PR, but it hasn't been merged yet:
#5243

[rxliuli]

我提过类似的 pr，但还没有被合并： #5243

似乎仅处理了类似 modelName@azure@azure 这种多个 @ 符号的情况，并未处理 modelName@azure 这种情况，例如 claude-3-5-sonnet@20240620，当然可以在后面再添加一个 @vertex 解决，例如 claude-3-5-sonnet@20240620@vertex

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

I mentioned a similar PR, but it hasn't been merged yet: #5243

It seems that it only handles the case of multiple @ symbols like modelName@azure@azure, but does not handle the case of modelName@azure, such as claude-3-5-sonnet@20240620, of course it can be done later Add another @vertex solution, for example claude-3-5-sonnet@20240620@vertex

[QAbot-zh]

我提过类似的 pr，但还没有被合并： #5243

似乎仅处理了类似 modelName@azure@azure 这种多个 @ 符号的情况，并未处理 modelName@azure 这种情况，例如 claude-3-5-sonnet@20240620，当然可以在后面再添加一个 @vertex 解决，例如 claude-3-5-sonnet@20240620@vertex

不是的，我是把最后一个@后面的部分切成 providerName，剩下部分作为 modelName

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

I mentioned a similar PR, but it hasn't been merged yet: #5243

It seems that it only handles the case of multiple @ symbols like modelName@azure@azure, but does not handle the case of modelName@azure, such as claude-3-5-sonnet@20240620. Of course, it can be used in Add another @vertex later to solve the problem, for example claude-3-5-sonnet@20240620@vertex

No, I cut the part after the last @ into providerName, and the remaining part was used as modelName

[rxliuli]

我提过类似的 pr，但还没有被合并： #5243

似乎仅处理了类似 modelName@azure@azure 这种多个 @ 符号的情况，并未处理 modelName@azure 这种情况，例如 claude-3-5-sonnet@20240620，当然可以在后面再添加一个 @vertex 解决，例如 claude-3-5-sonnet@20240620@vertex

不是的，我是把最后一个@后面的部分切成 providerName，剩下部分作为 modelName

嗯，所以如果模型本身有 @，那么自定义模型必须再使用一个 @ 避免错误分割嘛

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

I mentioned a similar PR, but it hasn't been merged yet: #5243

It seems that it only handles the case of multiple @ symbols like modelName@azure@azure, but does not handle the case of modelName@azure, such as claude-3-5-sonnet@20240620, of course it can Add another @vertex at the end to solve the problem, for example claude-3-5-sonnet@20240620@vertex

No, I cut the part after the last @ into providerName, and the remaining part was used as modelName

Well, so if the model itself has @, then the custom model must use another @ to avoid incorrect segmentation.

[QAbot-zh]

我提过类似的 pr，但还没有被合并： #5243

似乎仅处理了类似 modelName@azure@azure 这种多个 @ 符号的情况，并未处理 modelName@azure 这种情况，例如 claude-3-5-sonnet@20240620，当然可以在后面再添加一个 @vertex 解决，例如 claude-3-5-sonnet@20240620@vertex

不是的，我是把最后一个@后面的部分切成 providerName，剩下部分作为 modelName

嗯，所以如果模型本身有 @，那么自定义模型必须再使用一个 @ 避免错误分割嘛

哦理解你的意思了，可以根据切出来的 providerName 是否存在来判断要不要切，这样确实更智能一些

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

I mentioned a similar PR, but it hasn't been merged yet: #5243

It seems that it only handles the case of multiple @ symbols like modelName@azure@azure, but does not handle the case of modelName@azure, such as claude-3-5-sonnet@20240620, of course You can add another @vertex later to solve the problem, for example claude-3-5-sonnet@20240620@vertex

No, I cut the part after the last @ into providerName, and the remaining part was used as modelName.

Well, so if the model itself has @, then the custom model must use another @ to avoid incorrect segmentation.

Oh, I understand what you mean. You can judge whether to cut or not based on whether the cut out providerName exists. This is indeed smarter.