#3028: "Force Recheck" menu option is an acceptance of bugginess
---------------------+------------------------------------
Reporter: qengho | Owner:
Type: bug | Status: new
Priority: minor | Milestone: needs verified
Component: Unknown | Version: other (please specify)
Keywords: |
---------------------+------------------------------------
"Force Recheck" shouldn't exist. If Deluge and its underlying technology
worked as advertized, then there would be nothing to check.
As it is, I work on a filesystem with block-level checksums (so I am
certain my disks are not flipping bits), and every torrent is claimed to
download successfully, run their post-download move trigger, and then
stop.
About 1/5th of the time, running "Force Recheck" discovers some problem,
and Deluge then restarts the download phase at about 90%.
That shouldn't happen.
Moreover, there should be no "Force Recheck" button at all. That is an
excuse for shrugging the burden of broken software behavior off onto the
user. If libtorrent or deluge worked, then there would be no reason to
recheck.
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/3028>
Deluge <http://deluge-torrent.org/>
Deluge Project
--
You received this message because you are subscribed to the Google Groups
"Deluge Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/deluge-dev.
For more options, visit https://groups.google.com/d/optout.
