Adding comment to Ticket results in traceback

[Torsten Landschoff <torsten.landschoff@…>]

Hi!

Sorry for reporting this as a ticket, but it is the fastest way to have it recorded and perhaps somebody else has run into it. When changing one specific ticket, I get the following traceback:

Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/trac/web/api.py", line 339, in send_error
    'text/html')
  File "/usr/lib/python2.5/site-packages/trac/web/chrome.py", line 684, in render_template
    data = self.populate_data(req, data)
  File "/usr/lib/python2.5/site-packages/trac/web/chrome.py", line 592, in populate_data
    d['chrome'].update(req.chrome)
  File "/usr/lib/python2.5/site-packages/trac/web/api.py", line 169, in __getattr__
    value = self.callbacks[name](self)
  File "/usr/lib/python2.5/site-packages/trac/web/chrome.py", line 460, in prepare_request
    for category, name, text in contributor.get_navigation_items(req):
  File "/usr/lib/python2.5/site-packages/Bitten-0.6dev_r881-py2.5.egg/bitten/web_ui.py", line 98, in get_navigation_items
    include_inactive=False):
  File "/usr/lib/python2.5/site-packages/Bitten-0.6dev_r881-py2.5.egg/bitten/model.py", line 176, in select
    cursor.execute("SELECT name,path,active,recipe,min_rev,max_rev,"
  File "/usr/lib/python2.5/site-packages/trac/db/util.py", line 51, in execute
    return self.cursor.execute(sql)
  File "/usr/lib/python2.5/site-packages/trac/db/util.py", line 51, in execute
    return self.cursor.execute(sql)
InternalError: current transaction is aborted, commands ignored until end of transaction block

Interestingly, this is only for a single ticket, others work fine. I do not see how the ticket can affect the generation of the navigation bar. Any idea what's going on here?

[Torsten Landschoff <torsten.landschoff@…>]

As always, just after hitting "Submit", I wonder if this is at all related to Bitten. From the error message, it looks like PostgresSQL had a transaction rollback which was not cleared and bit bitten...

I'll look into it and report back.

[Torsten Landschoff <torsten.landschoff@…>]

Okay, you can disregard this bug, the real problem stems from the ​MasterTicketsPlugin. However, I would expect that an error while accessing the database would be isolated to the offending plugin by trac!?

[Felix Schwarz <felix.schwarz@…>]

The problem occurs when a plugin does something stupid with postgres. Afterwards any SQL access will throw the exception mentioned above. Sometimes trac triggers it even when rendering the error page. So it's partly trac's fault because trac can only display one exception but I think it's unreasonable to expect that trac could isolate plugins from each other within the same request.

[osimons]

Closing. Nothing that can be handled through the Bitten project.