-
Notifications
You must be signed in to change notification settings - Fork 6.7k
[docs] Add antipattern for nested ray.get #43184
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
Conversation
Signed-off-by: Stephanie Wang <[email protected]>
Co-authored-by: angelinalg <[email protected]> Signed-off-by: Stephanie Wang <[email protected]>
Co-authored-by: angelinalg <[email protected]> Signed-off-by: Stephanie Wang <[email protected]>
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
|
Signed-off-by: Stephanie wang <[email protected]>
|
Signed-off-by: Stephanie wang <[email protected]>
This pull request has been automatically marked as stale because it has not had You can always ask for help on our discussion forum or Ray's public slack channel. If you'd like to keep this open, just leave any comment, and the stale label will be removed. |
Signed-off-by: Jiajun Yao <[email protected]>
Why are these changes needed?
Add antipattern for nested ray.get, which should be avoided if the ObjectRefs can be passed as direct task args instead.