-
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
[Logging] Switch worker_setup_hook to worker_process_setup_hook #37247
[Logging] Switch worker_setup_hook to worker_process_setup_hook #37247
Conversation
Signed-off-by: SangBin Cho <rkooo567@gmail.com>
Signed-off-by: SangBin Cho <rkooo567@gmail.com>
Signed-off-by: SangBin Cho <rkooo567@gmail.com>
This is an experimental feature. The semantic of the API is subject to change. | ||
It doesn't support [Ray Client](ray-client-ref) yet. | ||
|
||
When you use `ray.init(runtime_env={...})` with a [Ray Job Submission](jobs-quickstart) API (`ray job subimt --working-dir` or `ray job submit --runtime-env ...`), runtime_env passed to `ray.init` is ignored. |
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.
When you use `ray.init(runtime_env={...})` with a [Ray Job Submission](jobs-quickstart) API (`ray job subimt --working-dir` or `ray job submit --runtime-env ...`), runtime_env passed to `ray.init` is ignored. | |
When you use `ray.init(runtime_env={...})` with a [Ray Job Submission](jobs-quickstart) API (`ray job submit --working-dir` or `ray job submit --runtime-env ...`), runtime_env passed to `ray.init` is ignored. |
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.
This is hard to parse. Are you saying that these two switches don't work when you just Ray Jobs?
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.
ray job ... is a job API. When you use the job API, the driver runtime env is ignored.
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.
Any recommended sentences?
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.
I changed it. Can you take a look? If there's no response by today, I will just merge a PR!
Signed-off-by: SangBin Cho <rkooo567@gmail.com>
Signed-off-by: SangBin Cho <rkooo567@gmail.com>
…project#37247) Change worker_setup_hook -> worker_process_setup_hook Signed-off-by: SangBin Cho <rkooo567@gmail.com>
…) (#37463) Change worker_setup_hook -> worker_process_setup_hook Signed-off-by: SangBin Cho <rkooo567@gmail.com>
…project#37247) Change worker_setup_hook -> worker_process_setup_hook
…project#37247) Change worker_setup_hook -> worker_process_setup_hook Signed-off-by: NripeshN <nn2012@hw.ac.uk>
…project#37247) Change worker_setup_hook -> worker_process_setup_hook Signed-off-by: e428265 <arvind.chandramouli@lmco.com>
…project#37247) Change worker_setup_hook -> worker_process_setup_hook Signed-off-by: Victor <vctr.y.m@example.com>
Why are these changes needed?
Change worker_setup_hook -> worker_process_setup_hook
Related issue number
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/
under thecorresponding
.rst
file.