fix: Store push notification config for newly created tasks#483
fix: Store push notification config for newly created tasks#483kabir merged 2 commits intoa2aproject:mainfrom
Conversation
This was missing in the non-streaming message sends
Summary of ChangesHello @kabir, 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 gap in the system's handling of push notification configurations for tasks initiated through non-streaming message sends. By introducing the necessary logic to store these configurations upon task creation, it ensures consistent behavior across different message sending mechanisms and resolves a previously identified bug, enhancing the reliability of push notification delivery. 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 fixes an issue where push notification configurations were not stored for newly created tasks in non-streaming message sends. The change adds logic to onMessageSend to handle this case, mirroring the existing logic for streaming sends. Additionally, new tests are added to verify the fix for new tasks and to ensure no regressions for existing tasks.
My review includes a couple of suggestions. First, in DefaultRequestHandler.java, I recommend making the condition for storing the push config more specific to new tasks to avoid redundant operations. Second, in DefaultRequestHandlerTest.java, I suggest making a test assertion stricter for better correctness guarantees. Overall, the changes are good and the tests are comprehensive.
server-common/src/main/java/io/a2a/server/requesthandlers/DefaultRequestHandler.java
Outdated
Show resolved
Hide resolved
server-common/src/test/java/io/a2a/server/requesthandlers/DefaultRequestHandlerTest.java
Outdated
Show resolved
Hide resolved
…ct#483) This was missing in the non-streaming message sends Follows up on a2aproject#383 and a2aproject#482 The TCK is not testing this, but it is introduced in a2aproject/a2a-tck#94
This was missing in the non-streaming message sends
Follows up on #383 and #482
The TCK is not testing this, but it is introduced in a2aproject/a2a-tck#94