Fix: correct effective crop_to_aspect_ratio logic and lint issues #21779
Conversation
…andling and tests
Summary of ChangesHello @utsab345, I'm Gemini Code Assist1! 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 refines the image resizing and saving functionalities within the Keras utilities. The primary focus is on fixing a subtle bug in the Highlights
Using Gemini Code AssistThe 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
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 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
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request correctly refactors the crop_to_aspect_ratio logic in the Resizing layer to only trigger when aspect ratios differ, and also includes some linting fixes. My review focuses on improving robustness. I've suggested adding a check to prevent a potential ZeroDivisionError in resizing.py and fixing a bug in image_utils.py where a warning for RGBA to RGB conversion for JPEG images was missed when the file format was inferred from the path.
| source_aspect_ratio = input_width / input_height | ||
| target_aspect_ratio = self.width / self.height |
There was a problem hiding this comment.
To prevent a potential ZeroDivisionError if input_height or self.height is zero, it's safer to add a small epsilon to the denominators. This is a good defensive practice, especially since these values could be dynamic tensors.
| source_aspect_ratio = input_width / input_height | |
| target_aspect_ratio = self.width / self.height | |
| source_aspect_ratio = input_width / (input_height + self.backend.epsilon()) | |
| target_aspect_ratio = self.width / (self.height + self.backend.epsilon()) |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #21779 +/- ##
=======================================
Coverage 82.63% 82.64%
=======================================
Files 577 577
Lines 59249 59254 +5
Branches 9291 9291
=======================================
+ Hits 48963 48968 +5
Misses 7903 7903
Partials 2383 2383
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Just to make sure I understand the context of this.
Is this an optimization? Is the Or is this an actual bug fix, i.e. the image are cropped incorrectly right now? |
4 participants
PR Description
This PR fixes the logic controlling crop_to_aspect_ratio inside transform_images() in the Resizing layer.
Summary of changes:
Ensures cropping only occurs when aspect ratios differ.
Adds a small epsilon (1e-6) for floating-point comparisons.
Fixes Ruff E501 long line comment warnings.
Verified that test_crop_to_aspect_ratio_no_op_when_aspects_match passes, confirming functional parity.
Related issue:
Fixes #21773