Opened 17 years ago
Last modified 17 years ago
#5110 closed defect
Crash in SVN Browser — at Version 1
| Reported by: | Owned by: | Christian Boos | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | version control | Version: | 0.10.1 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
Hi
I'm installing trac-0.10.1 in OpenBSD an it crash when I browse my SVN directory In trac-0.9.6 this error doesn't ocurr.
Traceback (most recent call last):
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
File "/usr/obj/ports/trac-0.10.1/fake-i386/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 230, in dispatch
File "/usr/obj/ports/trac-0.10.1/fake-i386/usr/local/lib/python2.4/site-packages/trac/versioncontrol/web_ui/log.py", line 163, in process_request
File "/usr/obj/ports/trac-0.10.1/fake-i386/usr/local/lib/python2.4/site-packages/trac/versioncontrol/web_ui/util.py", line 37, in get_changes
File "/usr/obj/ports/trac-0.10.1/fake-i386/usr/local/lib/python2.4/site-packages/trac/versioncontrol/cache.py", line 44, in get_changeset
File "/usr/obj/ports/trac-0.10.1/fake-i386/usr/local/lib/python2.4/site-packages/trac/versioncontrol/cache.py", line 155, in __init__
File "/usr/obj/ports/trac-0.10.1/fake-i386/usr/local/lib/python2.4/site-packages/trac/db/sqlite_backend.py", line 73, in fetchone
File "/usr/obj/ports/trac-0.10.1/fake-i386/usr/local/lib/python2.4/site-packages/trac/db/sqlite_backend.py", line 69, in _convert_row
File "/usr/local/lib/python2.4/encodings/utf_8.py", line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeDecodeError: 'utf8' codec can't decode bytes in position 120-123: invalid data
Note:
See TracTickets
for help on using tickets.
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.