BugWatchUpdater.updateBugWatches() has silly transaction boundaries

Bug #538096 reported by Graham Binns
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Gavin Panella

Bug Description

If you look at the main for loop in BugWatchUpdater.updateBugWatches() you'll see that there are some ridiculous transaction boundaries. Basically:

 1. A transaction is begu.
 2. We loop over the bug watches.
 3. We loop over them *again* and:
   a. Update their statuses
   b. Import comments
   c. Push comments
   d. Add backlinks to the remote bug tracker
 4. The transaction is commited.

This is beyond silly; we need saner transaction boundaries which don't (except where absolutely necessary) have network activity happening within them.

Related branches

Graham Binns (gmb)
Changed in malone:
importance: Undecided → High
Gavin Panella (allenap)
Changed in malone:
assignee: nobody → Gavin Panella (allenap)
status: Triaged → In Progress
Gavin Panella (allenap)
Changed in malone:
milestone: none → 10.03
Gavin Panella (allenap)
Changed in malone:
status: In Progress → Fix Committed
Revision history for this message
Ursula Junque (ursinha) wrote : Bug fixed by a commit
tags: added: qa-needstesting
Gavin Panella (allenap)
tags: added: qa-ok
removed: qa-needstesting
Gavin Panella (allenap)
Changed in malone:
status: Fix Committed → Fix Released
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.