-
Notifications
You must be signed in to change notification settings - Fork 97
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
Add MsgMeasurementPoint [AP-653] #1388
Conversation
babc7c4
to
0ab7335
Compare
718003c
to
ae709c5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
"slice_time": 261963842, "line": 18, "func": "route()\u0000", | ||
"payload": "+gcAALQAAgAAACgAAACCyZSNYVUAABKCyZQAAAAAQkCdDwAAAAASAHJvdXRlKCkA" | ||
}' | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: this new line seems unnecessary.
ae709c5
to
0bae518
Compare
0bae518
to
e05062e
Compare
Quality Gate passed for 'libsbp-c'The SonarCloud Quality Gate passed, but some issues were introduced. 2 New issues |
Description
@swift-nav/devinfra
Create a new message to output profiling information from measurement points.
Current version of some product will output measurement point profiling information in the LinuxCPUState message making use of the
cmdline
field to serialise various bits of information. Some other bits of information are placed in to the other fields in LinuxCpuState but since the fields are already defined the names are misleading.This PR introduces a dedicated message which contains the same information as is currently sent but broken out in to fields with the correct types. This removes the need to serialise/deserialise this information once products are updated to use this message instead.
API compatibility
Does this change introduce a API compatibility risk?
No
API compatibility plan
If the above is "Yes", please detail the compatibility (or migration) plan:
No
JIRA Reference
https://swift-nav.atlassian.net/browse/AP-653