fix: rearrange events sort causing message disorder#637
fix: rearrange events sort causing message disorder#637yuhao101 wants to merge 1 commit intogoogle:release/0.4from
Conversation
…dding duplicate FR event in some case
Summary of ChangesHello @yuhao101, 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 change focuses on improving the stability and correctness of conversation history management within the Highlights
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.
Code Review
This pull request addresses a bug causing message disorder by preventing duplicate function response events in the event history. The fix correctly identifies and skips these events when they are not associated with a function call. My review includes a suggestion to simplify the implementation for better readability and conciseness.
|
Hi maintainers, this PR is ready for review. Could someone help approve the workflow? Thanks! |
|
I ran into a similar problem when using long running tools - have made a slightly different fix here #682 which seems to also address your case. |
This PR addresses an issue identified in the adk-java v0.4.0 release version. #632