AttributeError: 'NoneType' object has no attribute 'displayname' requesting people merge
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Critical
|
Ian Booth |
Bug Description
OOPS-094457cbe5ffa5d229cefcc993182eb9 and OOPS-1cc18b356280049eb1800b4d19d05617 triggered an AttributeError: 'NoneType' object has no attribute 'displayname' when requesting merge of accounts
https:/
Relevant part of the traceback:
Module lp.registry.
token.
Module lp.services.
replacements = {'dupename': "%s (%s)" % (dupe.displayname, dupe.name),
AttributeError: 'NoneType' object has no attribute 'displayname'
Related branches
- Curtis Hovey (community): Approve (code)
-
Diff: 469 lines (+226/-197)3 files modifiedlib/lp/registry/browser/tests/test_peoplemerge.py (+224/-0)
lib/lp/registry/stories/person/merge-people.txt (+0/-196)
lib/lp/services/verification/model/logintoken.py (+2/-1)
tags: | added: merge-deactivate |
tags: | added: regression |
Changed in launchpad: | |
status: | Triaged → In Progress |
assignee: | nobody → Ian Booth (wallyworld) |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
This bug is implicitly fixed when we fix bug 960493 because this token was left behind my a successful merge.