Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hash check on completion #8390

Closed
teddyrogers opened this issue Jan 15, 2025 · 3 comments · Fixed by #8449
Closed

Hash check on completion #8390

teddyrogers opened this issue Jan 15, 2025 · 3 comments · Fixed by #8449
Assignees
Milestone

Comments

@teddyrogers
Copy link

teddyrogers commented Jan 15, 2025

Tribler 8.0.7, feature request, on completion of a download it would be good to have an option, in settings, to complete a hash check on the torrent.

On a couple of torrents, that have completed and seeding at 100%, I forced a hash recheck and noticed the files were not really 100% complete. This could be related to issue #8382. However, it highlights having the option to complete hash checks on completion could identify missed or partially downloaded pieces. This may also help to prevent invalid pieces being sent out to peers.

@qstokkink qstokkink added this to the 8.1.0 milestone Jan 16, 2025
@qstokkink

This comment has been minimized.

@absolutep
Copy link

having the option to complete hash checks on completion

This feature is already present in BiglyBT and it lead to BiglyBT being a huge resource hog [Disk usage 100% and RAM].

Image

I had to disable it for BiglyBT to perform normally.

I think it is far better to force recheck torrents ourselves when we have time.

@qstokkink
Copy link
Contributor

Oops, I posted my earlier comment on the wrong issue 👴

What we can do for this issue is simply create a new config flag, defaulting to "off" (because of @absolutep's advice above). When we receive a "torrent finished" alert, we can then force a recheck here:

def on_torrent_finished_alert(self, alert: lt.torrent_finished_alert) -> None:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

3 participants