Page 1 of 1

Error in error-handling finished job

Posted: October 26th, 2010, 6:12 am
by lennardw
I found this minor error by accident.
One of my downloads was almost finished, and I wanted to check the details of it. By the time I clicked on it, the download had finished, but the Web GUI wasn't updated (refreshed) yet. I got the following error message:

Code: Select all

Traceback (most recent call last):
  File "/home/sabnzbd/SABnzbd-0.5.4/cherrypy/_cprequest.py", line 618, in respond
    cherrypy.response.body = self.handler()
  File "/home/sabnzbd/SABnzbd-0.5.4/cherrypy/_cpdispatch.py", line 25, in __call__
    return self.callable(*self.args, **self.kwargs)
  File "/home/sabnzbd/SABnzbd-0.5.4/sabnzbd/interface.py", line 987, in default
    return template.respond()
  File "_home_sabnzbd_sabnzbd_interfaces_Plush_templates_nzo_tmpl.py", line 151, in respond
NotFound: cannot find 'filename' while searching for 'slot.filename'
Might be nice to have this in a clean error or message....

[[EDIT]]
Let me add some extra info. (don't think it's importand in this case, but I'm not a python coder, so who knows :) )
I'm using SABnzbd 0.5.4 with python2.6 on a Centos 5.5 virtual machine (LVM)

[[EDIT 2]] (sorry, didn't read the guidelines)
Version: 0.5.4
OS: Linux Centos 5.5
Install-type: Python source
Skin (if applicable): Plush
Firewall Software: None (and irrelevant in this case)
Are you using IPV6? No
Is the issue reproducible? Yes

Re: Error in error-handling finished job

Posted: October 26th, 2010, 7:32 am
by shypike
It's a side effect of the way we use the internal webserver framework.
It's caused by the lack of synchronisation between the engine and the web UI.
It's very hard to fix this and even hard to display a better error message.
Since it does no harm (except puzzling the user) we decided not to fix this.
We may pick this up later though.

Re: Error in error-handling finished job

Posted: October 26th, 2010, 10:58 am
by lennardw
Yes I had a feeling about that personally ;)
I couldn't emagine you guys didn't run into it once or twice whilst testing.

Thanks for the quick response though!