<!-- Thank you for your contribution! Please review
https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before
opening a pull request. -->

<!-- Please add a reviewer to the assignee section when you create a PR.
If you don't have the access to it, we will shortly find a reviewer and
assign them to your PR. -->

## Why are these changes needed?

It is not safe to use the current process' cmdline to determine the "uv
run" commandline args, since e.g. multiprocessing spawn will garble the
commandline, so our current way of detecting the "uv run" commandline
won't work if the process that runs `ray.init` was created with
multiprocessing spawn like it is the case in some vllm settings. Also
the command line might have been modified by setproctitle.

This PR changes the extraction of the `uv run` command line to a more
robust way that doesn't involve any state in the current process, only
the uv command line of the uv shim process, and also adds a regression
test.

It also makes it possible to run `uv run -m <module>` and adds a
regression test for that as well.

## Related issue number

<!-- For example: "Closes #1234" -->

## Checks

- [ ] I've signed off every commit(by using the -s flag, i.e., `git
commit -s`) in this PR.
- [ ] I've run `scripts/format.sh` to lint the changes in this PR.
- [ ] I've included any doc changes needed for
https://docs.ray.io/en/master/.
- [ ] I've added any new APIs to the API Reference. For example, if I
added a
method in Tune, I've added it in `doc/source/tune/api/` under the
           corresponding `.rst` file.
- [ ] I've made sure the tests are passing. Note that there might be a
few flaky tests, see the recent failures at https://flakey-tests.ray.io/
- Testing Strategy
   - [ ] Unit tests
   - [ ] Release tests
   - [ ] This PR is not tested :(

---------

Co-authored-by: pcmoritz <pcmoritz@anyscale.com>
Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com>

<!-- Thank you for your contribution! Please review
https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before
opening a pull request. -->

<!-- Please add a reviewer to the assignee section when you create a PR.
If you don't have the access to it, we will shortly find a reviewer and
assign them to your PR. -->

## Why are these changes needed?

It is not safe to use the current process' cmdline to determine the "uv
run" commandline args, since e.g. multiprocessing spawn will garble the
commandline, so our current way of detecting the "uv run" commandline
won't work if the process that runs `ray.init` was created with
multiprocessing spawn like it is the case in some vllm settings. Also
the command line might have been modified by setproctitle.

This PR changes the extraction of the `uv run` command line to a more
robust way that doesn't involve any state in the current process, only
the uv command line of the uv shim process, and also adds a regression
test.

It also makes it possible to run `uv run -m <module>` and adds a
regression test for that as well.

## Related issue number

<!-- For example: "Closes ray-project#1234" -->

## Checks

- [ ] I've signed off every commit(by using the -s flag, i.e., `git
commit -s`) in this PR.
- [ ] I've run `scripts/format.sh` to lint the changes in this PR.
- [ ] I've included any doc changes needed for
https://docs.ray.io/en/master/.
- [ ] I've added any new APIs to the API Reference. For example, if I
added a
method in Tune, I've added it in `doc/source/tune/api/` under the
           corresponding `.rst` file.
- [ ] I've made sure the tests are passing. Note that there might be a
few flaky tests, see the recent failures at https://flakey-tests.ray.io/
- Testing Strategy
   - [ ] Unit tests
   - [ ] Release tests
   - [ ] This PR is not tested :(

---------

Co-authored-by: pcmoritz <pcmoritz@anyscale.com>

<!-- Thank you for your contribution! Please review
https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before
opening a pull request. -->

<!-- Please add a reviewer to the assignee section when you create a PR.
If you don't have the access to it, we will shortly find a reviewer and
assign them to your PR. -->

## Why are these changes needed?

It is not safe to use the current process' cmdline to determine the "uv
run" commandline args, since e.g. multiprocessing spawn will garble the
commandline, so our current way of detecting the "uv run" commandline
won't work if the process that runs `ray.init` was created with
multiprocessing spawn like it is the case in some vllm settings. Also
the command line might have been modified by setproctitle.

This PR changes the extraction of the `uv run` command line to a more
robust way that doesn't involve any state in the current process, only
the uv command line of the uv shim process, and also adds a regression
test.

It also makes it possible to run `uv run -m <module>` and adds a
regression test for that as well.

## Related issue number

<!-- For example: "Closes #1234" -->

## Checks

- [ ] I've signed off every commit(by using the -s flag, i.e., `git
commit -s`) in this PR.
- [ ] I've run `scripts/format.sh` to lint the changes in this PR.
- [ ] I've included any doc changes needed for
https://docs.ray.io/en/master/.
- [ ] I've added any new APIs to the API Reference. For example, if I
added a
method in Tune, I've added it in `doc/source/tune/api/` under the
           corresponding `.rst` file.
- [ ] I've made sure the tests are passing. Note that there might be a
few flaky tests, see the recent failures at https://flakey-tests.ray.io/
- Testing Strategy
   - [ ] Unit tests
   - [ ] Release tests
   - [ ] This PR is not tested :(

---------

Co-authored-by: pcmoritz <pcmoritz@anyscale.com>
Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com>