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
As far as I can tell this issue is caused by the second disconnect event not being able to access the future due to it being on the incorrect event loop.
Line 413 of bleak_wrapper.py awaits the handle.disconnect()
The trace moves into bleak and dbus_next site_packages immediately.
The issue could be in the setting of the module loop line 66 of bleak_wrapper. Given the Bleak wrapper is a singleton this loop may be incorrectly shared between two GoPro classes.
Next steps:
Test the same connect disconnect loop via other SDK languages (C#), if the behaviour does not persist then we conclude it is the Python, else it is the GoPro (or C#)
Attach breakpoints into the loop and begin to query the event loops of each GoPro
Tracking:
gopro#124
The text was updated successfully, but these errors were encountered: