Mock datetime to fix python unit tests for the new year

[clincoln8]

Fix Date-Dependent Test: Patched datetime for test_fetch_highest_coverage_with_entities_single_variable in server/tests/lib/util_test.py to freeze the date to 2025-01-01. This ensures 2021 test data remains within the 5-year "recent" window check, preventing data age-out failures.

• The test started returning 2022 in recent PR runs (example) because 2021 is now excluded by the "within 5yr" date filtering logic, and 2022 was the next best date available in the dataset (supported by USA and Mexico).

[gemini-code-assist]

Summary of Changes

Hello @clincoln8, 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 resolves a failing unit test in server/tests/lib/util_test.py that became unstable due to the passage of time. By introducing a mock for the datetime module, the test now consistently perceives the current date as January 1, 2025, ensuring that its 2021 test data remains within a critical 5-year "recent" window, thus preventing future age-out failures.

Highlights

• Test Stability: Addresses a unit test that was failing due to date-dependent logic, ensuring its stability against the passage of time.
• Date Mocking: Implements datetime mocking within the affected test to control the perceived current date.
• Data Validity: Freezes the test date to 2025-01-01, ensuring that 2021 test data remains within a 5-year 'recent' window and preventing future age-out failures.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 fixes a date-dependent unit test by mocking datetime.date.today() to a fixed date, ensuring the test remains stable over time. The approach is correct. I've added one suggestion to improve consistency with other tests in the same file by patching datetime.date more specifically.

[clincoln8]

/gemini review

[gemini-code-assist]

Code Review

This pull request correctly fixes a date-dependent unit test by mocking datetime. The change is well-implemented and includes a clear comment explaining the purpose of the mock. Additionally, another test was updated for consistency, which is a good practice. I've added a couple of suggestions to reorder the @patch decorators to improve code readability and maintainability by making the order of mock arguments in the function signature match the visual order of the decorators.