BUG: "Do not download" of simple files

[lucskos]

Hi,

I just couldn't figure out where should be the bugreports sent to, probably here is ok.

The Files TAB on the bottom does not work as expected if you download a torrent which has only one file without directory. If you set it to "do not download" (because you just like to dl it partially and seeding), nothing happens, it will be downloaded entirely.

Deluge 1.1.9 (debian unstable)

[johnnyg]

creating a bug report is called creating a "ticket" and can be done here: http://dev.deluge-torrent.org/newticket

selective downloading requires full allocation, do you have it enabled?

[lucskos]

thx, i'll create the ticket.

Yes, of course full allocation is enabled. Actually it has no drawbacks on *nix, since the sparse file feature of most filesystems saves space.

[g0nad]

I too see this bug.

I started a torrent that contained four files. I only wanted one and set the other three to 'Do Not Download'. I got the file I wanted and in addition to that I got 0.66% of one of the 'Do Not Download' files.

Use Full Allocation is set.

I installed deluge 35 minutes ago, so from install to bug_found was pretty fast.

I do have to say that deluge looks pretty slick

[g0nad]

Just to confirm I removed that torrent and data and readded it with the same selection, exactly the same result.

[loki]

I too see this bug.

I started a torrent that contained four files. I only wanted one and set the other three to 'Do Not Download'. I got the file I wanted and in addition to that I got 0.66% of one of the 'Do Not Download' files.

Use Full Allocation is set.

I installed deluge 35 minutes ago, so from install to bug_found was pretty fast.

I do have to say that deluge looks pretty slick

Your specific 'bug' is not really a bug but just the way torrents work.
Please read the FAQ: http://dev.deluge-torrent.org/wiki/Faq# ... wnload.Why

[g0nad]

Thanks for the link.

It is a bug. Instead of getting it behave how the user would expect there's a FAQ entry essentially telling users to lump it.

If a file is not requested by the user it should not be created.

[loki]

It's not a bug if there's nothing that can be done about it, all other torrent programs suffer from this same so called 'bug'

[g0nad]

if file_selected[0] -> discard data (/dev/null, whatever)
if file_selected[1] -> write to file
else implode

Radically oversimplified and in an imaginary language, but it certainly isn't impossible to come up with a solution to this problem.

(I've got utorrent kicking round, I'll refresh my memory and test out its behavior - can't say I've seen it do the same)

[johnnyg]

Did you read the link?
The problem is when pieces span multiple files: you need part of the piece for the file you want but the other part of the piece causes the other file to be created.
It's a limitation of the bittorrent protocol.
The way utorrent handles it is that it groups the additional data under a different name and possibly sends it to the trash when you remove the torrent (it's been awhile since I've used utorrent).