Zero byte jobs are accepted via rss and api
Posted: April 18th, 2010, 9:56 am
Just got a 0 byte job in the queue, with timeleft/age/size listed as 0:00:00/14717d/0B. Obviously, nothing is downloaded. This 0-byte job doesn't seem to hold up other items in the queue (regardless of whether 'Only Get Articles for Top of Queue' is set or not), and can be removed via the web interface without a problem. But until then, it just stays in the queue. I assume that would prevent the queue from ever reaching a finished state, thus probably interfering with end-of-queue setting etc.
The job resulted from an nzb off nzbs.org, that, when downloaded "manually" via the browser, turns out to be an empty file itself. Adding this empty nzb file to the program's blackhole directory does nothing; it is however accepted when added via rss or by clicking the icon inserted into nzbs.org by duz's firefox plugin (assuming that uses the api somehow). Please prevent such a job from entering/staying in the queue.
Happens on my usual operating system, tested with both the latest public and private sabnzbd+ releases.
The job resulted from an nzb off nzbs.org, that, when downloaded "manually" via the browser, turns out to be an empty file itself. Adding this empty nzb file to the program's blackhole directory does nothing; it is however accepted when added via rss or by clicking the icon inserted into nzbs.org by duz's firefox plugin (assuming that uses the api somehow). Please prevent such a job from entering/staying in the queue.
Happens on my usual operating system, tested with both the latest public and private sabnzbd+ releases.
