Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue disconnecting when controlling multiple cameras #1

Open
PipGrylls opened this issue Feb 3, 2022 · 2 comments
Open

Issue disconnecting when controlling multiple cameras #1

PipGrylls opened this issue Feb 3, 2022 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@PipGrylls
Copy link
Owner

Tracking:
gopro#124

@PipGrylls PipGrylls added the bug Something isn't working label Feb 3, 2022
@PipGrylls PipGrylls self-assigned this Feb 3, 2022
@PipGrylls
Copy link
Owner Author

Issue recreated with dev install of latest code release

@PipGrylls
Copy link
Owner Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant