-
Notifications
You must be signed in to change notification settings - Fork 257
[Bug Fix] Fix Camel example training code parameter passing issue #750
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
base: main
Are you sure you want to change the base?
Conversation
…eout parameter to CamelAgent
Summary of ChangesHello @HwVanICI, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request resolves critical bugs within the Camel example training code by refining how agent configuration parameters, specifically Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request aims to fix parameter passing for max_tokens and step_timeout in the Camel example. The changes correctly remove the unsupported token_limit parameter and pass max_tokens via the model_config_dict. However, I've found a critical issue where an incorrect attribute name is used to fetch the request timeout, which would cause a runtime error. I've provided a suggestion to fix this. Once that's addressed, the PR should be good to go.
| rollout_engine_request_timeout = client.engine.config.rollout_engine_request_timeout | ||
|
|
||
| messages = data["messages"].copy() | ||
| agent = ChatAgent( | ||
| model=AReaLOpenAICompatibleModel( | ||
| openai_client=client, tokenizer=self.tokenizer, model_type="areal" | ||
| openai_client=client, tokenizer=self.tokenizer, model_type="areal", | ||
| model_config_dict=model_config_dict | ||
| ), | ||
| token_limit=self.max_total_tokens, | ||
| step_timeout=rollout_engine_request_timeout |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It appears there's a typo in the attribute name used to fetch the request timeout. Based on the InferenceEngineConfig dataclass defined in areal/api/cli_args.py, the correct attribute is request_timeout, not rollout_engine_request_timeout. This will cause an AttributeError at runtime.
I've suggested a fix that uses the correct attribute and also renames the local variable for better clarity, as it's passed directly to step_timeout.
| rollout_engine_request_timeout = client.engine.config.rollout_engine_request_timeout | |
| messages = data["messages"].copy() | |
| agent = ChatAgent( | |
| model=AReaLOpenAICompatibleModel( | |
| openai_client=client, tokenizer=self.tokenizer, model_type="areal" | |
| openai_client=client, tokenizer=self.tokenizer, model_type="areal", | |
| model_config_dict=model_config_dict | |
| ), | |
| token_limit=self.max_total_tokens, | |
| step_timeout=rollout_engine_request_timeout | |
| step_timeout = client.engine.config.request_timeout | |
| messages = data["messages"].copy() | |
| agent = ChatAgent( | |
| model=AReaLOpenAICompatibleModel( | |
| openai_client=client, tokenizer=self.tokenizer, model_type="areal", | |
| model_config_dict=model_config_dict | |
| ), | |
| step_timeout=step_timeout |
garrett4wade
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but the code should be formatted with pre-commit. See CONTRIBUTING.md for instructions.
|
Please respect gemini's comment as well. |
|
Thank you for your feedback. |
Description
This PR fixes bugs of the Camel example training code. In the run_agent() function of CamelMathAgent class is updated to pass the max_tokens and step_timeout parameter properly as follows.
Related Issue
Fixes #(issue)
Type of Change
work as expected)
Checklist
jb build docs/gemini review)Need help? Check the Contributing Guide or ask in
GitHub Discussions!