accessing pending_gpg_keys using the api fails to some users

Bug #562486 reported by Ursula Junque on 2010-04-13
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Edwin Grubbs

Bug Description

As seen on OOPS-1563B1563 and several others:
  TypeError: cannot create weak reference to 'unicode' object

Steps to reproduce:
1) Log in to devel api instance (service_root='')
2) Try to access one of these users' pending_gpg_keys: almu, dalep1, jza873, kayalemao, nitalynx, which can be found on oops reports. I checked on launchpad and the users seem active.

I was successful accessing pending_gpg_keys to the following users: ursinha, matsubara (other than me), rsalveti (one outside lp teams), yada (a user without keys). All returned no results, but haven't failed.

Related branches

Ursula Junque (ursinha) on 2010-04-13
description: updated
summary: - acessing pending_gpg_keys using the api fails to some users
+ accessing pending_gpg_keys using the api fails to some users
description: updated
Curtis Hovey (sinzui) on 2010-04-13
affects: launchpad-foundations → launchpad-registry
Curtis Hovey (sinzui) on 2010-04-13
Changed in launchpad-registry:
status: New → Triaged
importance: Undecided → High
milestone: none → series-10.05
Curtis Hovey (sinzui) wrote :

from canonical.launchpad.webapp.dbpolicy import MasterDatabasePolicy
 with MasterDatabasePolicy():
     (block of things that need to happen on master)
 That's what I was looking for. You can tell me whenever if that actually addresses the problem, or if we need to talk more

Curtis Hovey (sinzui) on 2010-05-03
Changed in launchpad-registry:
milestone: series-10.05 → 10.05
Changed in launchpad-registry:
assignee: nobody → Edwin Grubbs (edwin-grubbs)
status: Triaged → In Progress
Changed in launchpad-registry:
status: In Progress → Fix Committed
Curtis Hovey (sinzui) on 2010-06-02
Changed in launchpad-registry:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers