=== BradCrittenden is now known as bac === b is now known as Guest39961 === s8321414_ is now known as s8321414 === reed_ is now known as reed === semiosis is now known as semiosis_ === semiosis_ is now known as semiosis [17:14] is there a launchpad URL to get a diff between a range of revisions? [17:15] no, but you can use bzr to do so [17:16] bzr diff -c 1..3 lp:foo [17:16] err, -r [17:16] 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] if not no big deal... [17:18] 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] SixEcho: you can specify the revision range backwards to bzr diff to get a reverse diff, though [17:19] SixEcho: so bzr diff -r 3..1 for example [17:20] dobey: much thanks === ral_ is now known as ral === daker_ is now known as daker === mapreri_ is now known as mapreri === yofel_ is now known as yofel === cprov__ is now known as cprov === zoktar_ is now known as zoktar [22:32] 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] oops, I meant - https://bugs.launchpad.net/nova/+bug/1340793 === mapreri_ is now known as mapreri [22:44] daguegoneit: hi; can you get the OOPS ID from the error you got? [22:44] lifeless: ? [22:44] I have no idea [22:45] daguegoneit: LP does many million requests a day - the OOPS ID is a direct link to the request metadata [22:45] daguegoneit: are you experiencing the timeout via API or browser? [22:45] ok, so I'm clicking through in chrome, how would I get that [22:45] the error page / ajax error box should show it somewhere [22:45] nope [22:45] at least nothing I've seen [22:46] https://help.launchpad.net/Oops [22:46] daguegoneit: what priority are you trying to set on that bug ? [22:46] so on my 5th try it worked and set it to low [22:47] daguegoneit: btw these multi-project bugs are where timeouts will be much more common [22:47] yep, I'm aware [22:47] I'm still on a 20 - 30% fail rate on a first try of marking a Nova bug Invalid [22:49] ok, I'm going to play on staging and see if I can get a better screenshot of the error [22:52] wgrant: staging seems to be hugely out of date? [22:52] lifeless: It is deliberately so atm. [22:52] wgrant: ah; so I'm trying to get a screenshot to show sdague aka daguegoneit how to report an OOPS for you [22:53] when using ajax updates via chrome [22:53] ahhh [22:53] that ug still isn't fixed [22:53] just 'Timeout error, please try again in a few minutes. [22:53] OK' [22:54] wgrant: you don't get to whine about no OOPS till thats fixed, fair? [22:54] lifeless: so very rarely do I actually get that popup [22:54] that's the red box popup, right? [22:54] anyway, I need to call it a week. Might ping more next week === Laney is now known as Guest14360 [22:55] daguegoneit: what do you normally get when a failure occurs? grab a screenshot next time :) [22:55] lifeless: sure, it happens a lot, so I'll be able to get tons of screenshots [22:56] daguegoneit: just one; then thats the thing that we need to fix/document how to get an OOPS ID in there. === daguegoneit is now known as sdague [22:58] Let me see if I can find some from that URL. [23:01] As expected, it's because of the ridiculous number of structural subscribers on that set of projects. [23:02] Roughly even split between SQL and Python time, ew. === zoktar is now known as 77CAAFYCY === dobey_ is now known as dobey === aalex is now known as 6A4AAOMT9 === aboudreault is now known as 6JTAAFSTW === jpds is now known as 6JTAAFS52 === jamesh is now known as 6JTAAFV9I === hggdh is now known as 6JTAAFWBI === benji is now known as Guest28630