Error when rendering a ticket page

[tjb@…]

When accessing 1 of our tickets, we see the following python error displayed on the web-browser:

Python Traceback

Traceback (most recent call last):
  File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 283, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 170, in dispatch
    resp = chosen_handler.process_request(req)
  File "/usr/lib/python2.3/site-packages/trac/ticket/web_ui.py", line 219, in process_request
    self._insert_ticket_data(req, db, ticket, reporter_id)
  File "/usr/lib/python2.3/site-packages/trac/ticket/web_ui.py", line 393, in _insert_ticket_data
    req.hdf['ticket'] = ticket.values
  File "/usr/lib/python2.3/site-packages/trac/web/clearsilver.py", line 194, in __setitem__
    self.set_value(name, value, True)
  File "/usr/lib/python2.3/site-packages/trac/web/clearsilver.py", line 236, in set_value
    add_value(name, value)
  File "/usr/lib/python2.3/site-packages/trac/web/clearsilver.py", line 228, in add_value
    add_value('%s.%s' % (prefix, k), value[k])
  File "/usr/lib/python2.3/site-packages/trac/web/clearsilver.py", line 218, in add_value
    self.hdf.setValue(prefix, util.escape(value))
  File "/usr/lib/python2.3/site-packages/trac/util/html.py", line 95, in escape
    text = unicode(text).replace('&', '&') \
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 199: ordinal not in range(128)

Nothing is reported in the apache log.

All of the other tickets seem to work correctly. This has occurred recently - at some point in the past this ticket would display correctly. I am guessing that this may be a unicode related problem (eg #2903)

Our trac server environment is:

• Suse Enterprise Linux 9
• Apache 2.0.49
• trac r3029

[cmlenz]

Actually, this is a duplicate of #2905.

[tjb@…]

This problem had persisted for some time - at least until [3094].

I looked at the text data for the ticket causing the problem, and found an unexpected character (non-ascii) in there. Removing this fixed the problem for me.

There does seem to be a stability problem here (unexpected characters causing failures), but you probably don't need me to tell you that. At one stage, we had several reports fail, as well as the Search function. I will try updating to [3109], and see how we go.

Thanks for your efforts - trac is still a favourite amongst our engineers.