-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[api] Annotate as public / move ray-core APIs to _private and add enforcement rule #25695
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RLlib is using ray._private.worker._mode() to detect whether we are in local or worker mode.
will there be a replacement API if this is explicitly marked as _private?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
stamp
Given we're deprecating local mode, I think this may be something we can remove in the future. |
…orcement rule (ray-project#25695) Enable checking of the ray core module, excluding serve, workflows, and tune, in ./ci/lint/check_api_annotations.py. This required moving many files to ray._private and associated fixes.
…orcement rule (ray-project#25695) Enable checking of the ray core module, excluding serve, workflows, and tune, in ./ci/lint/check_api_annotations.py. This required moving many files to ray._private and associated fixes. Signed-off-by: Frank Luan <[email protected]>
Why are these changes needed?
Enable checking of the
ray
core module, excluding serve, workflows, and tune, in./ci/lint/check_api_annotations.py
. This required moving many files toray._private
and associated fixes.