-
Notifications
You must be signed in to change notification settings - Fork 106
fix: Event consumer should stop on input_required #566
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 @cmtoan, 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 addresses a critical issue in the event consumption mechanism where the system failed to halt event processing when a task entered an 'input required' state. By modifying the event consumer to recognize this state as a termination condition, the change ensures proper flow control and consistency with other language implementations, preventing unnecessary resource usage and potential logical errors. 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.
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 correctly implements the requirement for the EventConsumer to stop processing events when a task with the INPUT_REQUIRED state is encountered. The change is isolated and a new helper method is introduced for the logic. A corresponding unit test has been added to verify the new behavior. My review includes suggestions to improve the clarity of the new method's name and to address code duplication in the test suite for better long-term maintainability.
server-common/src/main/java/io/a2a/server/events/EventConsumer.java
Outdated
Show resolved
Hide resolved
server-common/src/main/java/io/a2a/server/events/EventConsumer.java
Outdated
Show resolved
Hide resolved
server-common/src/test/java/io/a2a/server/events/EventConsumerTest.java
Outdated
Show resolved
Hide resolved
|
There are flaky tests in QuarkusA2ARestTest. |
|
@cmtoan May you add some javadoc on your isStreamTerminatingTask to explain why INPUT_REQUIRED is terminating. |
kabir
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.
Thank you @cmtoan!
# Description Event consumer should stop on input_required task as fixed in the python version a2aproject/a2a-python#167
Description
Event consumer should stop on input_required task as fixed in the python version a2aproject/a2a-python#167