mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #185] TypeError on archive #1639
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#1639
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 @diego898 on GitHub (Mar 21, 2019).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/185
Describe the bug
I tried to save this relatively simple blog post, and got a
TypeError: unsupported operand type(s) for -: 'datetime.datetime' and 'float'errorSteps to reproduce
Steps to reproduce the behavior:
echo "http://www.offconvex.org/2019/03/19/CURL/" | ./archiveScreenshots or log output
Software versions
(please complete the following information)
git rev-parse HEAD | head -c7:d798117@pirate commented on GitHub (Mar 21, 2019):
Yeah sorry about this, pushed a refactor too fast last night without testing thoroughly. I'll have this fixed today.
@hyfen commented on GitHub (Mar 21, 2019):
I also encountered this one just now.
@pirate commented on GitHub (Mar 22, 2019):
@simon987 beat me to the fix. Try it now.
@NullEnt1ty commented on GitHub (Mar 22, 2019):
It seems to work now. Although the application exits with a non-zero code. This is the last output:
Is this intentional?
@simon987 commented on GitHub (Mar 22, 2019):
@NullEnt1ty This is a typo, I made a different PR for that: #187
@n0ncetonic commented on GitHub (Mar 22, 2019):
I recently experienced this but I'm guessing the PR will fix it.
@pirate commented on GitHub (Mar 22, 2019):
Just merged @simon987's PR, thanks for reporting @n0ncetonic and @NullEnt1ty! Comment back if you're still having problems and I'll reopen it.