[bugfix]Add llm_call_kwargs in tb2 example#366
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds the llm_call_kwargs configuration block with max_tokens set to 4096 to the Harbor terminal benchmark task configuration and updates the corresponding English and Chinese documentation. The review feedback recommends adjusting the inline comments in these additions to ensure they are separated from the code statements by at least two spaces, adhering to PEP 8 guidelines.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| "llm_call_kwargs": { # LLM调用参数 | ||
| "max_tokens": 4096, # 最大输出token数 | ||
| # "temperature": 0.7, | ||
| # "top_p": 0.9, | ||
| # "top_k": 50, | ||
| }, |
There was a problem hiding this comment.
According to PEP 8, inline comments should be separated by at least two spaces from the statement. This also ensures consistency with the rest of the file.
| "llm_call_kwargs": { # LLM调用参数 | |
| "max_tokens": 4096, # 最大输出token数 | |
| # "temperature": 0.7, | |
| # "top_p": 0.9, | |
| # "top_k": 50, | |
| }, | |
| "llm_call_kwargs": { # LLM调用参数 | |
| "max_tokens": 4096, # 最大输出token数 | |
| # "temperature": 0.7, | |
| # "top_p": 0.9, | |
| # "top_k": 50, | |
| }, |
References
- Inline comments should be separated by at least two spaces from the statement. (link)
| "llm_call_kwargs": { # LLM call parameters | ||
| "max_tokens": 4096, # Maximum output token number | ||
| # "temperature": 0.7, | ||
| # "top_p": 0.9, | ||
| # "top_k": 50, | ||
| }, |
There was a problem hiding this comment.
According to PEP 8, inline comments should be separated by at least two spaces from the statement. This also ensures consistency with the rest of the code block.
| "llm_call_kwargs": { # LLM call parameters | |
| "max_tokens": 4096, # Maximum output token number | |
| # "temperature": 0.7, | |
| # "top_p": 0.9, | |
| # "top_k": 50, | |
| }, | |
| "llm_call_kwargs": { # LLM call parameters | |
| "max_tokens": 4096, # Maximum output token number | |
| # "temperature": 0.7, | |
| # "top_p": 0.9, | |
| # "top_k": 50, | |
| }, |
References
- Inline comments should be separated by at least two spaces from the statement. (link)
| "llm_call_kwargs": { # LLM调用参数 | ||
| "max_tokens": 4096, # 最大输出token数 | ||
| # "temperature": 0.7, | ||
| # "top_p": 0.9, | ||
| # "top_k": 50, | ||
| }, |
There was a problem hiding this comment.
According to PEP 8, inline comments should be separated by at least two spaces from the statement. This also ensures consistency with the rest of the code block.
| "llm_call_kwargs": { # LLM调用参数 | |
| "max_tokens": 4096, # 最大输出token数 | |
| # "temperature": 0.7, | |
| # "top_p": 0.9, | |
| # "top_k": 50, | |
| }, | |
| "llm_call_kwargs": { # LLM调用参数 | |
| "max_tokens": 4096, # 最大输出token数 | |
| # "temperature": 0.7, | |
| # "top_p": 0.9, | |
| # "top_k": 50, | |
| }, |
References
- Inline comments should be separated by at least two spaces from the statement. (link)
2 participants
Thanks for your contribution; we appreciate it a lot. The following instructions will make your pull request healthier and help you get feedback more easily. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
感谢您的贡献，我们非常重视。以下说明将使您的拉取请求更健康，更易于获得反馈。如果您不理解某些项目，请不要担心，只需提交拉取请求并从维护人员那里寻求帮助即可。
PR Type / PR类型
Related Issue | 关联 Issue
Fixes #(issue ID / issue 编号) / Relates to #(issue ID / issue 编号)
Fixes #322
🔍 Motivation / 变更动机
Please describe the motivation of this PR and the goal you want to achieve through this PR.
请描述您的拉取请求的动机和您希望通过此拉取请求实现的目标。
There isn't an example to explain how to set models kwargs in terminal-bench 2
📝 Modification / 修改内容
Please briefly describe what modification is made in this PR.
请简要描述此拉取请求中进行的修改。
Add example to explain how to set models kwargs in terminal-bench 2 in docs and custom cfg
📐 Associated Test Results / 关联测试结果
Please provide links to the related test results, such as CI pipelines, test reports, etc.
请提供相关测试结果的链接，例如 CI 管道、测试报告等。
Does the modification introduce changes that break the backward compatibility of the downstream repositories? If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
是否引入了会破坏下游存储库向后兼容性的更改？如果是，请描述它如何破坏兼容性，以及下游项目应该如何修改其代码以保持与此 PR 的兼容性。
If the modification introduces performance degradation, please describe the impact of the performance degradation and the expected performance improvement.
如果引入了性能下降，请描述性能下降的影响和预期的性能改进。
🌟 Use cases (Optional) / 使用案例（可选）
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
如果此拉取请求引入了新功能，最好在此处列出一些用例并更新文档。
✅ Checklist / 检查列表
Before PR:
After PR:
👥 Collaboration Info / 协作信息
🌟 Useful CI Command / 实用的CI命令
/gemini review/gemini summary/gemini help/readthedocs build