Custom Query (2449 matches)

It has to happen sooner or later.

Python 2.7 is the last major version in the 2.x series: ​http://python.org/download/releases/2.7/

This will also involve ditching setuptools in favour of distribute: ​http://packages.python.org/distribute/

deluge:1.3.0-rc1 libtorrent: 0.14.10.0

Upon transitioning from the scheduler red zone to green, torrents start up again but except for a few which are now in paused mode. How did they get in paused mode?

To be a little more detailed, I think it happens a little like this:

I have 4 torrents, none of which are in paused mode and I am currently in the scheduler's active green zone but I have the queue set to only 2 active like so:

#1 A #2 A #3 Q #4 Q

Upon reaching the red zone the torrents stop but the active ones get assigned a mode of paused so that when the next green zone arrives the lower priority torrents are going instead like so:

#1 P #2 P #3 A #4 A

If it helps to reproduce the bug I am currently starting and stopping deluge client & daemon during each red zone.

The "peers" tab doesn't seem to refresh automatically when viewing a torrents' details in the Web UI.

If I refresh the page manually using F5 then I get a updated speeds but am limited to 13 peers max (currently 19 connected).

I've tried latest versions of Chrome (dev), Firefox and Internet Explorer to view the page. All of them do the same, no automatic updates and 13 peers listed max. I'm running the web ui+daemon on a linux debian box (testing). This bug seems present in the 1.3.0-rc1 tarball and latest git pull.

Speeds updated correctly on 1.2.3 but I could only see 8 peers max. Could this be something to do with how I installed deluge?: I installed the deluged/deluge-web packages and their dependencies from apt then installed the latest git version over the top via setup.py build+install.