-
Notifications
You must be signed in to change notification settings - Fork 1.9k
fix #2404: branching and include_contents='none' #2961
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
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.
Summary of Changes
Hello @ananyablonko, 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 a critical bug affecting agents configured with include_contents='none'
when operating within branched conversational structures. Previously, the event filtering logic could incorrectly pull context from unrelated branches, leading to agents failing to receive necessary prompts. The changes introduce a more precise event filtering mechanism that prioritizes the agent's current branch, ensuring that conversational context is accurately maintained and agents behave as expected in complex, multi-threaded interactions.
Highlights
- Fix for
include_contents='none'
in branched agents: Addressed a bug where agents configured withinclude_contents='none'
within a branched conversation structure (e.g.,ParallelAgent
withSequentialAgent
sub-agents) were not consistently receiving their expected prompts. The issue stemmed from the event filtering logic incorrectly identifying the 'most recent other-agent/user event' across all branches, rather than strictly within the agent's specific branch. - Refactored event filtering logic: The event processing mechanism has been refactored to first filter events by the agent's current branch before determining the latest relevant event. This ensures accurate context retrieval and reliable agent behavior in complex, multi-branched conversational flows, particularly when
include_contents='none'
is used. - Added new test case for multi-branch scenarios: A new test,
test_include_contents_none_multi_branch_current_turn
, has been introduced to validate the corrected behavior ofinclude_contents='none'
in multi-branch agent setups. This test specifically simulates aParallelAgent
scenario to confirm that sub-agents correctly receive context from their own branch.
Using Gemini Code Assist
The 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 /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands on the current page.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in pull request comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
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 .gemini/
folder in the base of the repository. Detailed instructions can be found here.
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
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
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 addresses a bug related to context inclusion for agents with include_contents='none'
in multi-branch scenarios. The fix correctly ensures that events are filtered by branch before determining the current turn's starting point, preventing race conditions where an event from another branch could be incorrectly selected. The change introduces a new helper function, _should_include_event_in_context
, to centralize event filtering logic, which improves code clarity. A corresponding unit test has been added to validate the fix in a multi-branch environment. My feedback focuses on further improving the readability and documentation of the new helper function.
Consider code where a sub_agent somewhere under a ParallelAgent has include_contents='none'.
The log here will often have one or more
subagent_{i}_2
not receive their prompts fromsubagent_{i}_1
.This inconsistency is caused by the way
include_contents='none'
is implemented in flows/llm_flows/contents.py:328-356:That is, we first find the most recent (other-agent / user) event, even if it's not on our branch, and then filter the remainder. Thus in the above example, we may sometimes filter out all events, when we expect to have the event of a previous agent in a
SequentialAgent
.The solution is to first filter events by branch, and only then search for the latest.
TEST SUMMARY: