Add missing bracket

[CptCaptain]

I've added a missing bracket to the docstring.

However, I was actually looking for the docs for this page, where it says in the parameters:
float (contrast tuple of) – How much to jitter contrast. contrast_factor is chosen uniformly from [min, max]. Should be non-negative numbers.
Obviously, there has been a mix-up.

I haven't been able to find the source for that page, maybe someone here knows how (or rather, where) to fix that.

cc @vfdev-5

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 1 New Failure, 8 Unrelated Failures

As of commit 13d8699 with merge base 9fa5f3f ():

NEW FAILURE - The following job has failed:

• Tests / unittests-macos (3.9, macos-12) / macos-job (gh)

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

• Tests / unittests-linux (3.9, linux.12xlarge, cpu) / linux-job (gh)
• Tests / unittests-macos (3.10, macos-12) / macos-job (gh)
• Tests / unittests-macos (3.8, macos-m1-12) / macos-job (gh)
• Tests / unittests-windows (3.10, windows.4xlarge, cpu) / windows-job (gh)
• Tests / unittests-windows (3.11, windows.4xlarge, cpu) / windows-job (gh)
• Tests / unittests-windows (3.8, windows.4xlarge, cpu) / windows-job (gh)
• Tests / unittests-windows (3.9, windows.4xlarge, cpu) / windows-job (gh)

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

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

• Tests / unittests-linux (3.8, linux.12xlarge, cpu) / linux-job (gh)

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

[facebook-github-bot]

Hi @CptCaptain!

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!

[NicolasHug]

Thank you @CptCaptain

[NicolasHug]

I haven't been able to find the source for that page, maybe someone here knows how (or rather, where) to fix that.

The file you updated in this PR is the relevant one. I think sphinx was failing to parse the docs properly due to the missing parenthesis you added, but now everything will properly be fine - we'll be able to confirm soon when the docs finish building.

Make sure to go forward with the CLA so we can merge your PR :) !

[CptCaptain]

Awesome, even better :)
I've signed the CLA, merge whenever you're ready.

[facebook-github-bot]

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