-
Notifications
You must be signed in to change notification settings - Fork 117
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
Negative Duration
does not round-trip properly after v2.12.0 with WRITE_DURATIONS_AS_TIMESTAMPS
enabled
#337
Comments
Here's inlined class from reproduction link from above:
|
And just so it is clear, 2.11 and 2.12 are old unmaintained versions (minus possible security fixes): fix, if any should go in 2.18.x so let's repro with 2.18.2. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I found this similar issue #165 but it seems different, as that user reported a bug on
2.10.2
and refers to a different config option.WRITE_DURATIONS_AS_TIMESTAMPS
defaults to true.Before v2.12.0
WRITE_DURATIONS_AS_TIMESTAMPS
set to true.It seems that a negative value...
v2.12.0 and later (including 2.18.2)
WRITE_DURATIONS_AS_TIMESTAMPS
set to true.It seems that a negative value...
Here is an example repo demonstrating the problem https://github.com/jmuia/jackson-duration-serialization
The text was updated successfully, but these errors were encountered: