During game execution, an error occurs where the authentication session expires and the server rejects requests when the execution time exceeds 120 seconds.
₩₩₩
File “/workspace/orak-2025-starter-kit/.venv/lib/python3.11/site-packages/grpc/_channel.py”, line 996, in _end_unary_response_blocking raise _InactiveRpcError(state) # pytype: disable=not-instantiable ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with: status = StatusCode.UNAUTHENTICATED details = “Session expired (timeout: 120s)” debug_error_string = “UNKNOWN:Error received from peer {grpc_status:16, grpc_message:“Session expired (timeout: 120s)”}”
₩₩₩
When a timeout occurs, the code must be resubmitted and executed again. In this process, the game server continues execution from the state (obs), while the agent is reinitialized and loses all existing history and internal state. As a result, the agent’s decision-making flow is disrupted, causing issues in the overall workflow.
We would like to inquire about the following points:
-
Is it possible to extend the timeout limit for game execution to allow more leeway?
-
In the hidden test environment, are these execution-time constraints and agent state reinitialization issues taken into consideration in the system design?
We would appreciate your clarification on these matters.
Thank you.