-
Notifications
You must be signed in to change notification settings - Fork 117
enh: The addition of the think closure tag supports multi-turn thin…
#267
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
Conversation
Summary of ChangesHello @leslie2046, 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 refines the 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 enhances the logic for wrapping reasoning content by ensuring that the <think> tag is always properly closed with </think>. This fixes a potential bug in multi-turn thinking scenarios where the closing tag could be missed. The change is correct, and I've added one suggestion to refactor the new logic for improved clarity and conciseness.
| if is_reasoning: | ||
| is_reasoning = False | ||
| if not reasoning_content: | ||
| output = "\n</think>" | ||
| if content: | ||
| output += content | ||
|
|
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.
The logic for handling the end of a reasoning block can be simplified for better readability and conciseness. The check if not reasoning_content: is redundant because this code is inside the else block of if reasoning_content:, where reasoning_content is guaranteed to be falsy. Additionally, the output string construction can be simplified into a single line.
if is_reasoning:
is_reasoning = False
output = "\n</think>" + contentthink closure tag supports multi-turn thin…think closure tag supports multi-turn thin…
|
Would you mind add some tests for the changes? |
Fine,I will add some tests tomorrow. |
provider:DeepSeek
|
provider:siliconflow
|
provider:volcengine_maas
|
|
@Yeuoly cc |
Yeuoly
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
…king scenarios.
ref langgenius/dify-official-plugins#2195
Pull Request Checklist
Thank you for your contribution! Before submitting your PR, please make sure you have completed the following checks:
Compatibility Check
README.mdREADME.mdREADME.mdREADME.mdAvailable Checks