-
Notifications
You must be signed in to change notification settings - Fork 321
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
[Post Ray 2.7.0 Release] Update Ray versions to Ray 2.7.0 #1423
[Post Ray 2.7.0 Release] Update Ray versions to Ray 2.7.0 #1423
Conversation
Signed-off-by: Gene Su <e870252314@gmail.com>
Signed-off-by: Gene Su <e870252314@gmail.com>
Signed-off-by: Gene Su <e870252314@gmail.com>
Signed-off-by: Gene Su <e870252314@gmail.com>
Signed-off-by: Gene Su <e870252314@gmail.com>
Signed-off-by: Gene Su <e870252314@gmail.com>
@@ -17,10 +17,10 @@ spec: | |||
serveConfigV2: | | |||
applications: | |||
- name: app1 | |||
import_path: autoscaling.blocked:app | |||
import_path: autoscaling.blocked_new:app |
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.
Would you mind sharing more details about why do we need to update this? Thanks!
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.
Bc the test was breaking and I found out there is another change Cindy made to fix it for newer version of Ray. Essentially the main differences is blocked_new.py is using the new get_deployment_handle
api while blocked.py was using the old get_handle()
…t#1423) Update Ray versions to Ray 2.7.0
…t#1423) Update Ray versions to Ray 2.7.0
Why are these changes needed?
Update to Ray 2.7.0
Related issue number
Post release step to update KubeRay.
Checks