-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
backend start problem #1472
Comments
That is just a warning, and it doesn't affect running the app. It showed up recently again, from a dependency, litellm, when we updated it. I'm sure it will vanish soon. |
you can upgrade your litellm version to solve it Like: pip install litellm==1.35.31
# or just
pip install litellm --upgrade |
It seems like this problem has returned, even in newer versions of LiteLLM |
Hi Guys I installed this today I am running MAC M1 Ultra with Sonoma 14.2.1 and managed to get all the steps done, I then had an issue with
I resolved that by running conda install onnxruntime -c conda-forge When running the server I get
any pointers greatly appreciated |
@jimthedj65 can you open a new Going to close this one since it's just a warning |
when i start backend :
/home/naladog/.cache/pypoetry/virtualenvs/opendevin-gp-JtEgx-py3.11/lib/python3.11/site-packages/pydantic/_internal/fields.py:160: UserWarning: Field "model_name" has conflict with protected namespace "model".
You may be able to resolve this warning by setting
model_config['protected_namespaces'] = ()
.warnings.warn(
/home/naladog/.cache/pypoetry/virtualenvs/opendevin-gp-JtEgx-py3.11/lib/python3.11/site-packages/pydantic/_internal/fields.py:160: UserWarning: Field "model_info" has conflict with protected namespace "model".
You may be able to resolve this warning by setting
model_config['protected_namespaces'] = ()
.warnings.warn(
The text was updated successfully, but these errors were encountered: