Custom Query (2392 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (16 - 18 of 2392)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Ticket Resolution Summary Owner Reporter
#3000 Duplicate 1.3.14 fails to respond properly to choosing which files one wants to download. Prods
Description

1.3.14 fails to respond properly to choosing which files one wants to download from within a torrent.

For example, I start a torrent but only want to download 5 of the 50 files within the torrent so I high-light those I do NOT want and choose "Do Not Download." Note that Deluge 1.3.14 has a lot of difficulty designating the files as "Do Not Download" and several attempts are often necessary...

Expected behaviour is that Deluge will ignore those files designated as "Do Not Download", and only download the files designated as "Normal, High, or Highest" priority.

What occurs: Deluge completely messes it up, and files that are designated "Do Not Download" are downloaded; files that are designated "Normal Priority" etc. are only partially downloaded, or not at all.

Also, if the 50 files have a total size of 50MB, and the files designated "Normal Priority" etc., have a total size of 5MB, the "Size" column will read some random number that is much larger than the expected 5MB. Running a Force ReCheck? does nothing to fix it. It is a total disaster.

Installed via ppa on Xubuntu Xenial. I have confirmed this on both my Xenial systems.

Purged ppa and returned to 1.3.12 and everything works fine.

#2141 Fixed 1.3.5 uses try/except incorrectly in two places stromberg
Description

I believe 1.3.5 uses try/except in a way that fails to catch one of the two listed exceptions, instead overwriting the second exception with detail related to the first. I believe this source of bugs is why try/except's syntax was changed slightly in 3.x.

The syntax is fine, but I doubt it's doing what's intended.

#2142 Fixed 1.3.5 uses try/except incorrectly in two places stromberg
Description

I believe 1.3.5 uses try/except in a way that fails to catch one of the two listed exceptions, instead overwriting the second exception listed with detail related to the first. I believe this source of bugs is why try/except's syntax was changed slightly in Python 3.x.

The syntax is fine, but I doubt it's doing what's intended.

I've attached a diff that fixes the two bad try/except's by simply adding parentheses to form a tuple of exceptions.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Note: See TracQuery for help on using queries.