Upgrading to Ray 2.0 #1401
Merged
Upgrading to Ray 2.0 #1401
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pedropgusmao
requested review from
danieljanes and
tanertopal
as code owners
|
Thanks for the PR @pedropgusmao, do we need to change other instances or |
|
Sorry, I missed the example and two other calls to |
danieljanes
approved these changes
Sep 2, 2022
There was a problem hiding this comment.
Thanks for the update @pedropgusmao, lgtm!
@tanertopal thoughts?
tanertopal
approved these changes
Sep 5, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reference Issues/PRs
NA
What does this implement/fix? Explain your changes.
Upgrades Ray version to 2.0.0
Any other comments?
Fixed the Private Variable Access warning by
ray.worker.get()toray.get()as suggested by the API.