Incompatibility Flags check #252
Merged
Conversation
This file contains 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.
As described in the MAVLink documentation MAVLink 2 messages with unknown Incompatibility Flags must be discard. This PR implements this behavior with the sole known flag being
MAVLINK_IFLAG_SIGNED.This is technically a semver breaking change since it causes previously accepted messages with unknown flags to be rejected.
Detailed changes:
read_v2_raw_messageandread_v2_raw_message_asyncignore messages with Incompatibility Flags other thenMAVLINK_IFLAG_SIGNEDset