mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 09:06:02 +03:00
[GH-ISSUE #1511] Bug: Migration to 0.8.3-rc results in "Created at" timestamps to all be modified against the present time the migration happened #2402
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#2402
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 @jessienab on GitHub (Sep 6, 2024).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1511
Describe the bug
Following a migration to 0.8.3, all Created At timestamps for 0.8.3 prior snapshots reflect the actual timestamp of when the migration happened, rather than the imported date/time the snapshot was actually taken.
Steps to reproduce
Screenshots or log output
There is a warning on older entries pre 0.8.3
ArchiveBox version
@pirate commented on GitHub (Sep 6, 2024):
Created_at and modified_at are new fields on Snapshot, so it makes sense that they got default fresh values, however I should probably copy over the old values from
.added/.updatedin the migration. Will fix it@sclu1034 commented on GitHub (Sep 11, 2024):
In case someone (*innocent look*) were to run into this with their live data, and was to lazy to pick out the correct backup snapshot to restore, here's a quick
jqfilter to pick data fromindex.jsoninto SQL commands:@pirate commented on GitHub (Sep 12, 2024):
@sclu1034 thats actually a great idea, i might take inspiration from you and use the index.json to fix several potential edge cases with the recent (fairly complex) migrations.