-
Notifications
You must be signed in to change notification settings - Fork 41
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
Making use of Proxy for the prompt optimization #6
Comments
Could you test again on verson 0.0.7? Thank you! 🙏 |
{
"name": "Test",
"dataset": "tweet-optim",
"description": "test task",
"evaluators": "./task.py:evaluators",
"evaluator_descriptions": {
"my_example_criterion": "CHANGEME: This is a description of what the example criterion is testing. It is provided to the metaprompt to improve how it responds to different results."
},
"optimizer": {
"model": {
"model": "qwen2.5-72b-instruct",
"base_url": "https://dashscope.aliyuncs.com/compatible-mode/v1",
"model_provider": "openai"
}
},
"initial_prompt": {
"identifier": "tweet-generator-example-with-nothing"
},
"$schema": "https://raw.githubusercontent.com/hinthornw/promptimizer/refs/heads/main/config-schema.json"
} File "C:\Users\23939.conda\envs\3.12\Lib\site-packages\openai_base_client.py", line 1634, in _request |
Its seems like nothing change after upgrading, it keeps looking for the API-KEY for the regular openai client. raise OpenAIError( |
Hey.
I'm trying to use the promptim optimization with azure client.
Its seems like configuring for doing so isn't do much (it keeps ask for the regular OPENAPI_KEY)
Is the use of an OpenAI (or Claude) proxy implemented yet, or is there a problem with my configuration?
part of my config file:
"optimizer": {
"model": {
"model": "gpt4o",
"model_provider": "azure_openai",
"max_tokens_to_sample": 8192,
"configurable_fields": "any",
"api_key": "db64482d5b7d-------------1",
"deployment_name": "gpt-4o",
"api_version": "2024-08-01-preview",
"base_url": "https://----------------.openai.azure.com"
}
}
Thanks
The text was updated successfully, but these errors were encountered: