Timestamp precision is not clamped to 6 digits #10
Labels
bug
Something isn't working
Comments
kortemik
added a commit
to kortemik/jla_01
that referenced
this issue
Dec 4, 2024
kortemik
added a commit
to teragrep/jla_01
that referenced
this issue
Dec 4, 2024
* use timestamp.toEpochMilli() instead of Instant to avoid teragrep/rlo_14#10 * test that timestamp matches to an expected pattern
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Using too precise timestamps for event makes it malformed as spec only allows up to 6 digits
Expected behavior
https://www.rfc-editor.org/rfc/rfc5424.html#section-6 RFC5424 says
TIME-SECFRAC = "." 1*6DIGITHow to reproduce
Use too precise timestamps with more than 6 digits of fractions, for example using
Instant.now()Screenshots
Software version
1.0.1
Desktop (please complete the following information if relevant):
Additional context
The text was updated successfully, but these errors were encountered: