Closed Bug 750503 Opened 14 years ago Closed 14 years ago

[traceback] UnicodeDecodeError: 'ascii' codec can't decode byte 0xd8 in position 14413: ordinal not in range(128) | Unable to log in/login

Categories

(addons.mozilla.org Graveyard :: Add-on Builder, defect)

defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED
Q2 2012

People

(Reporter: stephend, Assigned: zalun)

References

()

Details

(Whiteboard: [fromAutomation])

When our Selenium automation runs, and tries to sign in via BrowserID on -dev (http://builder-addons-dev.allizom.org/user/browserid-login/), we're seeing the following: Traceback (most recent call last): File "/data/www/builder-addons-dev.allizom.org/flightdeck/vendor/lib/python/django/core/handlers/base.py", line 111, in get_response response = callback(request, *callback_args, **callback_kwargs) File "/data/www/builder-addons-dev.allizom.org/flightdeck/apps/person/views.py", line 201, in browserid_login assertion=request.POST['assertion']) File "/data/www/builder-addons-dev.allizom.org/flightdeck/apps/person/views.py", line 137, in browserid_authenticate log.error("[browserID] Error from AMO (%s): %s" % (email, str(err))) UnicodeDecodeError: 'ascii' codec can't decode byte 0xd8 in position 14413: ordinal not in range(128)
Summary: [traceback] UnicodeDecodeError: 'ascii' codec can't decode byte 0xd8 in position 14413: ordinal not in range(128) → [traceback] UnicodeDecodeError: 'ascii' codec can't decode byte 0xd8 in position 14413: ordinal not in range(128) | Unable to log in/login
Assignee: nobody → zaloon
Severity: critical → blocker
Target Milestone: --- → Q2 2012
This is fixed now although I've got no idea why - we need to check it AMO is responding with 401 and we allow to login anyway (!) code is not ready for production yet
I mean I know why we've not receiving the error anymore: We no longer log the error - it's a page and raises UnicodeDecodeError when writing to the log file. That commit fixed it https://github.com/mozilla/FlightDeck/commit/fa55e50ef0f346fcb941ca62ef0d159eceeaca9c We do need to investigate if user should be logged in after receiving 401 here: https://github.com/mozilla/FlightDeck/blob/master/apps/person/views.py#L138 I do think it's sane, but it will block login on -dev
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Verified FIXED; sorry for the late verification
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.