[00:05] wgrant: Bleh, I can't pass arguments to a property :-( [00:06] sure you can if it curries [00:06] If it what? [00:08] StevenK: Why are you trying to pass arguments to a property? [00:08] chicken mango curries. of course. [00:09] StevenK: Did you get around to removing the default maintainer subscription in a separate branch, or should I do that now? [00:10] wgrant: I haven't, no. [00:11] wgrant: forbidden_recipients_filter is a property, but for all_assignees it needs to not link against BugSubscription [00:11] StevenK: Well [00:11] StevenK: It could not be a property. [00:11] Indeed [00:26] great, looks like my credit card has been hacked :-( [00:29] I love chicken mango curry [00:41] wallyworld: oops. Dodgy card reader in a restaurant? [00:41] not sure. i got unauthorised charges from Crazy Domains (who I have a domain name with) and EuroDns (who I have not heard of before) [00:43] I'd be looking at incompetence rather than malicious hacking then [00:44] yeah, you're probably right [00:45] but i'm still pissed off and if it were just Crazy Domains I'd be less unsure. it's happened before to me with charges from India worth $1000s [00:47] dodgy call centres :) [00:56] wallyworld: stop calling the sex lines then ? [01:01] lifeless: i will if you will [01:01] I'm not the one with credit card issues :P [01:02] but sure, why not :) [01:02] ha [01:03] I just had a glance at my credit card statement - Steam, Woolworths, pizza resturant, Steam, Steam, Woolworths ... [01:03] Damn Summer sale [01:05] don't know where you get time to play all those games [01:07] wallyworld: Not all of the Steam purchases were me, Sarah is a secondary card holder [01:07] no wonder you don't have kids yet [01:07] Ouch [01:07] sorry :-P === spm is now known as stevemci === stevemci is now known as spm [05:35] Bah [05:35] Project groups, we meet again [05:35] And you ruin all my plans, again [05:37] Hahaha === spm is now known as stevemci === stevemci is now known as spm === spm is now known as stevemci === stevemci is now known as spm [06:17] wallyworld_, wgrant: https://code.launchpad.net/~stevenk/launchpad/structsub-private-bugs-redux/+merge/116798 [06:20] StevenK: probably best that wgrant looks at that one [06:20] i don't feel i have the necessary background knowledge not to miss anything [06:20] Hahaha [06:20] WCPGW [06:21] Don't answer that :-) [06:21] StevenK: yes, the potential for leaking info scares me in this case [06:27] StevenK: Will look shortly [06:53] StevenK: Are you trying to poison me? [07:00] wgrant: With which bit? [07:01] 261 Not(In(BugSubscription.person_id, [07:01] 262 - Select(BugMute.person_id, BugMute.bug_id == self.bug.id)))) [07:01] 263 + Select(BugMute.person_id, BugMute.bug_id == self.bug.id)))) [07:01] 288 + filters = [BugSubscription.bug_notification_level >= self.level, [07:01] 289 + BugSubscription.bug_id == Bug.id, [07:01] 290 + Bug.duplicateof == self.bug, [07:01] The indentation doesn't really come through here [07:01] But it's near-fatal [07:02] wgrant: 260 and such are not my fault [07:03] The case at 260 was a grey area, but you took it into a red one :) [07:04] It's now indented by three (3) spaces [07:04] And it's less indented than the previous line of the expression, which is at the same level of nesting [07:04] I've reverted that bit [07:05] wgrant: http://pastebin.ubuntu.com/1111457/ [07:05] I think I love you. [07:06] Now now [07:06] StevenK: I'll finish the review tomorrow, if that's OK [07:06] We can't deploy it before Monday, anyway [07:07] Since deploying another bugmail privacy change on Friday afternoon comes up as "fuckno" on the 0-10 scale of good deployment ideas. [07:07] wgrant: I'll commit and push that one bit [07:07] Thanks. [07:07] Since I'm sure you recall what happened in March... [07:08] I try not to. [07:09] Speaking of deploying. [07:09] Let's deploy. [07:16] StevenK: I can't see any glaring issues, but I'll want to go over it in more detail and test a few things. [07:16] Particularly the test changes. [07:16] But it looks good so far [07:18] wgrant: I'm wary about not filtering direct subscriptions, but doing so breaks the world. [07:20] wgrant: You probably want to claim the review lest sinzui swoop in and review it while you sleep. [07:21] I was just thinking that. [07:40] good morning [07:50] Thanks to whoever fixed the "Report a bug" link :-) [07:50] mpt: Rick did. === almaisan-away is now known as al-maisan [08:35] \o/ === matsubara is now known as matsubara-afk === al-maisan is now known as almaisan-away === jcsackett changed the topic of #launchpad-dev to: http://dev.launchpad.net/ | On call reviewer: jcsackett | Firefighting: - | Critical bugs: 4.0*10^2 [14:29] jcsackett: could you please review this MP: https://code.launchpad.net/~adeuring/launchpad/bug-1020443-2/+merge/116876 ? (Follow-up for the one you reviewed last week.) [14:30] adeuring: looking now. [14:30] thanks! [15:04] adeuring, hey there. Good for a call now? [15:04] deryck: sure. mumble or skype? [15:05] adeuring, I think G+ is working now. Try: http://tinyurl.com/orange-standup [15:05] ok [15:18] adeuring: r=me, but there are two small issues you'll want to double check before landing. [15:18] they are in the comment on the MP. [15:25] jcsackett: thanks! [15:26] jcsackett: good spot, these two issues! [15:46] jcsackett: Could you please review https://code.launchpad.net/~abentley/lp-dev-utils/ec2-errors/+merge/116891 ? [15:46] abentley: when you say user error, what do you mean? [15:47] what sort of user error in ec2 is this concerned with? [15:48] jcsackett: I mean the user made an error. The one I ran into was requesting a test run when I hadn't pushed my changes, i.e. PublicBranchOutOfDate [15:49] so, with this, if you call ec2 with out pushing changes, it would no longer exit? [15:50] jcsackett: Sure it would. See the sys.exit on 21? [15:50] ah, my mistake, i misread indentation. [15:50] r=me, abentley. [15:51] jcsackett: ty. [18:04] how often do oops get synced? [18:08] dobey: what do you mean [18:11] the lp-oops page is telling me it can't find an oops id from a few hours ago [18:14] dobey: matsubara-afk might know more [18:14] he'll be back shortly [18:46] jcsackett: do you have a few minutes [18:46] well minutes to talk [18:52] sinzui: sure. [18:54] jcsackett: I started a hangout, My phone thinks it is calling you [19:14] sinzui: hi [19:14] sinzui: little late in checking in, sorry. [19:31] lifeless: I have nothing to report at the moment. I offered to review how hwe was targeting bugs to multiple pillars to find an alternate bug linking strategy. [19:33] kk [19:33] I am decided to try to fix a bug, but now find that i am totally disgusted by zope schema, widgets, templates, and Lp form layout. I just want to run away screaming [19:33] welcome to my world! Want to join TA? :) [19:35] I think I will pass today. I think deleting the archaic title attribute on product will at least let test forms quickly [19:36] dobey: use the new oops system. [19:36] dobey: and update your bookmarks. [19:36] dobey: the automatic links LP makes should work fine. [19:36] czajkowski: see my mail to canonical-launchpad a few weeks back for context. [19:39] i pointed that out [19:39] lifeless i tend to star yiur mails. usually stuff i need to know or reference :) [19:46] heh :) [20:14] lifeless: what's the new system? i don't see a link in the html body [20:14] dobey: what html body ? [20:14] lifeless: the one for the 503 from the api server that gets logged. there's an x-lazr-oopsid in the http headers though [20:14] dobey: perhaps a little more context will help, I may be telling your redundant or incorrect things. [20:15] dobey: ah righto, so - if you were to file a bug on LP. [20:15] you'd get the OOPS id linkified to link through to oops.canonical.com [20:15] we're seeing a lot of 503 errors in one of our tarmac instances (not sure why others aren't getting it) [20:15] dobey: most oopses are delivered in realtime, event based, no cron involved. [20:15] ah ok [20:15] oops.c.c is the new multi-team server [20:16] it has ca, lp, ops oopses and more planned [20:16] maybe lp-oops should redirect? [20:16] it has unmigrated oopses [20:16] we'll turn it off once they lose all relevancy. [20:16] ah [20:17] this was announced, but apparently not on a wide enough net. [20:17] status: Doomed [20:17] nice. :) [20:18] looks like a db timeout poking landing_candidates for this one branch :-/ [20:19] whats the oops ID ? [20:19] 61c47ad2db8192800bc7f2df619a7c64 [20:20] dobey: thanks. Future ref - the OOPS- is part of the id (distinguishes it from a mere hash :)) [20:20] the oops.c.c web UI has special code to try for OOPS-$1 if a lookup fails. [20:21] dobey: https://oops.canonical.com/?oopsid=OOPS-61c47ad2db8192800bc7f2df619a7c64#repeatedstatements is the interesting bit to me: 177 separate branch lookups. [20:22] right [20:23] the long sql statements output is bong there. [20:23] * lifeless files a bug [20:25] bug 1029637 [20:25] <_mup_> Bug #1029637: incorrect 'long sql statements' in an oops < https://launchpad.net/bugs/1029637 > [20:33] dobey: anyhow, the landing candidates collection isn't eager loaded for security rules. [20:33] So its going to perform terribly slowly. [20:34] dobey: this may be a regression due to privacy, or it may be that privacy has had no impact and your data set has just tipped over the edge. [20:34] I can't tell. [20:37] yeah, not sure. though we do have a fairly large data set of course :) [20:37] dobey: bug 1029642 for you. [20:37] <_mup_> Bug #1029642: ScopedCollection:CollectionResource:#branch_merge_proposal-page-resource (landing candidates) dying from late evaluation of security rules < https://launchpad.net/bugs/1029642 > [20:37] dobey: its only dealing with one batch AFAICT - 75 rows. [20:38] thanks [20:38] I suspect its more a regression that not, but I'd need to check the code quite closely to actually tell. [20:38] regardless, its critical either way. [20:39] yeah, it's preventing branches from landing [20:39] when did it last work ? [20:42] yesterday or day before i think; though not sure. i have seen a couple 503s happen on and off, but not sure if they're all related [20:42] i take that back [20:42] it *just* worked [20:43] but it seems we get intermittent 503 errors; much more frequently today it seems === jcsackett changed the topic of #launchpad-dev to: http://dev.launchpad.net/ | On call reviewer: - | Firefighting: - | Critical bugs: 4.0*10^2 [21:48] sinzui: poke :) (courtesy of czajkowski) [21:48] hi YokoZar [21:48] I do have a question actually [21:48] Is it possible to have a private project / series? Or just private bugs/PPAs? [21:48] YokoZar: the latter with the addition of branches [21:49] YokoZar: Private-projects is in planning now Work will start in a few weeks [21:49] sinzui: in the meantime I suppose I can invent some cool code names [21:50] YokoZar: yes, that is good practice. avoid dates if your dates can be linked to other public data about what you are doing [21:50] YokoZar: Every project will have the option of going truly private when the private-project feature enters beta [21:50] Cool [21:51] sinzui: is renaming a series possible? [21:52] yes, the maintainer or series release manager can rename a series using the Change details link on the series page [21:53] name == the name in the url and is used on other pages [22:28] wgrant: https://bugs.launchpad.net/launchpad/+bug/615604 [22:28] <_mup_> Bug #615604: +filebug on project group asks for product too early

< https://launchpad.net/bugs/615604 > [23:04] http://hueniverse.com/2012/07/oauth-2-0-and-the-road-to-hell/ [23:17] I sympathise