by DThor » Thu Jul 07, 2011 8:37 am
My experience with this has led me to believe that 90% of these scenarios come from interference with a download being processed, one way or another. That's probably a good indication that Newsbin probably could use a little better feedback during a couple of stages of processing.
One of the most common is a recent file that's incomplete, but has sufficient pars. Newsbin will wait by default, rather than par fix. You can kick it the correct way, assemble incompletes, or you can start fiddling with it more messily and potentially cause this issue. It's not always immediately obvious why the file is just sitting there, again at some point it would be nice to see this scenario communicate itself a little more clearly, to avoid confusion. I'm personally a fan of 'just clear the queue ', but then I'm not downloading 50G posts either...
DT