From 590458ee344d12d96719bfd20c0d2c8d5dc4922f Mon Sep 17 00:00:00 2001 From: Lonnie Liu Date: Tue, 27 Jun 2023 05:34:55 +0000 Subject: [PATCH] [doc] fix documentation test failure add a dash. Signed-off-by: Lonnie Liu --- .../cluster/running-applications/job-submission/ray-client.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/cluster/running-applications/job-submission/ray-client.rst b/doc/source/cluster/running-applications/job-submission/ray-client.rst index 19ebc67ffdb6..7a43afc91dbf 100644 --- a/doc/source/cluster/running-applications/job-submission/ray-client.rst +++ b/doc/source/cluster/running-applications/job-submission/ray-client.rst @@ -287,7 +287,7 @@ If a ``working_dir`` is specified in the runtime env, when running ``ray.init()` Ray workers are started in the ``/tmp/ray/session_latest/runtime_resources/_ray_pkg_`` directory on the cluster. This means that relative paths in the remote tasks and actors in the code will work on the laptop and on the cluster without any code changes. For example, if the ``working_dir`` on the laptop contains ``data.txt`` and ``run.py``, inside the remote task definitions in ``run.py`` one can just use the relative path ``"data.txt"``. Then ``python run.py`` will work on my laptop, and also on the cluster. As a side note, since relative paths can be used in the code, the absolute path is only useful for debugging purposes. Troubleshooting --------------- +--------------- Error: Attempted to reconnect a session that has already been cleaned up ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~