branch-puller mirror scripts fails with an InvalidURIError
Bug #141527 reported by
Diogo Matsubara
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
Jonathan Lange |
Bug Description
David Allouche indentified an error in the branch-puller mirror script.
Sometimes it might raise an InvalidURIError and that exception is not properly handled.
OOPS-629SMPM692 InvalidURIError "Please update your branch to point to http://
A log of the error can be found at:
https:/
David patched the production server with:
https:/
Changed in launchpad-bazaar: | |
assignee: | nobody → ddaa |
Changed in launchpad-bazaar: | |
status: | Triaged → In Progress |
Changed in launchpad-bazaar: | |
assignee: | nobody → jml |
Changed in launchpad-bazaar: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
The gravity of this bug is compounded by a recent regression in the order of pulling branches.
Previously, branches whose mirroring had started but completed (because of an unhandled exception or because the script was killed) on a previous run, were processed last. So branches that caused reproducible unhandled errors would not block other branches from being processed.
Now, a branch that caused an unhandled error on the previous run is processed first on the next run. If the error is reproducible, that effectively brings the service to a halt.
I suspect the regression was introduced in RF 4777, when fixing bug 74031.