There seems, to me at least, there's something wrong with the timestamps of a collection's update times: the "start_updatetime and "last_update_time" fields seem to be legit Unix timestamps
when converted to normal DateTime, the year is +50000, way beyond the epoch of the Dune series of Frank Herbert, and the last update time comes years after the start update time, which is preposterous given the duration of 1 lifetime.
these results^ were the same with 2 online datetime converters, one of which is in the image
Steps to Reproduce
tried to convert the timestamps into normal DateTimes
obtained year 50 thousand and small change, and strange moments (years of Updating)
Expected Behavior
Something credible, like year 2024, and the beginning time relatively close (hours, days) to the end time(s).
Your Environment
GPT4All version (if applicable): v3.2.1 (the database was created with this version of the program)
Operating System: Windows 10 Pro
Chat model used (if applicable):
The ISO 8601 format for datetime is widely used, functional, suggestive/clear, logical, familiar to, like, humans, and handy.
SINAPSA-IC
commented
1 day ago
There seems, to me at least, there's something wrong with the timestamps of a collection's update times: the "start_updatetime and "last_update_time" fields seem to be legit Unix timestamps
Steps to Reproduce
Expected Behavior
Something credible, like year 2024, and the beginning time relatively close (hours, days) to the end time(s).
Your Environment
The ISO 8601 format for datetime is widely used, functional, suggestive/clear, logical, familiar to, like, humans, and handy.