fix(ulog): the index of the timestamp may be non-zero #1016
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
The previous parsing assumed that the timestamp for a ulog data series was always at index 0, which is often, but not necessarily the case. The parser now store the correct index when parsing the definition.
kibidev
force-pushed
the
ulog_timestamp_can_have_nonzero_index
branch
from
3452b87
to
c1549fe
Compare
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.
The previous parsing assumed that the timestamp for a ulog data series was always at index 0, which is often, but not necessarily the case. The parser now store the correct index when parsing the definition.