Hi,

I have been using roundup 0.5.6 for some time now 
without any problems. I recently added a new string field 
to the database schema (in dbinit.py), and used admin 
web login to add allowable values for this new field. 
Then I started going through the existing issues to 
update this new field. The problem is that I get the 
following error when updating some (very unpredictable) 
issues - at which point the issue is corrupt and cannot 
be repaired. I use anydbm as the database. I tried 
upgrading to python 2.2.3 and roundup 0.5.9 but it still 
happens. (I prefer not to move to sqlite for this tracker 
as I guess I would then lose all of the history for 
issues?).

Any help would be greatly appreciated. Please let me 
know if you need any more information.
Thanks,
Paul

Templating Error
Debugging information follows

While evaluating the standard:'context/history' 
expression on line 174 Current variables: 
templates <roundup.cgi.templating.Templates instance 
at 0x015A0DB8> 
repeat <roundup.cgi.PageTemplates.TALES.SafeMapping 
instance at 0x015A1988> 
default <roundup.cgi.PageTemplates.TALES.Default 
instance at 0x009A7DE0> 
db <roundup.cgi.templating.HTMLDatabase instance at 
0x015A1AD8> 
utils <roundup.cgi.templating.utils instance at 
0x015A1B48> 
request <roundup.cgi.templating.HTMLRequest instance 
at 0x015A0C68> 
tracker <module '_roundup_tracker_1' 
from 'f:\odt\roundup\trackers\siren\__init__.pyo'> 
context <HTMLItem(0x15a1bb8) issue 238> 
nothing None 
config <module '_roundup_tracker_1.config' 
from 'f:\odt\roundup\trackers\siren\config.pyo'> 
options {'ok_message': ['client edited 
ok'], 'error_message': []} 
loop <roundup.cgi.PageTemplates.TALES.SafeMapping 
instance at 0x015A1988> 
attrs {'tal:replace': 'structure context/history'} 

A problem occurred in your template "issue.item". 
Full traceback: 
Traceback (most recent call last):
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\client.py", line 440, in 
renderContext
    return pt.render(self, None, None, **args)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\templating.py", line 187, in render
    getEngine().getContext(c), output, tal=1, 
strictinsert=0)()
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\TAL\TALInterpreter.py", line 154, 
in __call__
    self.interpret(self.program)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\TAL\TALInterpreter.py", line 186, 
in interpret
    handlers[opcode](self, args)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\TAL\TALInterpreter.py", line 525, 
in do_useMacro
    self.interpret(macro)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\TAL\TALInterpreter.py", line 186, 
in interpret
    handlers[opcode](self, args)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\TAL\TALInterpreter.py", line 549, 
in do_defineSlot
    self.interpret(slot)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\TAL\TALInterpreter.py", line 186, 
in interpret
    handlers[opcode](self, args)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\TAL\TALInterpreter.py", line 491, 
in do_condition
    self.interpret(block)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\TAL\TALInterpreter.py", line 186, 
in interpret
    handlers[opcode](self, args)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\TAL\TALInterpreter.py", line 345, 
in do_optTag_tal
    self.do_optTag(stuff)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\TAL\TALInterpreter.py", line 330, 
in do_optTag
    return self.no_tag(start, program)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\TAL\TALInterpreter.py", line 325, 
in no_tag
    self.interpret(program)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\TAL\TALInterpreter.py", line 186, 
in interpret
    handlers[opcode](self, args)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\TAL\TALInterpreter.py", line 432, 
in do_insertStructure_tal
    structure = self.engine.evaluateStructure(expr)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\PageTemplates\TALES.py", line 
225, in evaluate
    v = expression(self)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\PageTemplates\Expressions.py", 
line 188, in __call__
    return self._eval(econtext)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\PageTemplates\Expressions.py", 
line 183, in _eval
    return render(ob, econtext.vars)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\PageTemplates\Expressions.py", 
line 89, in render
    ob = ob()
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\cgi\templating.py", line 519, in history
    history = self._klass.history(self._nodeid)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\backends\back_anydbm.py", line 
1359, in history
    return self.db.getjournal(self.classname, nodeid)
  File "C:\ODT02L~1\PROG\PYTHON~1.3\lib\site-
packages\roundup\backends\back_anydbm.py", line 510, 
in getjournal
    raise IndexError, 'no such %s %s'%(classname, 
nodeid)
IndexError: no such issue 238

 

Logged In: YES 
user_id=6405

Sorry it's taken me so long to respond to this (then again, you're 
anonymous, so I don't even know if you'll see this reponse :) 
 
I'm looking into the issue. Off the top of my head, I can't see any reason 
why *some* journal entries would disappear if the only change you've 
made is to add a new property. In the anydbm backend, the mutation of 
the schema has no actual effect on the data stored. It certainly shouldn't 
result in the loss of item journals. 
 
As I said, I'm looking into it, but if you find any other information / 
behaviour that you could supply, please do! 

Logged In: NO 

Thanks for your response. It hasn't happened recently (since 
I updated the new field for all issues). The last time it did 
happen, I found that I could click the back arrow (on 
browser) when the template error page displayed and try 
clicking submit on the same issue again. This time there was 
no error (so I didn't need to retire the issue and re-build it) 
but all of the history had disappeared. 

I am thinking about migrating data to sqlite - is there any way 
of also transferring the history across?

Thanks again,
Paul

P.S. I have to say that roundup is an excellent application - 
we use it quite a bit in our company. Thanks for all of your 
work!

Logged In: YES 
user_id=6405

Sorry, but at the moment database exports don't include the entire 
journal, just the creation and last modified information. The message 
spool is retained though, in case that makes any difference. 

Logged In: YES 
user_id=6405

lease direct further questions to the roundup-users mailing list.