sensor_data_sharing_service: Cannot parse timestamp in milliseconds #429
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.
PR Details
Description
Data sensor sharing service receives timestamp in unit of millisecond, parses and returns the result as an unsigned int data type. This data type maximum value is smaller than the timestamp value, which cause the original timestamp value to be lost.
Create another separate function to parse long data type. Parse timestamp using long data type.
Related GitHub Issue
Related Jira Key
https://usdot-carma.atlassian.net/browse/FCP-30
Motivation and Context
NA
How Has This Been Tested?
NA
Types of changes
Checklist: