Implement subscribe rounds implementation

[niteshbalusu11]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @niteshbalusu11, 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 integrates the application with an external Ark server by implementing a new client that subscribes to Ark round events. This integration allows the system to react dynamically to the start of new Ark rounds, triggering necessary maintenance tasks in real-time rather than on a fixed schedule. Additionally, the changes include a comprehensive update of Rust dependencies and an optimization to the push notification delivery system.

Highlights

• New Ark Server Client: A new Rust client module (ark_client.rs) has been added to establish gRPC communication with an external Ark server. This client handles handshakes, retrieves server information, and subscribes to real-time round events.
• Event-Driven Maintenance Task: The application's maintenance task has been refactored from a fixed cron schedule to an event-driven model. It is now triggered immediately upon the detection of a new round starting on the Ark server, ensuring more responsive operations.
• Consolidated Dependency Management and Updates: The project's dependency management has been streamlined by removing the server/Cargo.lock file and consolidating all dependencies into the root Cargo.lock. This involved significant updates to numerous Rust crates, including new additions like bark-server-rpc and various lightning-related libraries.
• Optimized Push Notification Delivery: The push notification sending mechanism has been enhanced to process notifications in concurrent chunks of 100. This optimization improves the overall performance and reliability of delivering notifications.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 implements a client to subscribe to round events from an Ark server, which now triggers the maintenance task, replacing the previous cron-based approach. This is a significant architectural change that involves adding new dependencies and modifying the application's startup logic. Additionally, the push notification sending logic has been refactored to handle recipients in chunks, which is a good improvement. However, I've identified a critical issue in the new push notification code that could cause the service to panic due to the use of .unwrap(). I've also pointed out a high-severity reliability concern with the new Ark client, as it lacks reconnection logic. Please address these points to improve the robustness of the application.