Roundup Tracker - Issues


Author kowey
Recipients kowey
Date 2010-10-15.13:56:29
Message-id <>
We have some software which sits behind our version control repository
and which notifies roundup via the email gateway when certain kinds of
commits have been made.  It is frequently the case that several of these
emails are sent out in quick succession (as this process is automated)

Recently, we've been getting error messages of this sort:
An unexpected error occurred during the processing                     
of your message. The tracker administrator is being                    
Traceback (most recent call last):                                     
  File "/usr/lib/pymodules/python2.5/roundup/", line 738, in
    return self.handle_message(message)                                
  File "/usr/lib/pymodules/python2.5/roundup/", line 794, in
    return self._handle_message (message)                              
  File "/usr/lib/pymodules/python2.5/roundup/", line 1369, in
    cl.set(nodeid, **props)                                            
  File "/usr/lib/pymodules/python2.5/roundup/backends/",
line 1606, in set                                                    
    propvalues = self.set_inner(nodeid, **propvalues)                  
  File "/usr/lib/pymodules/python2.5/roundup/backends/",
line 1816, in set_inner                                              
    self.db.setnode(self.classname, nodeid, propvalues,
  File "/usr/lib/pymodules/python2.5/roundup/backends/",
line 933, in setnode                                                 
    self.sql(sql, vals)                                                
  File "/usr/lib/pymodules/python2.5/roundup/backends/",
line 159, in sql                                                     
    self.cursor.execute(sql, args)                                     
ProgrammingError: ERROR:  could not serialize access due to concurrent
update _issue set _activity='2010-10-15
13:14:44.653',_actor=1837,_resolvedin=2,_status=8 where id=1942 

Strangely it seems that the change we want to make takes effect anyway.

See also and the attached mail that our
auto-updater tries to send
Date User Action Args
2010-10-15 13:56:31koweysetrecipients: + kowey
2010-10-15 13:56:31koweysetmessageid: <>
2010-10-15 13:56:31koweylinkissue2550671 messages
2010-10-15 13:56:29koweycreate