wenxin's penalty_score range is incorrect
Self Checks
- [X] This is only for bug report, if you would like to ask a question, please head to Discussions.
- [X] I have searched for existing issues search for existing issues, including closed ones.
- [X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
- [X] Please do not modify this template :) and fill in all the required fields.
Dify version
0.6.8
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
@XiaoLey 你好! 我是Dosu,一个可以帮助您解决问题、回答疑问并成为贡献者的机器人。我会在等待人类维护者的期间帮助您。
The allowed range for the "penalty_score" parameter should be between 1.0 and 2.0. The user interface component ParameterItem enforces this range through the Slider and input elements, which use the min and max properties from the parameterRule object to set the allowed range [1].
To address the issue, ensure that the penalty_score parameter is set within the correct range in the configuration file or user interface. If the current value is outside this range, adjust it accordingly. If the issue persists, verify that the configuration file or environment variables are correctly set and that the service has been restarted to apply the changes.
Details
About Dosu This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.
Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.
To continue the conversation, mention @dosu.
Which one do you use.
https://github.com/langgenius/dify/blob/5becb4c43a42eb967801f42bb98a1882d76fa505/api/core/model_runtime/model_providers/wenxin/llm/ernie-speed-appbuilder.yaml#L21
You could check out this. And you can open a pr for this. :)
Which one do you use.
https://github.com/langgenius/dify/blob/5becb4c43a42eb967801f42bb98a1882d76fa505/api/core/model_runtime/model_providers/wenxin/llm/ernie-speed-appbuilder.yaml#L21
You could check out this. And you can open a pr for this. :)
Okay, I will conduct individual tests when I have time and provide the correct range values. I might make a pull request sometime this week.