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

gimbal: only reset protocol on destruction #2283

Merged
merged 1 commit into from
Apr 16, 2024
Merged

Conversation

julianoes
Copy link
Collaborator

Don't destruct the found protocol on each discovery. Otherwise, we lose all subscriptions when a timeout occurs.

Longer term, we'll probably just want to remove the v1 logic to simplify this.

Don't destruct the found protocol on each discovery. Otherwise, we lose
all subscriptions when a timeout occurs.

Longer term, we'll probably just want to remove the v1 logic to simplify
this.

Signed-off-by: Julian Oes <julian@oes.ch>
Copy link

sonarcloud bot commented Apr 16, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@julianoes julianoes merged commit f074901 into main Apr 16, 2024
28 checks passed
@julianoes julianoes deleted the pr-fix-gimbal-state branch April 16, 2024 19:46
ddatsko pushed a commit to ddatsko/MAVSDK that referenced this pull request Aug 6, 2024
Don't destruct the found protocol on each discovery. Otherwise, we lose
all subscriptions when a timeout occurs.

Longer term, we'll probably just want to remove the v1 logic to simplify
this.

Signed-off-by: Julian Oes <julian@oes.ch>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant