mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-26 01:26:00 +03:00
[GH-ISSUE #1018] bug: fails to init --setup #642
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#642
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 @vext01 on GitHub (Sep 1, 2022).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1018
Describe the bug
Initialisation fails.
Steps to reproduce
archivebox init --setupin a new directory.Screenshots or log output
My guess: module name clash
config. That is a very generic name. Will try in a virtualenv next.ArchiveBox version
Latest from pip
@vext01 commented on GitHub (Sep 1, 2022):
Works in a virtualenv
ArchiveResult(output=None, status='skipped')entries pollutinglatest_outputsand showing 0 files in the UI #1908ArchiveResult(output=None, status='skipped')entries pollutinglatest_outputsand showing 0 files in the UI #3418