mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #428] Bugfix: Inconsistent timezones in output #1798
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#1798
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pigmonkey on GitHub (Aug 7, 2020).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/428
I installed v0.4.11 and added new URLs from my Pinboard export:
The first timestamp (10:13:29) is in my system's localtime. The second timestamp (17:57:07) is not, in fact, 7 hours later. It is 2 minutes later, but in UTC.
I don't have a strong preference for which of the two timezones ArchiveBox should use in its output, but I do have a strong preference for consistency. Indicating the offset for whichever timezone is used would also be great.
@pirate commented on GitHub (Aug 11, 2020):
@pigmonkey try on the latest master version I think we've fixed it to be UTC everywhere.
@pirate commented on GitHub (Aug 14, 2020):
If you still see any issues comment back and I'll reopen this.
@pigmonkey commented on GitHub (Aug 16, 2020):
Yes, that fixed it. The timestamps are all UTC now in v0.4.14. Thanks!