v3.2.1: localdocs_v2 database: weird timestamps in the "collections" table

[SINAPSA-IC]

trafficstars

There seems, to me at least, there's something wrong with the timestamps of a collection's update times: the "start_update_time_ 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]

[cebtenzzre]

These are obviously ms-precision Unix timestamps:

$ date -d '@1725380892.008'
Tue Sep  3 12:28:12 EDT 2024