[Formatting] headers and future imports checks

[vmoens]

• init
• init

Description

Describe your changes in detail.

Motivation and Context

Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. You can use the syntax close #15213 if this solves the issue #15213

• [ ] I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes

What types of changes does your code introduce? Remove all that do not apply:

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds core functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Documentation (update in the documentation)
• [ ] Example (update in the folder of examples)

Checklist

Go over all the following points, and put an x in all the boxes that apply. If you are unsure about any of these, don't hesitate to ask. We are here to help!

• [ ] I have read the CONTRIBUTION guide (required)
• [ ] My change requires a change to the documentation.
• [ ] I have updated the tests accordingly (required for a bug fix or a new feature).
• [ ] I have updated the documentation accordingly.

[pytorch-bot[bot]]

:link: Helpful Links

:test_tube: See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/rl/2973

• :page_facing_up: Preview Python docs built from this PR

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

:x: 7 New Failures, 7 Unrelated Failures

As of commit 5c79b67bf484476dac2f41f63b7dba423edad91b with merge base 6ca216e1a0f30606da83035f6f322fc9eec8ce44 ():

NEW FAILURES - The following jobs have failed:

• Continuous Benchmark (PR) / GPU Pytest benchmark (gh) Process completed with exit code 1.
• Generate documentation / build-docs (3.9, 12.8) / linux-job (gh) RuntimeError: Command docker exec -t 4b9336a3bffa5a73ed873600928ba40b4346bdd9c531600dcd2dc77fd027eb2d /exec failed with exit code 2
• Habitat Tests on Linux / tests (3.9, 12.8) / linux-job (gh) RuntimeError: Command docker exec -t 47f260a2f13ddcae67224e524e8f9dd15e2bd925f2509b43fab9a99987b4ed86 /exec failed with exit code 1
• Lint / python-source-and-configs / linux-job (gh)
• Unit-tests on Linux / tests-cpu (3.11) / linux-job (gh) test/test_env.py::TestNonTensorEnv::test_parallel[False-False]
• Unit-tests on Linux / tests-cpu (3.12) / linux-job (gh) test/test_transforms.py::TestVecNorm::test_vecnorm_parallel_auto[5]
• Unit-tests on Linux / tests-olddeps (3.9, 11.6) / linux-job (gh) RuntimeError: Command docker exec -t 339b29624d0682b92e8f81463fee4731813fc38884407454ccb79b2139eda4e0 /exec failed with exit code 2

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• Continuous Benchmark (PR) / CPU Pytest benchmark (gh) (similar failure)

BROKEN TRUNK - The following jobs failed but was present on the merge base:

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

• Continuous Benchmark / CPU Pytest benchmark (gh) (trunk failure)
• Continuous Benchmark / GPU Pytest benchmark (gh) (trunk failure) RuntimeError: one of the variables needed for gradient computation has been modified by an inplace operation: [torch.cuda.FloatTensor []] is at version 4; expected version 3 instead. Hint: enable anomaly detection to find the operation that failed to compute its gradient, with torch.autograd.set_detect_anomaly(True).
• Libs Tests on Linux / unittests-gym (3.9, 12.8) / linux-job (gh) (trunk failure) test/test_libs.py::TestGym::test_gym_fake_td[True-False-3-HalfCheetah-v2]
• LLM Tests on Linux / unittests (3.9, 12.8) / linux-job (gh) (trunk failure) ##[error]The operation was canceled.
• Unit-tests on Linux / tests-optdeps (3.11, 12.8) / linux-job (gh) (trunk failure) test/test_cost.py::TestValues::test_gae_multi_done
• Unit-tests on Windows / unittests-cpu (3.10, windows.4xlarge, cpu) / windows-job (gh) (trunk failure) Process completed with exit code 2.

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

[facebook-github-bot]

Hi @vmoens!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

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!