Custom Query (332 matches)
Results (223 - 225 of 332)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#205 | fixed | email2trac chokes on non-ascii (utf8) characters in workflow | bas | eirik.schwenke@… |
Description |
We had an initial ticket status of "forespørsel", and that caused email2trac to fail with the error(s): email2trac: Traceback (most recent call last): email2trac: File "/usr/bin/email2trac", line 2133, in <module> tktparser.parse(sys .stdin) email2trac: File "/usr/bin/email2trac", line 1531, in parse self.new_ticket(m, sub ject, spam_msg) email2trac: File "/usr/bin/email2trac", line 967, in new_ticket self.set_ticket_fi elds(tkt) email2trac: File "/usr/bin/email2trac", line 876, in set_ticket_fields print 'trac .ini name %s = %s' %(name, value) email2trac: UnicodeEncodeError: 'ascii' codec can't encode character u'\xf8' in position 27: ordinal not in range(128) It would appear some more care is needed to support unicode in all strings in email2trac. I had a brief look at the script, but couldn't easily see if it would be safe and sound to simply wrap all missing strings with a .encode('utf-8') or not. For now the workaround has been to limit ourselves to ascii-characters in ticket-status names -- but that is obviously not a good solution (it's looks a bit strange in Norwegian, in eg. Japanese it would be hopeless). |
|||
#114 | wontfix | When updating ticket should take in-reply-to -header into account | bas | eero.afheurlin@… |
Description |
It would be nice to check for the in-reply-to and references headers to see which comment this is a reply to since trac (0.11) notifications add this information to headers and when using the web interfacy "reply" button trac has these nice arrows for quick reference. |
|||
#241 | fixed | Strange error on CentOS-5.5, email2trac-2.0.2, python-2.5 | bas | edward.b.matheson@… |
Description |
Getting Apr 11 13:03:02 ipcontrol1 postfix/local[27214]: 3397AF38130: to=<d318-support@ipcontrol1.atol>, relay=local, delay=0.86, delays=0.07/0.01/0/0.78, dsn=5.3.0, status=bounced (Command died with status 1: " /usr/local/bin/email2trac --project=atol --ticket_prefix=d318support". Command output: Traceback (most recent call last): File "/usr/local/lib/python2.5/logging/__init__.py", line 753, in emit self.flush() File "/usr/local/lib/python2.5/logging/__init__.py", line 731, in flush self.stream.flush() IOError: [Errno 27] File too large Traceback (most recent call last): File "/usr/local/lib/python2.5/logging/__init__.py", line 753, in emit self.flush() File "/usr/local/lib/python2.5/logging/__init__.py", line 731, in flush self.stream.flush() IOError: [Errno 27] File too large Traceback (most recent call last): File "/usr/local/lib/python2.5/logging/__init__.py", line 753, in emit self.flush() File "/usr/local/lib/python2.5/logging/__init__.py", line 731, in flush self.stream.flush()
I've spent quite a bit of time trying to solve this .. and am truly flummoxed. I've tried the system /usr/bin/python ( Python 2.4.3 ) .. didn't make any difference. I am not getting enough info from the error to find the problem. Any suggestions on how i can get more info out? The response in the mail is long and just repeats: "/usr/local/lib/python2.5/logging/__init__.py", line 753, in emit self.flush() File "/usr/local/lib/python2.5/logging/__init__.py", line 731, in flush self.stream.flush() IOError: [Errno 27] File too large Traceback (most recent call last): File "/usr/local/lib/python2.5/logging/__init__.py", line 753, in emit self.flush() File "/usr/local/lib/python2.5/logging/__init__.py", line 731, in flush self.stream.flush() IOE
Please Help ;-) |