Skip to content

Fix #9051: Add integer dtype check to RandomPosterize #9052

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

ion-linti
Copy link

This PR adds a helper function _ensure_integer_dtype that uses torch.iinfo to validate that inputs to RandomPosterize are integer‐typed. In RandomPosterize.transform we now call this helper to raise a clear TypeError when passed float, bool, or complex tensors.

Additionally, two new pytest cases have been added:

  • test_random_posterize_dtype_error verifies that non-integer dtypes (float32, bool, complex64) trigger the expected error message.
  • test_random_posterize_uint8_pass confirms that a uint8 tensor is processed without error and retains its dtype.

ion-linti added 2 commits May 2, 2025 16:10
– Introduce helper _ensure_integer_dtype to validate tensor.dtype via torch.iinfo  
– Call this helper in RandomPosterize.transform to raise TypeError on non-integer dtypes
– Test that RandomPosterize(bits=3, p=1.0) raises TypeError on float32, bool, complex64  
  with message “Number of value bits is only defined for integer dtypes”  
– Test that RandomPosterize(bits=4, p=1.0) successfully processes a uint8 tensor
Copy link

pytorch-bot bot commented May 2, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/vision/9052

Note: Links to docs will display an error until the docs builds have been completed.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@facebook-github-bot
Copy link

Hi @ion-linti!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

@ion-linti
Copy link
Author

I have signed the CLA.

@facebook-github-bot
Copy link

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@ion-linti
Copy link
Author

Hi! Waiting for your feedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants