Edgewall Software

Changes between Initial Version and Version 1 of Ticket #5110


Ignore:
Timestamp:
Apr 9, 2007, 12:58:43 PM (17 years ago)
Author:
Emmanuel Blot
Comment:

Can you check whether the changeset you're attempting to view does not have a log message that contains non-UTF8 characters? This is a typical cause of this kind of error.

SVN log messages should only contain UTF-8 characters.
0.9 series were more permissive about invalid characters, they were unable to detect this kind of issue. It does not mean a bug has been introduced in 0.10 series, but that the latter do not accept invalid characters anymore.

You can also search for "can't decode bytes" in the ticket database, as I'm confident several other tickets deal with the same issue.

BTW, you'd better upgrade to 0.10.3.1 as it fixes several functional and security issues.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5110 – Description

    initial v1  
    44In trac-0.9.6 this error doesn't ocurr.
    55
    6 
     6{{{
    77Traceback (most recent call last):
    88  File "/usr/obj/ports/trac-0.10.1/fake-i386/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 379, in dispatch_request
     
    1717    return codecs.utf_8_decode(input, errors, True)
    1818UnicodeDecodeError: 'utf8' codec can't decode bytes in position 120-123: invalid data
     19}}}