mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #703] Init fails when an unrecognized/invalid data/index.json is present in data directory root #3464
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#3464
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 @dohlin on GitHub (Apr 12, 2021).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/703
Describe the bug
Running
docker-compose run archivebox init --setup(before and after upgrade from 0.5.6 to 0.6.0) results in a crash/traceback messageSteps to reproduce
Run
docker-compose run archivebox init --setup. Same behavior noticed before and after upgrade from 0.5.6 to 0.6.0Screenshots or log output
This is from after the upgrade to 0.6.0, but the end result is the same as 0.5.6.
ArchiveBox version
Thoughts on why this is crashing and what I can do to fix it?
@pirate commented on GitHub (Apr 12, 2021):
According to this line in the output:
Looks like you have a rogue
index.jsonfile in the root of your data folder that it's trying to parse as an old v0.4.x archive main index.The reason it's failing is because that file is not actually a valid main index file according to ArchiveBox, perhaps it got added by accident or it's a static export you generated with
archivebox listand not an old main index file?Can you rename or move that file somewhere else and try again?
I also just added a case to catch this in the code and show a better error message instead of blocking the
init:50b341b. You can use early before the next release by changing yourdocker-compose.ymlto use theimage: archivebox/archivebox:devcontainer.@dohlin commented on GitHub (Apr 12, 2021):
Sure enough, that worked. Thank you!!