It might be helpful to have a synchronous version of SpawnDebugger, perhaps with a param max_wait_ms, that blocks until the debugger has started up or until max_wait_ms is exceeded. We ran into issues in our multi-agent setup where we were spawning a debugger whenever we detected that a debugger was not yet created, and once this is done in a tight loop while creating many agents it leads to multiple debugger applications being open, with each opening a window for each existing agent.
It might be helpful to have a synchronous version of
SpawnDebugger
, perhaps with a parammax_wait_ms
, that blocks until the debugger has started up or untilmax_wait_ms
is exceeded. We ran into issues in our multi-agent setup where we were spawning a debugger whenever we detected that a debugger was not yet created, and once this is done in a tight loop while creating many agents it leads to multiple debugger applications being open, with each opening a window for each existing agent.