force order switches every time
Posted: August 24th, 2013, 7:29 pm
Version: 0.7.14
OS: OSX 10.8.4
Firewall Software: None
Are you using IPV6? No
Is the issue reproducible? yes
Every time I turn on Sabnzbd the order of everything in my force queue switches (bottom to top). My high, normal, & low stay the in their correct order.
I do NOT have the 'sort by age' box checked
It was like this in the previous release too (0.7.13 I assume), and potentially earlier. It isn't the hugest bother, but if it's an easy fix I'd like to take care of it, it can be annoying.
It doesn't look like there is anything about it in the log, here is me quitting then opening the program:
2013-08-24 17:24:47,360::INFO::[_cplogging:55] [24/Aug/2013:17:24:47] ENGINE Bus STOPPING
2013-08-24 17:24:47,366::INFO::[_cplogging:55] [24/Aug/2013:17:24:47] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('127.0.0.1', 8085)) shut down
2013-08-24 17:24:47,385::INFO::[_cplogging:55] [24/Aug/2013:17:24:47] ENGINE Stopped thread '_TimeoutMonitor'.
2013-08-24 17:24:47,385::INFO::[_cplogging:55] [24/Aug/2013:17:24:47] ENGINE Bus STOPPED
2013-08-24 17:24:47,385::INFO::[_cplogging:55] [24/Aug/2013:17:24:47] ENGINE Bus EXITING
2013-08-24 17:24:47,385::INFO::[_cplogging:55] [24/Aug/2013:17:24:47] ENGINE Bus EXITED
2013-08-24 17:25:02,073::INFO::[_cplogging:55] [24/Aug/2013:17:25:02] ENGINE Bus STARTING
2013-08-24 17:25:02,076::INFO::[_cplogging:55] [24/Aug/2013:17:25:02] ENGINE Started monitor thread '_TimeoutMonitor'.
2013-08-24 17:25:02,179::INFO::[_cplogging:55] [24/Aug/2013:17:25:02] ENGINE Serving on 127.0.0.1:8085
2013-08-24 17:25:02,179::INFO::[_cplogging:55] [24/Aug/2013:17:25:02] ENGINE Bus STARTED
Thanks
OS: OSX 10.8.4
Firewall Software: None
Are you using IPV6? No
Is the issue reproducible? yes
Every time I turn on Sabnzbd the order of everything in my force queue switches (bottom to top). My high, normal, & low stay the in their correct order.
I do NOT have the 'sort by age' box checked
It was like this in the previous release too (0.7.13 I assume), and potentially earlier. It isn't the hugest bother, but if it's an easy fix I'd like to take care of it, it can be annoying.
It doesn't look like there is anything about it in the log, here is me quitting then opening the program:
2013-08-24 17:24:47,360::INFO::[_cplogging:55] [24/Aug/2013:17:24:47] ENGINE Bus STOPPING
2013-08-24 17:24:47,366::INFO::[_cplogging:55] [24/Aug/2013:17:24:47] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('127.0.0.1', 8085)) shut down
2013-08-24 17:24:47,385::INFO::[_cplogging:55] [24/Aug/2013:17:24:47] ENGINE Stopped thread '_TimeoutMonitor'.
2013-08-24 17:24:47,385::INFO::[_cplogging:55] [24/Aug/2013:17:24:47] ENGINE Bus STOPPED
2013-08-24 17:24:47,385::INFO::[_cplogging:55] [24/Aug/2013:17:24:47] ENGINE Bus EXITING
2013-08-24 17:24:47,385::INFO::[_cplogging:55] [24/Aug/2013:17:24:47] ENGINE Bus EXITED
2013-08-24 17:25:02,073::INFO::[_cplogging:55] [24/Aug/2013:17:25:02] ENGINE Bus STARTING
2013-08-24 17:25:02,076::INFO::[_cplogging:55] [24/Aug/2013:17:25:02] ENGINE Started monitor thread '_TimeoutMonitor'.
2013-08-24 17:25:02,179::INFO::[_cplogging:55] [24/Aug/2013:17:25:02] ENGINE Serving on 127.0.0.1:8085
2013-08-24 17:25:02,179::INFO::[_cplogging:55] [24/Aug/2013:17:25:02] ENGINE Bus STARTED
Thanks