rl icon indicating copy to clipboard operation
rl copied to clipboard
verified publisher icon pytorch

Minor fixes to comments and docstrings

Open thomasbbrunner opened this issue 1 year ago • 2 comments

Description

These are minor fixes to comments and docstrings that I've been gathering for the past weeks.

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)
  • [x] 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!

  • [x] 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.

thomasbbrunner avatar Sep 19 '24 08:09 thomasbbrunner

:link: Helpful Links

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

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

:heavy_exclamation_mark: 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

:x: 28 New Failures

As of commit 2a2b50f087cc15e466b05554d4f236da6659a2a5 with merge base e294c68ca8ac1794b19398b07a1cc42cca586ea1 (image):

NEW FAILURES - The following jobs have failed:

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

pytorch-bot[bot] avatar Sep 19 '24 08:09 pytorch-bot[bot]

Hi @thomasbbrunner!

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!

facebook-github-bot avatar Sep 19 '24 08:09 facebook-github-bot

No ciflow labels are configured for this repo. For information on how to enable CIFlow bot see this wiki

pytorch-bot[bot] avatar Sep 30 '24 13:09 pytorch-bot[bot]