Add Webkit / Chromium epoch format function #3549
Conversation
Nirusu
force-pushed
the
feat/webkit-time
branch
from
91475fc to
a926507
Compare
|
Thanks @Nirusu, this looks useful. 😄 @sqlitebrowser/developers Anyone up for reviewing this? It looks like a simple change. 😄 If it passes review, we can probably include it in the 3.13 release too. |
|
Thanks @lucydodo. Merged. 😄 |
|
@lucydodo It looks like something weird is going wrong with the build: It doesn't seem to be a problem with the PR itself, and our GitHub Runners are all online. Any ideas? Note that this is not urgent, as it could just be some GitHub infrastructure issue that fixes itself in a few hours. We can just try the build again tonight and see if it works. 😄 |
|
This is probably a temporary issue. I've restarted the CI job, let's wait and see. :) |
|
Well, since it's still failing, it looks like something else is going on. However, the nightly build job we ran this morning had no problems, so I'll wait until tomorrow and see what I can do if it still happens. As a note, the only part that's failing is the temporary artifact removal action, so the release itself is fine: |
|
Yeah, it's probably some kind of infrastructure issue. 😄 |
3 participants
This adds formatting options for WebKit time (also used by Chrome / Chromium-based browsers).
For me, this was useful while I was doing some forensic works having to look at Chrome's SQLite3 history file, so I thought maybe I can just contribute it here and get it upstreamed.
Some information about WebKit time:
WebKit epoch are microseconds from 1601-01-01 00:00 UTC to now.
This can map to UNIX time by converting them to seconds (
/ 1e6) and then subtracting the offset between the two start dates (11644473600).Hence, we just convert the time to an UNIX epoch and let
datetimehandle the rest of the conversion.