langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-24 12:32:54 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

After upgrading to version v1.0.0, duplicate model of SiliconFlow occurred. #9265

New Issue
Closed
opened 2026-02-21 18:32:35 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 18:32:35 -05:00
Owner
Copy Link
Copy Source

Originally created by @jarrett-au on GitHub (Mar 5, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

v1.0.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  • In the v0.15.3 environment: Go to "Settings" → "Model Providers" - "SiliconFlow":
    Image
  • and manually add a custom model: Set the name as "Pro/deepseek-ai/DeepSeek-R1":
    Image
  • Perform the version upgrade to v1.0.0

✔️ Expected Behavior

When the system is upgraded, it should automatically merge the existing custom model configurations with the built-in models of the new version or provide a conflict handling solution (such as a migration prompt/configuration inheritance mechanism) to ensure the uniqueness of the final model list.

❌ Actual Behavior

Image

The model of deepseek-r1 manually created in the original version 0.15.3 and the built-in model of the SiliconFlow plugin both exist simultaneously. When selecting a model in the workflow, the two model will [be enabled/disabled synchronously].

I have tried to manually delete the added model, but it didn't take effect, and the model still remains in the list.

Originally created by @jarrett-au on GitHub (Mar 5, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version v1.0.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce - In the v0.15.3 environment: Go to "Settings" → "Model Providers" - "SiliconFlow": ![Image](https://github.com/user-attachments/assets/abaf5dae-908b-4f4c-bd02-5b83fca2b9dc) - and manually add a custom model: Set the name as "Pro/deepseek-ai/DeepSeek-R1": ![Image](https://github.com/user-attachments/assets/399d3fbd-f8ea-44df-a646-f98ab0164aba) - Perform the version upgrade to v1.0.0 ### ✔️ Expected Behavior When the system is upgraded, it should automatically merge the existing custom model configurations with the built-in models of the new version or provide a conflict handling solution (such as a migration prompt/configuration inheritance mechanism) to ensure the uniqueness of the final model list. ### ❌ Actual Behavior ![Image](https://github.com/user-attachments/assets/6e46e81f-de3e-41f5-8603-d57a4d053cf7) The model of deepseek-r1 manually created in the original version 0.15.3 and the built-in model of the SiliconFlow plugin both exist simultaneously. When selecting a model in the workflow, the two model will [be enabled/disabled synchronously]. I have tried to manually delete the added model, but it didn't take effect, and the model still remains in the list.
yindo added the 🐞 bug label 2026-02-21 18:32:35 -05:00
yindo closed this issue 2026-02-21 18:32:35 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#9265
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?