test(resilience): add comprehensive tests for RetryHandler

[JuanCS-Dev]

Added comprehensive unit tests for RetryHandler in vertice_core.resilience. The tests cover:

• Exponential backoff and jitter calculation.
• Error classification (Transient, Permanent, RateLimit).
• Retry decision logic (should_retry).
• execute wrapper behavior (success, retry, failure).
• @retry decorator.
• Retry-After header support.

Also addressed a deprecation warning by replacing datetime.utcnow() with datetime.now(timezone.utc) in vertice_core.resilience.types.

---

PR created automatically by Jules for task 17868078270976339522 started by @JuanCS-Dev

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[gemini-code-assist]

Summary of Changes

Hello @JuanCS-Dev, 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 robustness of the RetryHandler component by introducing a comprehensive suite of unit tests. These tests validate the core retry mechanisms, including error classification, backoff strategies, and the integration of the @retry decorator, ensuring reliable operation under various failure conditions. Additionally, it includes a minor update to use timezone-aware datetime objects, resolving a deprecation warning.

Highlights

• Comprehensive Test Coverage: Added extensive unit tests for the RetryHandler component, ensuring its reliability across various scenarios.
• Retry Logic Validation: Verified exponential backoff, jitter calculation, error classification (Transient, Permanent, RateLimit), and the core retry decision logic.
• Execution Wrapper and Decorator Testing: Tested the behavior of the execute wrapper for success, retry, and failure cases, as well as the functionality of the @retry decorator.
• Retry-After Header Support: Confirmed correct handling and respect for the Retry-After header in rate-limiting scenarios.
• Deprecation Warning Fix: Addressed a datetime.utcnow() deprecation by replacing it with datetime.now(timezone.utc) for timezone-aware timestamps.

Changelog

• packages/vertice-core/src/vertice_core/resilience/types.py
  • Replaced datetime.utcnow() with datetime.now(timezone.utc) to use timezone-aware datetimes and address a deprecation warning.
• tests/unit/core/resilience/test_retry.py
  • Added a new test file containing extensive tests for RetryHandler functionality, covering error classification, backoff, retry logic, and decorator functionality.

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 comprehensive suite of unit tests for the RetryHandler and correctly addresses the deprecation of datetime.utcnow(). No vulnerabilities were found in the provided changes. I suggest cleaning up unused imports in the new test file and adding an edge-case test for max_retries=0 to further enhance test coverage.

[gemini-code-assist]

There are a couple of unused imports here. Mock from unittest.mock and the time module are not used in this file. They can be removed to keep the import section clean.

Suggested change

	from unittest.mock import Mock, AsyncMock, patch
	import time
	from unittest.mock import AsyncMock, patch

[gemini-code-assist]

This is a great set of tests! To improve coverage of edge cases, consider adding a test to verify the behavior when max_retries is set to 0. The handler should not perform any retries in this case. You could add a test like the following to the TestRetryHandler class:

    @pytest.mark.asyncio
    async def test_execute_no_retries_on_config(self):
        """Should not retry if max_retries is 0."""
        config = RetryConfig(max_retries=0)
        handler = RetryHandler(config=config)
        mock_func = AsyncMock(side_effect=TimeoutError("Failure"))

        with pytest.raises(TimeoutError):
            await handler.execute(mock_func)

        assert mock_func.call_count == 1
        assert handler.get_stats()["failures"] == 1
        assert handler.get_stats()["retries"] == 0