mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 09:06:02 +03:00
[GH-ISSUE #145] KeyError: 'title' when importing Firefox History #3118
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#3118
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 @nicolaschan on GitHub (Feb 18, 2019).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/145
Describe the bug
When parsing
firefox_history.json, the parser runs into a KeyError, because some entries might not have a title field.Steps to reproduce
Steps to reproduce the behavior:
./archiveon itScreenshots or log output
If applicable, use screenshots or copy/pasted terminal output to help explain your problem.
Here is an example of one such entry from my
firefox_history.json:Software versions (please complete the following information):
74b99fe9ebPython 3.6.7
Linux 4.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux
Chromium 71.0.3578.98 Built on Ubuntu , running on Ubuntu 18.04
@pirate commented on GitHub (Feb 19, 2019):
Fixed in latest master (
bb5879a). Give it a try, and comment back if it's still not working. Thanks for reporting this!