-
Notifications
You must be signed in to change notification settings - Fork 34
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
Problem with timestamp formatting #621
Milestone
Comments
andrus
added a commit
that referenced
this issue
Mar 19, 2023
andrus
added a commit
that referenced
this issue
Mar 19, 2023
attempt to get rid of custom DateTimeFormatters
Yeah, the use of custom DateTimeFormatter was the culprit. I switched the entire framework to the standard ISO formatters from the JDK. The error no longer occurs. Since this is a somewhat invasive change, it is 5.0 only. My general recommendation would be to avoid |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I’ve bumped into some issues related to AgRest time formatting. That time is too far away from unix epoch, time formatting becomes strange (e.g. adds random time to results). For usual dates, like full 20th century seems to work fine, Problem starts when it comes deeper into past:
I’ve created tests to visualise it (note that it might return different results in different local timezone. I use CET ):
Problem most likely is in
io.agrest.encoder.ISODateTimeEncoder
line:I blame this conversion via ofEpochMilli but honestly didn’t test it too deep.
(we still have v 4.10)
The text was updated successfully, but these errors were encountered: