Modify ↓
Opened 19 years ago
Closed 19 years ago
#2529 closed defect (worksforme)
unicode error viewing ticket (with workaround)
| Reported by: | koral | Owned by: | Jonas Borgström |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | 0.9.2 |
| Severity: | normal | Keywords: | unicode |
| Cc: | koral@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
after modifying some information to a ticket, that ticket page got an error showing a backtrace that lead to UnicodeDecodeError exception in db.py's _convert_row(self, row). other tickets were viewable but that one always lead to that error.
- using the attached patch I can get the page back to work, but every commend added after the revision when problem occourred, are not shown.
this bug is nasty on our production server.
thanks for developing such a great app, we love it.
Attachments (1)
Change History (3)
by , 19 years ago
| Attachment: | db_unicodedecodeerror_workaround.diff added |
|---|
comment:1 by , 19 years ago
comment:2 by , 19 years ago
| Keywords: | unicode added |
|---|---|
| Resolution: | → worksforme |
| Status: | new → closed |
You somehow managed to get non-UTF8 encoded data in your database… With the recent switch to unicode, the proposed patch is not relevant anymore, so I'm closing this report.
I'd suggest that you track down the reason why non-UTF-8 encoded data made it into your database, and that you manually remove/fix the offending content. This might be related to #1310…
Note:
See TracTickets
for help on using tickets.
about the patch
note: this attachment is only a loosy workaround, since I know nothing about python and trac internals.