fix: skip invalid updates

[vlopes11]

The beacon API will generate a plethora of invalid updates. Prior to this commit, only the ones who generated a void change would be updated. This commit however preserves the sanity check of the set of selected updates.

[gemini-code-assist]

Summary of Changes

Hello @vlopes11, 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 focuses on enhancing the robustness of the light client service by refining how it processes updates from the beacon API. It introduces a more resilient mechanism to skip invalid updates, ensuring that the system continues to operate smoothly without being hindered by malformed or irrelevant data. Complementing this functional improvement, the PR also includes a substantial update to the project's dependency tree, bringing many crates to their latest versions and incorporating new ones, which collectively contribute to a more modern and stable codebase.

Highlights

• Improved Invalid Update Handling: The light client service now gracefully skips invalid updates received from the beacon API, preventing disruptions to the update history and simplifying error management.
• Comprehensive Dependency Updates: Numerous project dependencies have been updated, including significant version bumps for core crates like indexmap, serde, toml, and various windows-sys related packages, enhancing overall stability and leveraging newer features.
• Refactored Error Logic: The error handling mechanism for beacon API updates in the light client service has been streamlined, replacing complex conditional error logging and history discarding with a unified debug log for all skipped invalid updates.

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 introduces a significant improvement to the service's resilience by changing how it handles invalid beacon API updates. Instead of treating them as critical errors that would cause the service to discard its state and pause, they are now gracefully skipped with a debug log message. This makes the service more robust against the 'plethora of invalid updates' from the beacon API as described. The change also removes a fragile string-based error match, improving maintainability. Additionally, numerous dependencies have been updated in Cargo.lock, which is good for keeping the project up-to-date with the latest fixes and features from upstream crates. I've added one suggestion to refactor the update filtering logic to be more idiomatic and efficient.