-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
[Client] Make Client{ObjectRef,ActorRef} subclasses of their server-side counterparts #16110
Conversation
f6e13dc
to
10ad72b
Compare
coool, all the buildkite checks pass, will take a closer look soon |
Add basic unit tests.
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.
Thank you for adding these tests!!
@ericl , can you please review this? |
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.
Looks good from my perspective! Just want a few more eyes on it before merging!
Looks great, thanks for digging into how to fix this! |
Thanks @mwtian ! |
…server-side counterparts (ray-project#16110)" This reverts commit f14f197.
…f their server-side counterparts (ray-project#16110)" (ray-project#16196)" This reverts commit 9942505.
Why are these changes needed?
This avoids code duplication and user confusion when handling Client{ObjectRef,ActorRef}. Users just need to know about ObjectRef and ActorID regardless of whether the logic runs in Ray worker or with Ray client.
Compared to current implementations of Client{ObjectRef,ActorRef}, the differences of the new implementations are the additional methods from the parents
ObjectRef
andActorID
. No additional differences are intended.Related issue number
Closes #14042
Checks
scripts/format.sh
to lint the changes in this PR.