No way to ask Launchpad to refresh a stale diff
Bug #483945 reported by
Jonathan Lange
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Low
|
Colin Watson | ||
Bug Description
The diff on a merge proposal can be stale, especially when the target branch has changed but the source branch hasn't. In these cases, there's no way of asking Launchpad to regenerate the diff. Perhaps there should be.
WORK AROUND
Ask a webops on #launchpad-dev or #launchpad-ops to unscan the proposed branch.
Related branches
lp:~cjwatson/launchpad/bmp-export-scheduleDiffUpdates
- William Grant: Approve (code)
-
Diff: 172 lines (+70/-15)5 files modifiedlib/lp/code/interfaces/branchmergeproposal.py (+14/-1)
lib/lp/code/model/branch.py (+2/-11)
lib/lp/code/model/branchmergeproposal.py (+17/-0)
lib/lp/code/model/gitrepository.py (+1/-2)
lib/lp/code/model/tests/test_branchmergeproposal.py (+36/-1)
| Changed in launchpad-code: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| tags: | added: openstack |
| tags: | added: trivial |
| tags: | added: mp-preview-diff |
| description: | updated |
| Changed in launchpad: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Colin Watson (cjwatson) |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #1 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| description: | updated |
Revision history for this message
| Colin Watson (cjwatson) wrote | #2 |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in stable r18511 <http://