Launchpad itself

UnicodeEncodeError when trying to search in launchpad/people/+index

Bug #251569 reported by Ursula Junque
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Brad Crittenden
Launchpad itself 2.2.6

Bug Description

As seen on OOPS-936G1004 , http://launchpad.net/people/+index causes a oops when trying to search for "ñ", "é", and characters like that, in all types of search.

UnicodeEncodeError: 'ascii' codec can't encode character u'\\xf1' in position 956: ordinal not in range(128)

Update: recently a few times, OOPS-968D2201, for instance, with the name "wacław".

See original description
Ursula Junque (ursinha)
Changed in launchpad:
status: New → Confirmed
Ursula Junque (ursinha)
Changed in launchpad:
assignee: nobody → salgado
Revision history for this message
Guilherme Salgado (salgado) wrote :

This is not restricted to the people search; See OOPS-936EA108, OOPS-936EB115 and OOPS-936ED106 (all from searching for 'é' on popup widgets). These may represent a separate issue, but my impression is that there may be a bug in a lower level (storm maybe?)

Changed in launchpad:
assignee: salgado → nobody
Revision history for this message
Guilherme Salgado (salgado) wrote :

Actually, OOPS-936EB115 is something else (certainly on our side).

Revision history for this message
Björn Tillenius (bjornt) wrote : Re: [Bug 251569] Re: UnicodeEncodeError when trying to search in launchpad/people/+index

On Thu, Jul 24, 2008 at 06:53:47PM -0000, Guilherme Salgado wrote:
> Actually, OOPS-936EB115 is something else (certainly on our side).

OOPS-936EB115 is a known problem, which exists for all our input fields.
It happens when your browser sends the input as ISO-8859-1, instead of
as UTF-8 (which is the encoding the page was rendered as).

Revision history for this message
Björn Tillenius (bjornt) wrote :

This is not the same bug as bug 44919. My comment was regarding OOPS-936EB115, which is different from OOPS-936G1004.

Revision history for this message
Ursula Junque (ursinha) wrote :

salgado will have a look at it next week

Changed in launchpad:
assignee: nobody → salgado
Revision history for this message
Ursula Junque (ursinha) wrote :

Changing the importance because it's a known issue

Changed in launchpad:
importance: Undecided → Medium
Revision history for this message
Guilherme Salgado (salgado) wrote :

By 'known issue' you mean we acknowledge it? Or do we know how to fix
it already?

Revision history for this message
Yada (yada-yada-yada-mailinator-deactivatedaccount) wrote :

We acknowledge it, and also that it should be fixed.

Revision history for this message
Ursula Junque (ursinha) wrote :

I mean, we acknowledge it, and also that it should be fixed.

Sorry Yada, he talks way too much :)

Ursula Junque (ursinha)
description: updated
Guilherme Salgado (salgado)
Changed in launchpad-registry:
assignee: salgado → nobody
Curtis Hovey (sinzui)
Changed in launchpad-registry:
importance: Medium → Low
status: Confirmed → Triaged
description: updated
Ursula Junque (ursinha)
summary: - UnicodeEncodeError when browser submits non-utf-8 data
+ UnicodeEncodeError/UnicodeDecodeError when browser submits non-utf-8
+ data
description: updated
Revision history for this message
Björn Tillenius (bjornt) wrote : Re: UnicodeEncodeError/UnicodeDecodeError when browser submits non-utf-8 data

This bug seems to have been morphed into something it isn't. This bug was initially about UnicodeEncodeError, which has nothing to do with bug 44919, which is about the client submitting non-UTF8 data. UnicodeEncodeError and UnicodeDecodeError are two completly different errors. All OOPSes related to UnicodeEncodeErrors are valid OOPSes, which we should fix. This basically means we OOPS every time the use searches on /people using characters like 'ö'. I'm not sure about other characters, but I'd consider increasing the importance of this bug, since it's is an OOPS bug.

OOPS-1209G1180 is an UnicodeDecodeError, and seems to be due to bug 44919.

Revision history for this message
Björn Tillenius (bjornt) wrote :

I'm resetting the status and importance to let Registry triage this bug again, since the last time it was done this was considered to be a client issue, not a valid OOPS on our end.

I'm re-assigning it to Registry, since this only happens on /people/

affects: launchpad-foundations → launchpad-registry
Changed in launchpad-registry:
importance: Low → Undecided
status: Triaged → New
summary: - UnicodeEncodeError/UnicodeDecodeError when browser submits non-utf-8
- data
+ UnicodeEncodeError when trying to search in launchpad/people/+index
description: updated
tags: removed: infrastructure
Curtis Hovey (sinzui)
Changed in launchpad-registry:
importance: Undecided → High
milestone: none → 2.2.5
status: New → Triaged
Revision history for this message
Curtis Hovey (sinzui) wrote :

Hi Brad.

This error looks like we needs to decode the user input before we do the fti operation. Can you look into this?

Changed in launchpad-registry:
assignee: nobody → Brad Crittenden (bac)
Curtis Hovey (sinzui)
Changed in launchpad-registry:
milestone: 2.2.5 → 2.2.6
Brad Crittenden (bac)
Changed in launchpad-registry:
status: Triaged → In Progress
Revision history for this message
Brad Crittenden (bac) wrote :

r8580

Changed in launchpad-registry:
status: In Progress → Fix Committed
Revision history for this message
Curtis Hovey (sinzui) wrote : Bug 251569 Fix released

Fixed released in Launchpad 2.2.6.

Changed in launchpad-registry:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.