Release/v1.5.1

[HYLcool]

As the title says. And fix some bugs.

[gemini-code-assist]

Summary of Changes

Hello, 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 primarily updates the project's version, refactors OpenCV dependencies to use opencv-contrib-python, and includes specific fixes and dependency management for video processing functionalities. It also addresses potential issues with test stability by skipping a test case.

Highlights

• Version Update: Incremented the version number from 1.5.0 to 1.5.1.
• Dependency Update: Switched the OpenCV dependency from opencv-python to opencv-contrib-python across multiple modules.
• Tensorflow Version Pinning: Pinned the tensorflow version to 2.20.0 in two mappers.
• OpenCV Package Management: The video_undistort_mapper now checks and manages OpenCV package installations, ensuring only opencv-contrib-python is installed and fixing numpy version issues.
• Test Skipping: Skipped the RayTracerTest due to possible non-finalized results.

🧠 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.

Changelog

• Bug Fixes
  • Addressed OpenCV version conflicts and numpy version issues in video_undistort_mapper.
• Dependency Updates
  • Replaced opencv-python with opencv-contrib-python.
  • Pinned tensorflow version to 2.20.0.
• Test Modifications
  • Skipped RayTracerTest due to non-finalized results.

Activity

• Version number updated.
• OpenCV dependency switched to opencv-contrib-python in multiple files.
• TensorFlow version pinned to 2.20.0 in relevant files.
• OpenCV package management logic added to video_undistort_mapper.
• RayTracerTest skipped.

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 prepares for release v1.5.1. It includes a version bump, several bug fixes, and dependency updates. The main change is switching the OpenCV dependency from opencv-python to opencv-contrib-python across the codebase to ensure consistency and fix related issues. Some tests have also been refactored for better maintainability. My review focuses on a few critical issues with dependency pinning and a suggestion for more robust environment checking.