-
Notifications
You must be signed in to change notification settings - Fork 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
fix: missing key name when running with ollama provider #1638
Conversation
This is a review from a crew. I'm testing a crew for PRs, so if it sounds weird that is the reason, you are one of the first ones to see this. :) I'll try to personally look into it as well OverviewThis Pull Request introduces significant improvements to Specific Code Improvements Suggested
Historical ContextAlthough specific related PRs could not be retrieved for further insights, earlier pull requests (#1567, #1552, #1535, #1514, #1512) have previously addressed key areas relevant to agent functionality and environment variable management. Monitoring trends from these past changes can enhance understanding of ongoing improvements and issues relevant to this file. ConclusionThe changes made in PR #1638 represent positive steps towards robust environment variable management within the |
Hi @joaomdmoura, thanks for reviewing this PR. With this PR patched, it successfully runing with |
520a9c2
to
dcf03ea
Compare
Would you like to have a further review of this fix, before releasing the new version? |
Great fix @bowenliang123!! Thank you! |
Move the existance in
unnacepted_attributes
after ensuring key name not null, to fix the error when running with model providerollama
:The root cause is the line 160 of
crewai/agent.py
where it's getting value from env_var by attribute name ,But ENV_VARS in
crewai/cli/constants.py
forollama
does not has a attribute name ofkey_name
,