mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #298] Question: Chromium Timeout #217
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#217
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 @dataarchivist on GitHub (Nov 20, 2019).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/298
I hoped it will changed it, but the cpu / ram cant stop the timeout errors,
so I wished to increased them. The config (not config.default) are still ignored.
Used the normal git curl.
May it would be a good idea, to increase the timeout by default to ~5 mins?
EDIT: For now I use the config.py and it works perfectly for me.
@pirate commented on GitHub (Nov 20, 2019):
Config handling is massively improved in v0.4, see
archivebox confighere: https://github.com/pirate/ArchiveBox/pull/207 and on the Wiki Roadmap page.If you still have issues with timeout errors after using v0.4 and the new config system, feel free to open a new ticket for that with a paste of your terminal output or a screenshot + config you're using.