feat: task cancellation

[mkorobovv]

Added: OnGetTask implementation
Added: OnCancelTask implementation
Added: Tests for implementations

The PR implements OnGetTask and OnCancelTask. OnGetTask and OnCancelTask use TaskStore to manage task states. OnCancelTask check Task.Status.State with Terminal function to cancel the tasks not in terminal state.

re #21

[gemini-code-assist]

Summary of Changes

Hello @mkorobovv, I'm Gemini Code Assist¹! 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 significantly enhances the task management capabilities by introducing robust implementations for retrieving and canceling tasks. The OnGetTask method now provides flexible access to task data, including its history, while OnCancelTask ensures that tasks can be properly terminated, with safeguards against canceling already completed tasks. These additions are supported by a comprehensive suite of unit tests, ensuring reliability and correctness. Minor API method name adjustments were also made for improved clarity.

Highlights

• Task Retrieval Implementation: The OnGetTask method has been fully implemented to retrieve task details from the TaskStore, including support for limiting the historical messages returned based on a HistoryLength parameter.
• Task Cancellation Implementation: The OnCancelTask method has been implemented, allowing tasks to be canceled. It includes checks to prevent cancellation of tasks already in a terminal state and interacts with the queueManager and executor to process the cancellation.
• Comprehensive Unit Tests: Extensive unit tests have been added for both OnGetTask and OnCancelTask, covering various success paths, edge cases (like history length limits), and error conditions (e.g., missing IDs, store failures, terminal states).
• API Method Renaming: Several methods related to task push notification configuration have been renamed for brevity, changing On*TaskPushNotificationConfig to On*TaskPushConfig.

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

1. 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. ↩

[gemini-code-assist]

Code Review

This pull request successfully implements the OnGetTask and OnCancelTask handlers, including comprehensive test coverage for various scenarios. The overall implementation is solid. My feedback includes a few suggestions to improve code clarity, efficiency, and test assertions by leveraging standard Go practices and libraries.

[mkorobovv]

@yarolegovich