Trac detected an internal error while getting a report

[andre.beltman@…]

I am using the private tickets plugin. Using any pre-defined report I always get an internal error:

---

Oops… Trac detected an internal error:

If you think this really should work and you can reproduce it, you should consider reporting this problem to the Trac team.

Go to ​http://trac.edgewall.org/ and create a new ticket where you describe the problem, how to reproduce it. Don't forget to include the Python traceback found below.

TracGuide — The Trac User and Administration Guide Python Traceback

Traceback (most recent call last):

File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 387, in dispatch_request

dispatcher.dispatch(req)

File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 239, in dispatch

template, content_type = self._post_process_request(req,

File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 269, in _post_process_request

content_type)

File "/usr/lib/python2.3/site-packages/TracPrivateTickets-1.1.1-py2.3.egg/privatetickets/report.py", line 35, in post_process_request

id = req.hdf['report.items.%s.ticket'%i]

File "/usr/lib/python2.3/site-packages/trac/web/clearsilver.py", line 157, in getitem

raise KeyError, name

KeyError: 'report.items.0.ticket'

Download in other formats:

• RSS Feed
• Comma-delimited Text
• Tab-delimited Text

Trac Powered

Powered by Trac 0.10.3 By Edgewall Software.

Visit the Trac open source project at ​http://trac.edgewall.org/

[Jeroen Ruigrok van der Werven]

Upon reading this I think you should file the ticket at:

​http://trac-hacks.org/newticket?component=PrivateTicketsPlugin&owner=coderanger

Since it looks like a problem with the privateticketsplugin, not Trac. Lets see what Noah says about this (reassigning to him).

[Noah Kantrowitz]

First off I only test on 0.10.4 for 0.10 plugins. Second, probably just some edge case I didn't account for. Third, chances are I won't fix this if it is a bug, as I will soon be porting the plugin to 0.11 with the new security API.

[cmsupport@…]

This ticket was submitted by one of our customers (we provide ready configured svn/trac servers together with support on the tooling, and expert advice/support on configuration management and quality assurance).

He had created his own set of queries replacing the default ones in Trac. After that we configured and enabled the private ticket plugin since he wanted to allow his client to see the client tickets. Then the queries failed for the private user. Together with him we drilled down to the statement in the query that causes it. "id AS id" was used instead of the default "id AS ticket". "id AS id" works for all users except the private user when the private ticket plugin is enabled.

Is it possbile to check if this problem still exists in the upcoming ported version for 0.11? We have a work around for it so we can easily wait for a stable version for 0.11.

We're using TracPrivateTickets 1.1.1 on Trac 0.10.3 on a Redhat Enterprise Linux 4ES server with mod_python 3.3.1.

Frits van der Holst
ICTNoviQ
CMaaS (Configuration Management as a Service)
CMaaS Support Desk (cmsupport AT ictnoviq.nl)

[Christian Boos]

Nevertheless, the particular details of that plugin are dealt with elsewhere (see comment:1), so this is not the proper place to discuss issues with that plugin.

For more about that capability in Trac 0.11 itself, see #3466 and #1316.