fix: ensure push notifications order#141
Conversation
Summary of ChangesHello @guglielmo-san, 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 race condition within the push notification sending logic by introducing a promise-based serialization mechanism. This ensures that notification batches are processed sequentially in a predictable FIFO order, preventing concurrency issues. The effectiveness of this solution is confirmed by an enhanced integration test that now deterministically reproduces the original race condition. 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 effectively addresses the race condition in SendPushNotification by serializing notification batches using a promise chain. The changes to the integration test, which introduce a delay to deterministically trigger the race condition, are a great way to validate the fix. My review includes a suggestion to make the promise chain more resilient to potential errors, preventing the entire notification mechanism from halting. I've also recommended an improvement to the test assertions to make them clearer and more explicit about verifying the correct order of notifications.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
ishymko
left a comment
There was a problem hiding this comment.
Let's reference failed test runs from Actions as an example in the PR description.
Co-authored-by: Ivan Shymko <vana.shimko@gmail.com>
🤖 I have created a release *beep* *boop* --- ## [0.3.5](v0.3.4...v0.3.5) (2025-11-05) ### Bug Fixes * cancel/task now returns the expected 'cancelled' task status ([#158](#158)) ([3eec0bd](3eec0bd)) * correct the default value in the agentCardPath comment ([#130](#130)) ([3279c7b](3279c7b)) * enable follow up task issue on non blocking request ([#160](#160)) ([352dc05](352dc05)) * ensure push notifications order ([#141](#141)) ([22360e6](22360e6)) * ensure user messages are added to existing tasks ([#138](#138)) ([00fb916](00fb916)) * validate JSON-RPC params ([#155](#155)) ([5b39f4d](5b39f4d)) * validate JSON-RPC request id according to the spec ([#152](#152)) ([9558c36](9558c36)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Description
This PR introduces a promise chain (
this.notificationChain) to serialize the batches of notifications. This ensures that only one batch at a time is processed, in a predictable First-In, First-Out (FIFO) order. The test was already ensuring it and it caused some flakiness before, examples:The
push_notification_integration.spec.tstest file has been modified to simulate a more deterministic delay (100ms) on the completion of the first received notification. This guarantee a 100% test failure when the notification serialization is not implemented.Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
CONTRIBUTINGGuide.fix:which represents bug fixes, and correlates to a SemVer patch.feat:represents a new feature, and correlates to a SemVer minor.feat!:, orfix!:,refactor!:, etc., which represent a breaking change (indicated by the!) and will result in a SemVer major.Fixes #140 🦕