You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can't get event loop from inside a coroutine, apparently. I have no idea how to fix this and it's probably because I should be doing this in a different way.
While not a perfect solution because introduce a race condition, removing the creation of a coroutine for waiting the response makes it possible to call rpc_request from a method called from the Executor. The rpc_request was always meant to be blocking so instead of running it on the asyncio thread it's actually running on the main thread.
For requests that require a faster rate, such as stream_frame it doesn't use the blocking rpc_request but sends the data straight to the connection.
As the result of the race condition apparently behaves inconsistently on different computers (might be the specs or the OS) this turns out to be a terrible idea. Reopening this issue and going to try a different approach like this or this.
Can't get event loop from inside a coroutine, apparently. I have no idea how to fix this and it's probably because I should be doing this in a different way.
This code:
Prints
There is no current event loop in thread 'ThreadPoolExecutor-0_0'.
when I swipe up on Motion Sensor.The text was updated successfully, but these errors were encountered: