incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wayne Witzel ❸" <>
Subject [allura:tickets] #6769 Make GC Issues importer resilient to upstream changes mid-import
Date Fri, 18 Oct 2013 11:54:45 GMT
Looks good. The tests properly exercise the described bug. Merged to master.


** [tickets:#6769] Make GC Issues importer resilient to upstream changes mid-import**

**Status:** closed
**Labels:** import google-code 
**Created:** Thu Oct 17, 2013 09:42 PM UTC by Cory Johns
**Last Updated:** Fri Oct 18, 2013 11:40 AM UTC
**Owner:** Cory Johns

For long imports, tickets could be added, removed, or made private upstream while the import
is running.  This can cause the list of ticket numbers to change, and since they're not all
pre-loaded, there is a higher chance of this happening and causing `DuplicateKeyError`s.

Change `iter_issues` to:

* Pull in all issue IDs prior to importing any tickets (this will reduce the window for changes)
* Iterate the issue IDs in increasing order instead of the current random order (this will
prevent adding new tickets, the most likely change, from causing problems)
* Remove any duplicates from the list of issue IDs caused by tickets that were deleted or
marked private
* Once the import is completed, check for any newly added issues


Sent from because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message