-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
frequency_penalty and presence_penalty from curl request discarded #1051
Labels
bug
Something isn't working
Comments
The same goes for top_k, while top_p works properly. |
I can second that this is happening. The llama backend does load frequency_penalty from the config, but not from the request. |
same issue for me as well, anyway I could chip in to fix this ? |
blob42
added a commit
to blob42/LocalAI
that referenced
this issue
Mar 10, 2024
1 task
mudler
pushed a commit
that referenced
this issue
Mar 17, 2024
…1817) * fix request debugging, disable marshalling of context fields Signed-off-by: blob42 <contact@blob42.xyz> * merge frequency_penalty request parm with config Signed-off-by: blob42 <contact@blob42.xyz> * openai: add presence_penalty parameter Signed-off-by: blob42 <contact@blob42.xyz> --------- Signed-off-by: blob42 <contact@blob42.xyz>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
LocalAI version:
1.25.0
Environment, CPU architecture, OS, and Version:
Linux REDACTED 4.18.0-147.5.1.6.h541.eulerosv2r9.x86_64 #1 SMP Wed Aug 4 02:30:13 UTC 2021 x86_64 GNU/Linux
Describe the bug
I have frequency_penalty or presence_penalty in the body of my /chat/completions request but it ignore it. If it is unset in the model .yaml it is set to 0, otherwise it only use the .yaml one. Tested on Airoboros 70b.
For this try I have set both to 1:
The full "configuration read" log :
Parameters:
To Reproduce
Setup a model and try to change presence_penalty using body parameters
Expected behavior
Logs
Additional context
The text was updated successfully, but these errors were encountered: