[RLlib] - Example _set_state in tcp_client_inference_env_runner incorrectly handles TemporaryDirectory (path issue).

[zhujqlibiao]

What happened + What you expected to happen

ray\rllib\env\tcp_client_inference_env_runner.py

The _set_state function in the RLlib example improperly uses TemporaryDirectory. Specifically:

The ONNX file is written to the current working directory instead of the temporary directory created by TemporaryDirectory.
This causes permission issues in environments where the current working directory is not writable.

Steps to Reproduce:
def _set_state(msg_body):
with tempfile.TemporaryDirectory():
with open("_temp_onnx", "wb") as f:
f.write(
gzip.decompress(
base64.b64decode(msg_body["onnx_file"].encode("utf-8"))
)
)
onnx_session = onnxruntime.InferenceSession("_temp_onnx")
output_names = [o.name for o in onnx_session.get_outputs()]
return onnx_session, output_names
Run the above code in an environment where the current working directory is not writable.
Observe the permission error.

Versions / Dependencies

Version: 2.41.0
windows11

Reproduction script

Problem Analysis:
The TemporaryDirectory is created but not used to store the file _temp_onnx. Instead, the file is written to the current working directory (os.getcwd()), which can cause issues in environments where the working directory is read-only or restricted.

Proposed Solution:
The ONNX file should be written to the temporary directory instead of the current working directory. Here's the corrected code:

def _set_state(msg_body):
with tempfile.TemporaryDirectory() as temp_dir:
temp_file_path = os.path.join(temp_dir, "_temp_onnx")
with open(temp_file_path, "wb") as f:
f.write(
gzip.decompress(
base64.b64decode(msg_body["onnx_file"].encode("utf-8"))
)
)
onnx_session = onnxruntime.InferenceSession(temp_file_path)
output_names = [o.name for o in onnx_session.get_outputs()]
return onnx_session, output_names
Why This Fix Works:
By explicitly using the path provided by TemporaryDirectory, the ONNX file is stored in a writable location that is automatically cleaned up after use.
This avoids permission issues and ensures the file is written safely in environments with restricted working directory permissions.

Issue Severity

None