Merge branch 'master' into master

Author: am-kinetica

.buildkite/test.rules.test.txt

@@ -83,7 +83,6 @@ docker/Dockerfile.ray: docker linux_wheels
 
 doc/code.py: doc
 doc/example.ipynb: doc
-doc/tutorial.rst: doc
 .readthedocs.yaml: doc
 .vale.ini: doc
 .vale/styles/config/vocabularies/Core/accept.txt: doc

.buildkite/test.rules.txt

@@ -20,6 +20,13 @@
 ! linux_wheels macos_wheels docker doc python_dependencies min_build tools
 ! release_tests spark_on_ray
 
+# NOTE: dstrodtman is leading effort to rework content in RST files, and wanted to shift
+# from blocking premerge for these changes. We can remove this pass block once effort concludes,
+# or earlier should regressions become an issue.
+doc/*.rst
+# pass
+;
+
 python/ray/air/
 @ ml train train_gpu tune data linux_wheels
 ;

.buildkite/windows.rayci.yml

@@ -106,7 +106,7 @@ steps:
         --test-env=CI="1"
         --test-env=RAY_CI_POST_WHEEL_TESTS="1"
         --test-env=USERPROFILE
-        --workers "$${BUILDKITE_PARALLEL_JOB_COUNT}" --worker-id "$${BUILDKITE_PARALLEL_JOB}" --parallelism-per-worker 3
+        --workers "$${BUILDKITE_PARALLEL_JOB_COUNT}" --worker-id "$${BUILDKITE_PARALLEL_JOB}" --parallelism-per-worker 1
     depends_on:
       - windowsbuild
       - block-windows-tests

ci/ci.sh

@@ -49,6 +49,7 @@ compile_pip_dependencies() {
       python/requirements/lint-requirements.txt \
       python/requirements/test-requirements.txt \
       python/requirements/cloud-requirements.txt \
+      python/requirements/serve/serve-test-requirements.txt \
       python/requirements/docker/ray-docker-requirements.txt \
       python/requirements/ml/core-requirements.txt \
       python/requirements/ml/data-requirements.txt \
@@ -117,6 +118,7 @@ compile_313_pip_dependencies() {
       python/requirements/lint-requirements.txt \
       python/requirements/py313/test-requirements.txt \
       python/requirements/cloud-requirements.txt \
+      python/requirements/serve/serve-test-requirements.txt \
       python/requirements/docker/ray-docker-requirements.txt \
       python/requirements/ml/py313/core-requirements.txt \
       python/requirements/ml/py313/data-requirements.txt \

ci/lint/pydoclint-baseline.txt

@@ -1477,8 +1477,6 @@ python/ray/serve/api.py
     DOC103: Function `start`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**kwargs: ].
     DOC201: Function `get_replica_context` does not have a return section in docstring
     DOC201: Function `ingress` does not have a return section in docstring
-    DOC101: Function `run_many`: Docstring contains fewer arguments than in function signature.
-    DOC103: Function `run_many`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [_local_testing_mode: bool].
     DOC101: Function `run`: Docstring contains fewer arguments than in function signature.
     DOC103: Function `run`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [_local_testing_mode: bool].
     DOC101: Function `multiplexed`: Docstring contains fewer arguments than in function signature.

ci/raydepsets/configs/ci_serve.depsets.yaml

@@ -12,8 +12,7 @@ depsets:
     depsets:
       - ray_img_depset_${PYTHON_SHORT}
     requirements:
-      - python/requirements/serve/serve-requirements.txt
-      - python/requirements/serve/haproxy-reqs.txt
+      - python/requirements/serve/serve-test-requirements.txt
     constraints:
       - /tmp/ray-deps/requirements_compiled_py3.13.txt
     output: python/deplocks/ci/serve_base_depset_py${PYTHON_VERSION}.lock

doc/source/data/joining-data.rst

@@ -54,15 +54,6 @@ Ray Data provides the following levers to allow tuning the performance of joins
     -   Note that, `num_partitions * partition_size_hint` should ideally be approximating actual dataset size, ie `partition_size_hint` could be estimated as dataset size divided by `num_partitions` (assuming relatively evenly sized partitions)
     -   However, in cases when dataset partitioning is expected to be heavily skewed `partition_size_hint` should approximate largest partition to prevent Out-of-Memory (OOM) errors
 
-.. note:: Be mindful that by default Ray reserves only 30% of the memory for its Object Store. This is recommended to be set at least to ***50%*** for all
-    Ray Data workloads, but especially so for ones utilizing joins.
-
-To configure Object Store to be 50%, add to your image:
-
-.. testcode::
-
-    RAY_DEFAULT_OBJECT_STORE_MEMORY_PROPORTION=0.5
-
 .. _joins_configuring_num_partitions:
 
 Configuring number of partitions

doc/source/data/performance-tips.rst

@@ -441,9 +441,6 @@ You can configure execution options with the global DataContext. The options are
         object_store_memory=10e9,
     )
 
-.. note::
-    Be mindful that by default Ray reserves only 30% of the memory for its Object Store. This is recommended to be set at least to ***50%*** for all Ray Data workloads.
-
 Reproducibility
 ---------------
 

doc/source/ray-core/handling-dependencies.rst

@@ -490,8 +490,8 @@ API Reference
 
 The ``runtime_env`` is a Python dictionary or a Python class :class:`ray.runtime_env.RuntimeEnv <ray.runtime_env.RuntimeEnv>` including one or more of the following fields:
 
-- ``working_dir`` (str): Specifies the working directory for the Ray workers. This must either be (1) an local existing directory with total size at most 500 MiB, (2) a local existing zipped file with total unzipped size at most 500 MiB (Note: ``excludes`` has no effect), or (3) a URI to a remotely-stored zip file containing the working directory for your job (no file size limit is enforced by Ray). See :ref:`remote-uris` for details.
-  The specified directory will be downloaded to each node on the cluster, and Ray workers will be started in their node's copy of this directory.
+- ``working_dir`` (str): Specifies the working directory for the Ray workers. This must either be (1) a local existing directory with total size at most 500 MiB, (2) a local existing archive file (``.zip``, ``.tar.gz``, or ``.tgz``) with total uncompressed size at most 500 MiB (Note: ``excludes`` has no effect), or (3) a URI to a remotely-stored archive (``.zip``, ``.tar.gz``, or ``.tgz``) containing the working directory for your job (no file size limit is enforced by Ray). See :ref:`remote-uris` for details.
+  The specified directory is downloaded to each node on the cluster, and Ray workers start in their node's copy of this directory.
 
   - Examples
 
@@ -503,6 +503,8 @@ The ``runtime_env`` is a Python dictionary or a Python class :class:`ray.runtime
 
     - ``"s3://path/to/my_dir.zip"``
 
+    - ``"s3://path/to/my_dir.tar.gz"``
+
   Note: Setting a local directory per-task or per-actor is currently unsupported; it can only be set per-job (i.e., in ``ray.init()``).
 
   Note: By default, if the local directory contains a ``.gitignore`` and/or ``.rayignore`` file, the specified files are not uploaded to the cluster. To disable the ``.gitignore`` from being considered, set ``RAY_RUNTIME_ENV_IGNORE_GITIGNORE=1`` on the machine doing the uploading.
@@ -512,7 +514,7 @@ The ``runtime_env`` is a Python dictionary or a Python class :class:`ray.runtime
   Note: If the local directory contains symbolic links, Ray follows the links and the files they point to are uploaded to the cluster.
 
 - ``py_modules`` (List[str|module]): Specifies Python modules to be available for import in the Ray workers.  (For more ways to specify packages, see also the ``pip`` and ``conda`` fields below.)
-  Each entry must be either (1) a path to a local file or directory, (2) a URI to a remote zip or wheel file (see :ref:`remote-uris` for details), (3) a Python module object, or (4) a path to a local `.whl` file.
+  Each entry must be either (1) a path to a local file or directory, (2) a URI to a remote archive (``.zip``, ``.tar.gz``, ``.tgz``) or wheel (``.whl``) file (see :ref:`remote-uris` for details), (3) a Python module object, or (4) a path to a local ``.whl`` file.
 
   - Examples of entries in the list:
 
@@ -818,25 +820,31 @@ If you want to specify this directory as a local path, your ``runtime_env`` dict
   runtime_env = {..., "working_dir": "/some_path/example_dir", ...}
 
 Suppose instead you want to host your files in your ``/some_path/example_dir`` directory remotely and provide a remote URI.
-You would need to first compress the ``example_dir`` directory into a zip file.
+You need to first compress the ``example_dir`` directory into a ``.zip`` or ``.tar.gz`` archive.
 
-There should be no other files or directories at the top level of the zip file, other than ``example_dir``.
-You can use the following command in the Terminal to do this:
+There should be no other files or directories at the top level of the archive, other than ``example_dir``.
+You can use one of the following commands in the Terminal:
 
 .. code-block:: bash
 
     cd /some_path
-    zip -r zip_file_name.zip example_dir
+    # Using zip:
+    zip -r archive.zip example_dir
+    # Using tar.gz:
+    tar -czf archive.tar.gz example_dir
 
-Note that this command must be run from the *parent directory* of the desired ``working_dir`` to ensure that the resulting zip file contains a single top-level directory.
-In general, the zip file's name and the top-level directory's name can be anything.
-The top-level directory's contents will be used as the ``working_dir`` (or ``py_module``).
+Run this command from the *parent directory* of the desired ``working_dir`` to ensure that the resulting archive contains a single top-level directory.
+In general, the archive's name and the top-level directory's name can be anything.
+The top-level directory's contents are used as the ``working_dir`` (or ``py_module``).
 
-You can check that the zip file contains a single top-level directory by running the following command in the Terminal:
+You can check that the archive contains a single top-level directory by running one of the following commands in the Terminal:
 
 .. code-block:: bash
 
-  zipinfo -1 zip_file_name.zip
+  # For zip:
+  zipinfo -1 archive.zip
+  # For tar.gz:
+  tar -tzf archive.tar.gz
   # example_dir/
   # example_dir/my_file_1.txt
   # example_dir/subdir/my_file_2.txt
@@ -849,15 +857,22 @@ Your ``runtime_env`` dictionary should contain:
 
   runtime_env = {..., "working_dir": "s3://example_bucket/example.zip", ...}
 
+You can also use ``.tar.gz`` or ``.tgz`` archives:
+
+.. testcode::
+  :skipif: True
+
+  runtime_env = {..., "working_dir": "s3://example_bucket/example.tar.gz", ...}
+
 .. warning::
 
-  Check for hidden files and metadata directories in zipped dependencies.
-  You can inspect a zip file's contents by running the ``zipinfo -1 zip_file_name.zip`` command in the Terminal.
-  Some zipping methods can cause hidden files or metadata directories to appear in the zip file at the top level.
-  To avoid this, use the ``zip -r`` command directly on the directory you want to compress from its parent's directory. For example, if you have a directory structure such as: ``a/b`` and you want to compress ``b``, issue the ``zip -r b`` command from the directory ``a.``
-  If Ray detects more than a single directory at the top level, it will use the entire zip file instead of the top-level directory, which may lead to unexpected behavior.
+  Check for hidden files and metadata directories in archived dependencies.
+  You can inspect an archive's contents by running ``zipinfo -1 archive.zip`` or ``tar -tzf archive.tar.gz`` in the Terminal.
+  Some archiving methods can cause hidden files or metadata directories to appear at the top level.
+  To avoid this, use ``zip -r`` or ``tar -czf`` directly on the directory you want to compress from its parent's directory. For example, if you have a directory structure such as: ``a/b`` and you want to compress ``b``, issue the command from the directory ``a``.
+  If Ray detects more than a single directory at the top level, it uses the entire archive instead of the top-level directory, which may lead to unexpected behavior.
 
-Currently, four types of remote URIs are supported for hosting ``working_dir`` and ``py_modules`` packages:
+Remote URIs support ``.zip``, ``.tar.gz``, and ``.tgz`` archive formats. Four types of remote URIs are supported for hosting ``working_dir`` and ``py_modules`` packages:
 
 - ``HTTPS``: ``HTTPS`` refers to URLs that start with ``https``.
   These are particularly useful because remote Git providers (e.g. GitHub, Bitbucket, GitLab, etc.) use ``https`` URLs as download links for repository archives.

doc/source/serve/api/index.md

@@ -94,6 +94,7 @@ See the [model composition guide](serve-model-composition) for how to update cod
    :toctree: doc/
    :template: autosummary/autopydantic.rst
 
+   serve.config.ControllerOptions
    serve.config.gRPCOptions
    serve.config.HTTPOptions
    serve.config.AutoscalingConfig