User callback debugging and MavlinkDirect improvements#2694
Merged
Conversation
This adds a class to debug user callbacks taking too long. The class is only instantiated and used when the env variable MAVSDK_CALLBACK_DEBUGGING=1 is set.
We should not use the callback queue internally (unless we need to) but only once it comes to external/user callbacks.
0de7714 to
e25d7e6
Compare
|
JonasVautherin
approved these changes
Oct 31, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



This adds better user callback tracking with
MAVSDK_CALLBACK_DEBUGGING=1set:The instrumentation let me discover that we were using the queue internally instead of externally in MavlinkDirect. That's fixed as well.