Option to cancel verification / repair

Want something added? Ask for it here.
Post Reply
barabbas
Release Testers
Release Testers
Posts: 15
Joined: July 11th, 2009, 5:03 am

Option to cancel verification / repair

Post by barabbas »

Sometimes after downloading something SABbnzbd will take forever to verify or try repairing something that I know (by that time) that the download cannot be repaired. For example when downloading a season of something and it will fail verifying the first episode I look into the temp folder and the files are too small. So I'd like to cancel the post processing and delete the temp files.

Yes, I know I can shutdown SABnzbd and delete the files, but that's not really a comfortable solution. I guess implementing this wouldn't take too much effort. Kill the PAR2 process and delete the files. Done.

Thank you so much for your time.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Option to cancel verification / repair

Post by shypike »

barabbas wrote: I guess implementing this wouldn't take too much effort. Kill the PAR2 process and delete the files.
Given that SABnzbd is a multi-platform application, it's quite a bit of work.
You can lookup the par2 process in the Windows task manager and kill it yourself.
barabbas
Release Testers
Release Testers
Posts: 15
Joined: July 11th, 2009, 5:03 am

Re: Option to cancel verification / repair

Post by barabbas »

Sorry, might've underestimated how complicated this would be. I never used python, but in Java or C#/Mono I would start a process and let the interpreter do the rest. Killing the process would work on any system just by calling p.abort() or something. Using the Task Manager will have to to. Thanks for your reply!
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Option to cancel verification / repair

Post by shypike »

The Python library has send_signal and abort commands for sub-processes.
That would be an easy solution.
However, that would also mean that we must drop support for Python 2.5.
We're not ready for that yet, especially since the Windows binary is still based on it.
Post Reply