Conversation
🔎 FLASH Analysispx4_fmu-v5x [Total VM Diff: 144 byte (0.01 %)]px4_fmu-v6x [Total VM Diff: 152 byte (0.01 %)]Updated: 2025-04-25T11:27:06 |
Contributor
Author
sfuhrer
approved these changes
Apr 14, 2025
Contributor
sfuhrer
left a comment
There was a problem hiding this comment.
Thanks for the diligent explanation, looks very reasonable to me.
…age length overrun
d908237 to
1438219
Compare
dakejahl
approved these changes
Apr 25, 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.




Solved Problem
Geofence breaching messages had been overrunning length of STATUSTEXT.text by a few characters. This may in some events lead to invalid character being displayed in GCS.
Solution
Changelog Entry
For release notes:
Context
Related links, screenshot before/after, video