mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #458] Exception in archive_methods.save_readability #3324
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#3324
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 @jrruethe on GitHub (Aug 26, 2020).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/458
When attempting to archive this link with Readability enabled, the following exception occurs.
From what I can tell so far, I think the exception occurs somewhere in here before
cmdis instantiated here, which means thatcmddoesn't exist after the exception is caught and control makes it down to here.This is with Docker image
nikisweeting/archivebox:0.4.21@cdvv7788 commented on GitHub (Aug 26, 2020):
Thanks for the report. I will check it.
@cdvv7788 commented on GitHub (Aug 27, 2020):
@jrruethe I sent a PR. A new version with the fix should come out next week. You can try the fix by using that branch directly for now.
@jrruethe commented on GitHub (Aug 27, 2020):
Thank you very much!
@pirate commented on GitHub (Sep 1, 2020):
This should be fixed now on
master. If you still encounter any issues comment back here and I'll reopen the ticket.To use
masterimmediately without waiting for the next release you can build it directly from Github: