I've noticed in last versions that scheduler doesn't really work as it should - sometimes it get's
stuck at a speed from past and it doesn't change when it has to.

Today I noticed something more odd:
http://www.shrani.si/f/1C/bY/4iOipqB9/ktorr.jpg

This is a screenshot showing 70 / un. speed, but I don't have it my schedule at all.

Usually reloading the plugin on clearing and reloading the schedule helps, but only for some time.
It goes berserk after e.g. a day.

NOTE: I noticed this problem even before svn rev. 1010699, but I didn't use scheduler from the start of 3.x series, so I don't know if it was working deeper in the past or not.

Will check it out, probably a minor bug.

Can you send me your log file after you get this again ?

Happened again, log is 8MB. Where can I send it, or are there specific messages that you are interrested
and they can be extracted to reduce size?

Today in the morning the speed was 100 KBps / 20 KBps, which is the ktorrent max dl/ul speed defined in config.

Ok, I think only this is relevant:

Code: Select all

Fri Aug 21 01:24:50 2009: Started update timer
Fri Aug 21 01:24:50 2009: Changing schedule to : 80 down, 20 up
Fri Aug 21 01:24:50 2009: Qt Warning: Calling appendChild() on a null node does nothing.
Fri Aug 21 01:24:50 2009: Loading Anti-P2P filter...
Fri Aug 21 01:24:50 2009: AntiP2P header loaded.
Fri Aug 21 01:24:50 2009: Qt Warning: Calling appendChild() on a null node does nothing.
Fri Aug 21 01:24:51 2009: Qt Warning: Calling appendChild() on a null node does nothing.
Fri Aug 21 01:24:51 2009: Qt Warning: Calling appendChild() on a null node does nothing.
Fri Aug 21 01:24:51 2009: Downloading XML file http://192.168.2.1:5000/rootDesc.xml
Fri Aug 21 01:24:51 2009: Trying to find UPnP devices on the local network
Fri Aug 21 01:24:51 2009: Qt Warning: Calling appendChild() on a null node does nothing.
Fri Aug 21 01:24:51 2009: Starting minimized
Fri Aug 21 01:25:53 2009: Changing schedule to : 80 down, 20 up
Fri Aug 21 02:59:59 2009: Changing schedule to normal values : 100 down, 20 up
Fri Aug 21 04:34:05 2009: Changing schedule to : 120 down, 30 up
Fri Aug 21 07:59:59 2009: Changing schedule to normal values : 100 down, 20 up


I don't know why it changes normal values, schedule s full:

I can reproduce the problem, will fix it.

OK it has been fixed