[17:14] <SixEcho> is there a launchpad URL to get a diff between a range of revisions?
[17:15] <dobey> no, but you can use bzr to do so
[17:16] <dobey> bzr diff -c 1..3 lp:foo
[17:16] <dobey> err, -r
[17:16] <SixEcho> dobey: or any chance there is a url to produce a reverse or "backout diff" for a particular revision?   just trying to succinctly reference a change(s) in a ticket
[17:17] <SixEcho> if not no big deal...
[17:18] <dobey> no, there's no web interface for directly managing branch contents. you can view the diff for a particular revision, but not a reverse of it
[17:19] <dobey> SixEcho: you can specify the revision range backwards to bzr diff to get a reverse diff, though
[17:19] <dobey> SixEcho: so bzr diff -r 3..1 for example
[17:20] <SixEcho> dobey: much thanks
[22:32] <daguegoneit> wgrant: lifeless said I should bug you if I got timeout issues in launchpad, which we do a lot in openstack. Like https://bugs.launchpad.net/nova/+bug/1211648 is something I'd really like to be able to set priorities on.
[22:33] <daguegoneit> oops, I meant - https://bugs.launchpad.net/nova/+bug/1340793
[22:44] <lifeless> daguegoneit: hi; can you get the OOPS ID from the error you got?
[22:44] <daguegoneit> lifeless: ?
[22:44] <daguegoneit> I have no idea
[22:45] <lifeless> daguegoneit: LP does many million requests a day - the OOPS ID is a direct link to the request metadata
[22:45] <lifeless> daguegoneit: are you experiencing the timeout via API or browser?
[22:45] <daguegoneit> ok, so I'm clicking through in chrome, how would I get that
[22:45] <lifeless> the error page / ajax error box should show it somewhere
[22:45] <daguegoneit> nope
[22:45] <daguegoneit> at least nothing I've seen
[22:46] <lifeless> https://help.launchpad.net/Oops
[22:46] <lifeless> daguegoneit: what priority are you trying to set on that bug ?
[22:46] <daguegoneit> so on my 5th try it worked and set it to low
[22:47] <lifeless> daguegoneit: btw these multi-project bugs are where timeouts will be much more common
[22:47] <daguegoneit> yep, I'm aware
[22:47] <daguegoneit> I'm still on a 20 - 30% fail rate on a first try of marking a Nova bug Invalid
[22:49] <lifeless> ok, I'm going to play on staging and see if I can get a better screenshot of the error
[22:52] <lifeless> wgrant: staging seems to be hugely out of date?
[22:52] <wgrant> lifeless: It is deliberately so atm.
[22:52] <lifeless> wgrant: ah; so I'm trying to get a screenshot to show sdague aka daguegoneit how to report an OOPS for you
[22:53] <lifeless> when using ajax updates via chrome
[22:53] <lifeless> ahhh
[22:53] <lifeless> that ug still isn't fixed
[22:53] <lifeless> just 'Timeout error, please try again in a few minutes.
[22:53] <lifeless> ￼OK'
[22:54] <lifeless> wgrant: you don't get to whine about no OOPS till thats fixed, fair?
[22:54] <daguegoneit> lifeless: so very rarely do I actually get that popup
[22:54] <daguegoneit> that's the red box popup, right?
[22:54] <daguegoneit> anyway, I need to call it a week. Might ping more next week
[22:55] <lifeless> daguegoneit: what do you normally get when a failure occurs? grab a screenshot next time :)
[22:55] <daguegoneit> lifeless: sure, it happens a lot, so I'll be able to get tons of screenshots
[22:56] <lifeless> daguegoneit: just one; then thats the thing that we need to fix/document how to get an OOPS ID in there.
[22:58] <wgrant> Let me see if I can find some from that URL.
[23:01] <wgrant> As expected, it's because of the ridiculous number of structural subscribers on that set of projects.
[23:02] <wgrant> Roughly even split between SQL and Python time, ew.