Closed leoscholl closed 3 years ago
Maybe an issue in mp_proxy.py line 256 self.stop
calls parent taskwrapper.py target_proxy.end_task
which doesn’t work if the task has already finished. Can be temporarily fixed by leaving out this call to self.stop
. But why is the mp_proxy status
not already set to 0 when the task has ended?
maybe related to #27
going to close this issue, since it's not causing problems any more. but for future reference, there is still a non-critical bug somewhere in the rpc code...
tasktrack_log shows that end_task is being called at the beginning of these experiments
seems to only happen with optitrack feature enabled?