[10:52] hey [10:52] does anyone know why https://code.launchpad.net/~didrocks/software-properties/error-fixes is not importing? [10:52] or it seems stucked in "updating" [10:58] seb128: Looking [10:58] wgrant, thanks [11:00] seb128: The branch is corrupt, possibly not pushed properly. Worth asking Didier to delete it and push it again. [11:00] wgrant, he didn't get an error while pushing, unsure what went wrong [11:00] and I can bzr branch/merge it fine [11:00] so it seems valid [11:00] weird [11:01] $ bzr branch lp:~didrocks/software-properties/error-fixes /tmp/error-fixes [11:01] bzr: ERROR: No such file: 'dialogaddsourceslist-20100825085057-b6js95rdf2xuk0uj-2' [11:01] Branching trunk works fine. [11:01] oh, right, I just bzr merged it [11:01] Can you try a repush? [11:01] didn't try a full branch [11:01] If that doesn't fix it, I'll investigate harder. [11:03] bzr push --overwrite says that there is nothing to push [11:03] and I was wrong, he got a network disconnect when first pushing and had to break-lock and push again [11:03] well anyway was reviewed manually and merged [11:03] so no big deal [11:03] thanks for looking [11:05] Ahh [11:05] That'd do it. [13:41] mapreri: Yes, we found that when doing preliminary investigative work, but it's not very satisfactory. You can't use it on Google Apps for Work accounts because it pops up a button to ask permission, and you can only run it on a timer, not on all new mail, so it's racy [13:41] mapreri: This is why we decided not to recommend that to people and did the expanded footers thing instead. [13:42] cjwatson: my main point was that it's a quite unfriendly UI to filter mail... [13:43] Certainly [13:43] btw, I find having those data on the footer handy also because it's easier to look up for me than going read the headers, even if I don't do filtering [13:43] I've had them switched on for my own account for a while, mainly so that I notice oddities. I'll probably turn them off eventually, but I know what you mean. [17:02] Evening all, I remember reading a blog post (or something) on Launchpad and how tightening the screws on timeout limits was used to identify, log and fix performance issues on LP. I've found http://blog.launchpad.net/launchpad-performance-week/introducing-launchpad-performance-weeks now, but it either had less details than I remember it, or there's one or more follow-up posts which I haven't been able to track down. Does this ring a bell for [17:02] anyone? :) === coreycb` is now known as coreycb === JanC_ is now known as JanC