SourceForge bug import script doesn't handle nonexistent projects properly

Bug #257741 reported by Graham Binns
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

If you specify an nonexistent product when importing bugs from SourceForge, you get a traceback:

Traceback (most recent call last):
  File "/home/graham/canonical/lp-branches/trunk/lib/canonical/launchpad/scripts/sftracker.py", line 440, in importTracker
    self.importTrackerItem(item)
  File "/home/graham/canonical/lp-branches/trunk/lib/canonical/launchpad/scripts/sftracker.py", line 353, in importTrackerItem
    msg = self.createMessage(item.title, date, userid, text)
  File "/home/graham/canonical/lp-branches/trunk/lib/canonical/launchpad/scripts/sftracker.py", line 320, in createMessage
    owner = self.get_person(userid)
  File "/home/graham/canonical/lp-branches/trunk/lib/canonical/launchpad/scripts/sftracker.py", line 279, in get_person
    comment='when importing bugs for %s from SourceForge.net'
AttributeError: 'NoneType' object has no attribute 'displayname'

This happens because the sourceforge-import.py script doesn't handle the nonexistent product properly. It should check that the product exists before it tries to do anything else, but it's obviously not doing.

Tags: lp-bugs
Graham Binns (gmb)
Changed in malone:
status: New → Triaged
Curtis Hovey (sinzui)
Changed in malone:
importance: Undecided → Low
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

This seems related to bug 227380.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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