Removing "don't reset connection for each transaction" option broke translations copy

Bug #255758 reported by Jeroen T. Vermeulen
10
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Jeroen T. Vermeulen

Bug Description

We recently stopped resetting connections after every transaction, and correspondingly removed the transaction manager's reset_after_transaction field.

Except the translations copying script still set this option in one code path (now unnecessarily), where setting this option now results in an error. Since the mock transaction manager we use to test this code was not updated to remove reset_after_transaction, the test kept passing.

This is a problem for opening the Intrepid translations, which we are aching to do.

Changed in rosetta:
assignee: nobody → jtv
importance: Undecided → Critical
milestone: none → 2.1.8
status: New → In Progress
Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Fixed in RF 6818

Changed in rosetta:
status: In Progress → Fix Committed
Changed in rosetta:
status: Fix Committed → Fix Released
visibility: private → public
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.