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

[Doc] Fix a broken rllib reference #46280

Merged

Conversation

peytondmurray
Copy link
Contributor

Why are these changes needed?

This PR fixes a broken RLlib link.

Related issue number

Currently blocking #46279, but I've broken this change out into a separate PR to minimize codeowner impact.

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

@can-anyscale can-anyscale enabled auto-merge (squash) June 26, 2024 19:59
@github-actions github-actions bot added the go add ONLY when ready to merge, run all tests label Jun 26, 2024
@can-anyscale can-anyscale merged commit ec9e410 into ray-project:master Jun 26, 2024
7 checks passed
can-anyscale pushed a commit that referenced this pull request Jun 27, 2024
## Why are these changes needed?

This PR fixes a broken link and type annotation in Ray Train, and
re-enables nitpicky mode in the docs.

There were two issues affecting the documentation:

1. The autosummary of `ray.data.dataset.Schema` was incorrectly
referencing `ray.data.Schema`
2. The docstring of `Schema` contained entries (`types` and `names`)
under the `Attribute` section which were already documented using
docstrings of their respective properties. The build error that you get
when you build the documentation unhelpfully suggested using `noindex`,
but instead we just need to either use the docstrings in `Attributes` or
the docstrings under the property methods, not both.

## Related issue number

Reverts #46241. Blocked by #46280.

Signed-off-by: pdmurray <[email protected]>
Signed-off-by: Peyton Murray <[email protected]>
Co-authored-by: Balaji Veeramani <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go add ONLY when ready to merge, run all tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants