Skip to content

Model does not exist about Tencent LLM - hunyuan-standard-256K #10035

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
5 tasks done
SodrSnne opened this issue Oct 30, 2024 · 1 comment · Fixed by #10052
Closed
5 tasks done

Model does not exist about Tencent LLM - hunyuan-standard-256K #10035

SodrSnne opened this issue Oct 30, 2024 · 1 comment · Fixed by #10052

Comments

@SodrSnne
Copy link

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

0.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Snipaste_2024-10-30_10-56-49

An official error was encountered while using the hunyuan-256k model, indicating that the model did not exist。

It seems to be a misspelling of uppercase and lowercase letters.

I verified the problem using the script, capitalized the "K" then it worked.

Snipaste_2024-10-30_11-03-21

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Copy link

dosubot bot commented Oct 30, 2024

@SodrSnne Hello there! I'm here to help you with bug fixes, answer questions, and guide you on becoming a contributor. If you need assistance, feel free to ask.

It seems like you've encountered a case sensitivity issue with the model name "hunyuan-standard-256k" when using the Tencent LLM in Dify. The model name should be "hunyuan-standard-256K" with an uppercase "K" to work correctly. This aligns with your observation that capitalizing the "K" resolved the issue.

For future reference, ensure that the model names are correctly capitalized as required by the API specifications to avoid similar errors. If you have any further questions or need additional assistance, feel free to ask!

To continue talking to Dosu, mention @dosu.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant