-
Notifications
You must be signed in to change notification settings - Fork 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
[Core|Serve]: Ray 2.39.0/2.40.0 keep runtime_env state between multiple ray.init() #49074
Comments
Martin4R
added
bug
Something that is supposed to be working; but isn't
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
labels
Dec 4, 2024
jcotant1
added
serve
Ray Serve Related Issue
core
Issues that should be addressed in Ray Core
labels
Dec 4, 2024
jjyao
added
P0
Issues that should be fixed in short order
and removed
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
labels
Dec 9, 2024
@MortalHappiness can you take a look at this one? |
Found the PR that caused this problem: #48218. Trying to fix it now. |
I haven't found the root cause, but reverting the changes of these 5 files in #48218 can fix this issue. |
jjyao
added
serve
Ray Serve Related Issue
and removed
core
Issues that should be addressed in Ray Core
labels
Dec 11, 2024
@akshay-anyscale can we have some serve team member to look at it. @MortalHappiness found the offending commit already. |
8 tasks
roshankathawate
pushed a commit
to roshankathawate/ray
that referenced
this issue
Jan 9, 2025
…project#49697) ## Why are these changes needed? State was being leaked across calls to `serve.run` due to in-place mutation within `get_deploy_args`. I've moved the logic into `build_app` and added associated unit tests. Also added an integration test matching the original bug report. ## Related issue number Closes ray-project#49074 --------- Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com> Signed-off-by: Roshan Kathawate <roshankathawate@gmail.com>
HYLcool
pushed a commit
to HYLcool/ray
that referenced
this issue
Jan 13, 2025
…project#49697) ## Why are these changes needed? State was being leaked across calls to `serve.run` due to in-place mutation within `get_deploy_args`. I've moved the logic into `build_app` and added associated unit tests. Also added an integration test matching the original bug report. ## Related issue number Closes ray-project#49074 --------- Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com> Signed-off-by: lielin.hyl <lielin.hyl@alibaba-inc.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened + What you expected to happen
We upgraded to Ray 2.39.0 and noticed our tests were failing. We tracked it down to Ray somehow take over runtime_env settings (precisely environment variables) from one ray.init(...) call to the next ray.init(...) call, even so there was a proper ray.shutdown() in between of them.
We did not find a workaround other than staying on Ray 2.38.0 for now.
Versions / Dependencies
Reproduction script
The issue can be easily reproduced by running the provided reproduction script within Ray CPU docker images of platform linux/amd64 and Python 3.12.
Script explanation
Script for Python 3.12
Issue Severity
High: It blocks me from completing my task.
The text was updated successfully, but these errors were encountered: