mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #157] Failed to archive link: KeyError: 'base_url' #1619
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#1619
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 @raman325 on GitHub (Mar 2, 2019).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/157
Describe the bug
On every URL being archived, all archive steps seem to be successful but then I get this error before moving on to the next URL. I am using Pinboard's GET posts API which appears to give the same output as exporting from Pinboard directly:
curl "https://api.pinboard.in/v1/posts/all?auth_token=<user>:<token>"The end result is that the output.html of the page works, but the index.html does not (index.json has content though).Steps to reproduce
Steps to reproduce the behavior:
Screenshots or log output
Software versions (please complete the following information):
63e6ed8)@pirate commented on GitHub (Mar 3, 2019):
Ah sorry, this was a bug from a recent refactor. Just fixed it in
14e66a6.Pull the latest master and give it a try, comment back if it doesn't work and I'll reopen the ticket.
@raman325 commented on GitHub (Mar 4, 2019):
Looks like that did the trick, thanks!