Skip to content
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

use_sequence_param_check #8615

Merged
merged 3 commits into from
Aug 30, 2024

Conversation

venkatram-dev
Copy link
Contributor

@venkatram-dev venkatram-dev commented Aug 28, 2024

Use Sequence for parameters type checking in transforms.RandomErase

Issue
#8549

cc @vfdev-5

Copy link

pytorch-bot bot commented Aug 28, 2024

🔗 Helpful Links

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

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

✅ You can merge normally! (8 Unrelated Failures)

As of commit cffb70d with merge base c10f938 (image):

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

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

Copy link
Member

@NicolasHug NicolasHug left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @venkatram-dev . The relevant CI jobs are green, so I'll land this.

@NicolasHug NicolasHug merged commit c33b00a into pytorch:main Aug 30, 2024
49 of 57 checks passed
facebook-github-bot pushed a commit that referenced this pull request Sep 2, 2024
…omErase (#8615)

Summary: Co-authored-by: Nicolas Hug <nh.nicolas.hug@gmail.com>

Reviewed By: ahmadsharif1

Differential Revision: D62032048

fbshipit-source-id: 274a8c8b5fe150103755ec84f2791b39fb3f5d60
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.

3 participants