Roundup Tracker - Issues

Issue 640310

classification
Traceback entering non-existant supersdr
Type: Severity: normal
Components: Web interface Versions:
process
Status: closed fixed
:
: richard : richard
Priority: normal :

Created on 2002-11-18 21:02 by anonymous, last changed 2002-12-09 23:52 by richard.

Messages
msg510 Author: [hidden] (anonymous) Date: 2002-11-18 21:02
Here's the content of an email from one of my local
Roundup users:

Looks like a typo'd when entering a superseder and it
blew up because the issue I tried to supersede from did
not exist.
Just thought you'd like to see a way that you could
blow it up.

Traceback (most recent call last):
 File
"C:\Python22\lib\site-packages\roundup\cgi\client.py",
line 764, in newItemAction
   nid = self._createnode(props)
 File
"C:\Python22\lib\site-packages\roundup\cgi\client.py",
line 1030, in _createnode
   return cl.create(**props)
 File
"C:\Python22\lib\site-packages\roundup\backends\back_anydbm.py",
line 842, in create
   raise IndexError, '%s has no node %s'%(link_class,
IndexError: issue has no node 292

msg511 Author: [hidden] (richard) Date: 2002-12-09 23:52
Logged In: YES 
user_id=6405

Fixed. Ish. Needs a nicer fix, but at least you won't get a traceback now. 
 
History
Date User Action Args
2002-11-18 21:02:49anonymouscreate