Ensure millis precision in timestamps of outgoing messages #368
+70
−1
Conversation
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
ISO8601 does not specify that fractional seconds shall be omitted if given. Enforce that an on full seconds, the millis resolution is retained for outgoing messages and that incoming messages of any precision can be parsed. On incoming messages with... * ...seconds precision, assume that millis are zero. * ...millis precision, assume that micros are zero. * ...micros precision, assume that nanos are zero. This retains proper timestamp comparison.
Closed
TVolden
approved these changes
Dec 5, 2025
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.
ISO8601 does not specify that fractional seconds shall be omitted if given. Enforce that an on full seconds, the millis resolution is retained for outgoing messages and that incoming messages of any precision can be parsed.
On incoming messages with...
This retains proper timestamp comparison.