Skip to content

[core] (cgroups 25/n) Making cgroup_path a part of the public API for ray.init(...)#60726

Merged
edoakes merged 6 commits intomasterfrom
irabbani/cgroups-21
Feb 4, 2026
Merged

[core] (cgroups 25/n) Making cgroup_path a part of the public API for ray.init(...)#60726
edoakes merged 6 commits intomasterfrom
irabbani/cgroups-21

Conversation

@israbbani
Copy link
Contributor

@israbbani israbbani commented Feb 3, 2026

Follow up from #60183.

When not running inside privileged containers, the user will have to specify a cgroup_path. It makes sense for this to be a part of the public API for ray.init(...).

Things I'm changing

  1. Promoting cgroup_path to a public API parameter for ray.init
  2. Updating tests to use that parameter.
  3. Running all cgroup tests on CI for all C++ and python changes.

ray.init(...)

Signed-off-by: irabbani <israbbani@gmail.com>
@israbbani israbbani added the go add ONLY when ready to merge, run all tests label Feb 3, 2026
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request makes cgroup_path a public parameter in ray.init(), which is a sensible change given its necessity in non-privileged container environments. The implementation correctly updates the function signature, documentation, and internal usage. I have a couple of minor suggestions to improve the documentation's clarity and to clean up some leftover code.

Signed-off-by: irabbani <israbbani@gmail.com>
@israbbani israbbani changed the title [core] (cgroups 21/n) Making cgroup_path a part of the public API for ray.init(...) [core] (cgroups 25/n) Making cgroup_path a part of the public API for ray.init(...) Feb 3, 2026
@israbbani israbbani marked this pull request as ready for review February 3, 2026 19:27
@israbbani israbbani requested a review from a team as a code owner February 3, 2026 19:27
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Signed-off-by: irabbani <israbbani@gmail.com>
@edoakes edoakes enabled auto-merge (squash) February 3, 2026 23:18
@edoakes edoakes disabled auto-merge February 3, 2026 23:18
@edoakes
Copy link
Collaborator

edoakes commented Feb 3, 2026

Don't forget to update the docs page

@israbbani
Copy link
Contributor Author

Yep waiting for this to merge and then I'll update the other PR.

@edoakes edoakes enabled auto-merge (squash) February 3, 2026 23:27
@github-actions github-actions bot disabled auto-merge February 4, 2026 00:00
Copy link
Contributor

@Kunchd Kunchd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming, we probably want to modify scipt.py to make cgroup-path public as well: https://github.com/ray-project/ray/blob/master/python/ray/scripts/scripts.py#L672.

Signed-off-by: irabbani <israbbani@gmail.com>
@israbbani
Copy link
Contributor Author

Assuming, we probably want to modify scipt.py to make cgroup-path public as well: https://github.com/ray-project/ray/blob/master/python/ray/scripts/scripts.py#L672.

Good point. Fixed

@edoakes edoakes enabled auto-merge (squash) February 4, 2026 01:18
@ray-gardener ray-gardener bot added the core Issues that should be addressed in Ray Core label Feb 4, 2026
@edoakes edoakes merged commit 44be7c5 into master Feb 4, 2026
7 checks passed
@edoakes edoakes deleted the irabbani/cgroups-21 branch February 4, 2026 02:48
tiennguyentony pushed a commit to tiennguyentony/ray that referenced this pull request Feb 6, 2026
… ray.init(...) (ray-project#60726)

Follow up from ray-project#60183.

When not running inside privileged containers, the user will have to
specify a `cgroup_path`. It makes sense for this to be a part of the
public API for `ray.init(...)`.

Things I'm changing
1. Promoting `cgroup_path` to a public API parameter for `ray.init`
2. Updating tests to use that parameter.
3. Running all cgroup tests on CI for all C++ and python changes.

---------

Signed-off-by: irabbani <israbbani@gmail.com>
Signed-off-by: tiennguyentony <46289799+tiennguyentony@users.noreply.github.com>
tiennguyentony pushed a commit to tiennguyentony/ray that referenced this pull request Feb 7, 2026
… ray.init(...) (ray-project#60726)

Follow up from ray-project#60183.

When not running inside privileged containers, the user will have to
specify a `cgroup_path`. It makes sense for this to be a part of the
public API for `ray.init(...)`.

Things I'm changing
1. Promoting `cgroup_path` to a public API parameter for `ray.init`
2. Updating tests to use that parameter.
3. Running all cgroup tests on CI for all C++ and python changes.

---------

Signed-off-by: irabbani <israbbani@gmail.com>
Signed-off-by: tiennguyentony <46289799+tiennguyentony@users.noreply.github.com>
tiennguyentony pushed a commit to tiennguyentony/ray that referenced this pull request Feb 7, 2026
… ray.init(...) (ray-project#60726)


Follow up from ray-project#60183.

When not running inside privileged containers, the user will have to
specify a `cgroup_path`. It makes sense for this to be a part of the
public API for `ray.init(...)`.

Things I'm changing
1. Promoting `cgroup_path` to a public API parameter for `ray.init`
2. Updating tests to use that parameter.
3. Running all cgroup tests on CI for all C++ and python changes.

---------

Signed-off-by: irabbani <israbbani@gmail.com>
Signed-off-by: tiennguyentony <46289799+tiennguyentony@users.noreply.github.com>
tiennguyentony pushed a commit to tiennguyentony/ray that referenced this pull request Feb 7, 2026
… ray.init(...) (ray-project#60726)


Follow up from ray-project#60183.

When not running inside privileged containers, the user will have to
specify a `cgroup_path`. It makes sense for this to be a part of the
public API for `ray.init(...)`.

Things I'm changing
1. Promoting `cgroup_path` to a public API parameter for `ray.init`
2. Updating tests to use that parameter.
3. Running all cgroup tests on CI for all C++ and python changes.

---------

Signed-off-by: irabbani <israbbani@gmail.com>
Signed-off-by: tiennguyentony <46289799+tiennguyentony@users.noreply.github.com>
tiennguyentony pushed a commit to tiennguyentony/ray that referenced this pull request Feb 7, 2026
… ray.init(...) (ray-project#60726)

Follow up from ray-project#60183.

When not running inside privileged containers, the user will have to
specify a `cgroup_path`. It makes sense for this to be a part of the
public API for `ray.init(...)`.

Things I'm changing
1. Promoting `cgroup_path` to a public API parameter for `ray.init`
2. Updating tests to use that parameter.
3. Running all cgroup tests on CI for all C++ and python changes.

---------

Signed-off-by: irabbani <israbbani@gmail.com>
Signed-off-by: tiennguyentony <46289799+tiennguyentony@users.noreply.github.com>
Sparks0219 pushed a commit to Sparks0219/ray that referenced this pull request Feb 9, 2026
… ray.init(...) (ray-project#60726)

Follow up from ray-project#60183. 

When not running inside privileged containers, the user will have to
specify a `cgroup_path`. It makes sense for this to be a part of the
public API for `ray.init(...)`.

Things I'm changing
1. Promoting `cgroup_path` to a public API parameter for `ray.init`
2. Updating tests to use that parameter. 
3. Running all cgroup tests on CI for all C++ and python changes.

---------

Signed-off-by: irabbani <israbbani@gmail.com>
elliot-barn pushed a commit that referenced this pull request Feb 9, 2026
… ray.init(...) (#60726)

Follow up from #60183. 

When not running inside privileged containers, the user will have to
specify a `cgroup_path`. It makes sense for this to be a part of the
public API for `ray.init(...)`.

Things I'm changing
1. Promoting `cgroup_path` to a public API parameter for `ray.init`
2. Updating tests to use that parameter. 
3. Running all cgroup tests on CI for all C++ and python changes.

---------

Signed-off-by: irabbani <israbbani@gmail.com>
Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com>
elliot-barn pushed a commit that referenced this pull request Feb 9, 2026
… ray.init(...) (#60726)

Follow up from #60183. 

When not running inside privileged containers, the user will have to
specify a `cgroup_path`. It makes sense for this to be a part of the
public API for `ray.init(...)`.

Things I'm changing
1. Promoting `cgroup_path` to a public API parameter for `ray.init`
2. Updating tests to use that parameter. 
3. Running all cgroup tests on CI for all C++ and python changes.

---------

Signed-off-by: irabbani <israbbani@gmail.com>
ans9868 pushed a commit to ans9868/ray that referenced this pull request Feb 18, 2026
… ray.init(...) (ray-project#60726)

Follow up from ray-project#60183.

When not running inside privileged containers, the user will have to
specify a `cgroup_path`. It makes sense for this to be a part of the
public API for `ray.init(...)`.

Things I'm changing
1. Promoting `cgroup_path` to a public API parameter for `ray.init`
2. Updating tests to use that parameter.
3. Running all cgroup tests on CI for all C++ and python changes.

---------

Signed-off-by: irabbani <israbbani@gmail.com>
Signed-off-by: Adel Nour <ans9868@nyu.edu>
Aydin-ab pushed a commit to kunling-anyscale/ray that referenced this pull request Feb 20, 2026
… ray.init(...) (ray-project#60726)

Follow up from ray-project#60183. 

When not running inside privileged containers, the user will have to
specify a `cgroup_path`. It makes sense for this to be a part of the
public API for `ray.init(...)`.

Things I'm changing
1. Promoting `cgroup_path` to a public API parameter for `ray.init`
2. Updating tests to use that parameter. 
3. Running all cgroup tests on CI for all C++ and python changes.

---------

Signed-off-by: irabbani <israbbani@gmail.com>
peterxcli pushed a commit to peterxcli/ray that referenced this pull request Feb 25, 2026
… ray.init(...) (ray-project#60726)

Follow up from ray-project#60183.

When not running inside privileged containers, the user will have to
specify a `cgroup_path`. It makes sense for this to be a part of the
public API for `ray.init(...)`.

Things I'm changing
1. Promoting `cgroup_path` to a public API parameter for `ray.init`
2. Updating tests to use that parameter.
3. Running all cgroup tests on CI for all C++ and python changes.

---------

Signed-off-by: irabbani <israbbani@gmail.com>
Signed-off-by: peterxcli <peterxcli@gmail.com>
peterxcli pushed a commit to peterxcli/ray that referenced this pull request Feb 25, 2026
… ray.init(...) (ray-project#60726)

Follow up from ray-project#60183.

When not running inside privileged containers, the user will have to
specify a `cgroup_path`. It makes sense for this to be a part of the
public API for `ray.init(...)`.

Things I'm changing
1. Promoting `cgroup_path` to a public API parameter for `ray.init`
2. Updating tests to use that parameter.
3. Running all cgroup tests on CI for all C++ and python changes.

---------

Signed-off-by: irabbani <israbbani@gmail.com>
Signed-off-by: peterxcli <peterxcli@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core Issues that should be addressed in Ray Core go add ONLY when ready to merge, run all tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants