Skip to content
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

Autogen llm_config error #1863

Closed
doanaktar opened this issue Mar 5, 2024 · 7 comments · Fixed by #1946
Closed

Autogen llm_config error #1863

doanaktar opened this issue Mar 5, 2024 · 7 comments · Fixed by #1946
Labels
models Pertains to using alternate, non-GPT, models (e.g., local models, llama, etc.)

Comments

@doanaktar
Copy link

doanaktar commented Mar 5, 2024

Hi, when my version is pyautogen==0.2.16 Autogen gives this error:

ValueError: Please either set llm_config to False, or specify a non-empty 'model' either in 'llm_config' or in each config of 'config_list'.

But when i switch to the pyautogen==0.2.2 version. It does not gives any error.

This is my llm_config:

{'config_list': 
        [{
        'base_url': 'http://0.0.0.0:8053',
        'api_key': 'NULL'
    }],
    'cache_seed': 25}

And litellm runs on that port without any issues.

@qingyun-wu
Copy link
Contributor

There are some updates in the required format of config_list. Could you set llm_config to False, or specify a non-empty 'model' either in 'llm_config' or in each config of 'config_list' as suggested in the error message if you are using 0.2.16? Thank you!

@jackgerrits
Copy link
Member

If I am interpreting this correctly it seems that litellm does not need a model arg to work? So perhaps requiring this is too heavy handed?

@sonichi
Copy link
Contributor

sonichi commented Mar 10, 2024

@jackgerrits good point. I'm OK with removing the check in ConversableAgent. @gunnarku what do you think?

@sonichi sonichi added llm models Pertains to using alternate, non-GPT, models (e.g., local models, llama, etc.) labels Mar 10, 2024
@ekzhu
Copy link
Collaborator

ekzhu commented Mar 10, 2024

Looping in @olgavrou

@gunnarku
Copy link
Contributor

The dilemma is between breaking the backward compatibility and more robust validation for preconditions (and I admit that I am biased towards more formality ;-)).

If we remove the checking for the presence of the model attribute, we'll regress to the state described in #1522 (the root cause for #1654).

If it's the only known case of overly aggressive validation, then modifying the configuration by the user is an obvious fix.

Issuing a warning message is a middle-ground solution.

However, @@jackgerrits and @sonichi, this is your show - do what's right for AutoGen customers ;-)

@sonichi
Copy link
Contributor

sonichi commented Mar 10, 2024

I tried to find a solution to accommodate both requirements in #1946

@olgavrou
Copy link
Member

Looping in @olgavrou

custom models also don't necessarily need the model to be set

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
models Pertains to using alternate, non-GPT, models (e.g., local models, llama, etc.)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants