scripts/logger.py uses unicode strings as oops messages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Unassigned |
Bug Description
I think this is a failure while a logged warning is being registered as an oops, caused by a non-ASCII character in the logged message:
2011-01-10 06:52:34 WARNING Template "hrself" in Groupe S HR congé trunk: can't approve entry 5049083 ('hrself/i18n/nl
_BE.po') because entry 5049091 is in the way.
Traceback (most recent call last):
File "/srv/launchpad
sys.exc_info(), self.request, informational=
File "/srv/launchpad
entry = self._makeError
File "/srv/launchpad
in self._oops_
File "/srv/launchpad
('<oops-message-%d>' % key, str(message)) for key, message
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 37: ordinal not in range(128)
This happened in the translations import queue gardener. It did not stop the script from running, but presumably it does hide an oops.
description: | updated |
Ok, so the oops code wants bytestrings - we should have logger.py utf8 encode any unicode strings it has.