[00:17] wallyworld_: O hai [00:17] hello [00:17] did we need to mumble? [00:17] * StevenK looks for mumble [00:44] wgrant: How is the second branch wrong? I don't want to set it to private if it's EMBARGOEDSECURITY for the moment. [00:47] StevenK: In commands.py? [00:47] wgrant: Yup. [00:47] StevenK: It will currently AssertionError if given EMBARGOEDSECURITY [00:48] Oh, I fixed that, just forgot to commit and push. [00:55] wgrant, hi [01:18] poolie: Hi [01:24] wgrant: I removed the assert, I'm going to toss it at ec2. [01:25] wgrant: As to why createBug() is in systemhomes, I still have NFI === abentley changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: - | Firefighting: - | Critical bugtasks: 4*10 [02:05] wgrant: got 5 for a quick chat ? [02:40] lifeless: Just got back from lunch. Still around? [02:43] yes [02:43] skype? [02:43] It hates PulseAudio. Let me see. [02:44] pavucontrol will let you fix that easily [02:44] No, it won't even connect to PA AFAICT [02:44] oh, thats new and special [02:44] Yeah [02:44] Haven't had this one before. [02:44] Let's see if the one from partner works. [03:21] PA seems to have decided my headset is not an input device recently [03:23] it would be right? :) [04:25] Hmm, how do I tell firebug to keep executing JS? [04:26] The play button. Tricky. === bigjools-afk is now known as jtvs-evil-twin [07:41] good morning === jtvs-evil-twin is now known as bigjools_ === almaisan-away is now known as al-maisan [09:01] cjwatson: Are you good to QA r15036 on DF today? [10:59] StevenK: yep, I will be [11:18] wgrant: If your still there, does PG 9.1 make your life easier with bugtask search data structures? Things are so far on track to switch Production starting 23rd April. [11:18] (Minor things like the Precise release might affect that :) ) [11:21] This merge proposal is making me thirsty. [11:25] stub: Being able to use GIN for a second iteration will be nice. [11:25] Saw your comment about array syntax mentioning 8.4 [11:26] And its better support for text arrays might open up new avenues for tags. [11:26] But it isn't worth doing this as a 9.1 specific feature branch? [11:27] No. This is good enough for now, and we get it a month early. [11:27] Anything 9.1-specific will need more experimentation post-upgrade. [11:27] And this is deliberately designed so we can iterate cheaply by introducing new versions of the table. [11:28] I'm looking forward to the death of slony. Oh, and 5 seconds FDT. === rick_h changed the topic of #launchpad-dev to: http://dev.launchpad.net/ | On call reviewer: rick_h* | Firefighting: - | Critical bugtasks: 4*10 [11:34] wgrant: What do the indexes ending with the bugtask or bug columns get used for. Is it being used as a creation date (but with stable ordering)? [11:35] * stub reads the mp blurb just in case this was explained :) [11:35] stub: Ah, sorry, forgot about the indices. [11:35] stub: Those are bug search sort orders. [11:35] So bugtask/bug are tiebreakers. [11:36] Just to ensure consistent ordering? [11:36] bug is used when the context is unambiguous (only a single task for each bug can appear, ie. most contexts), bugtask when it's ambiguous (eg. distributions, where you can have tasks for multiple packages on a single bug) [11:36] Yes, I believe. [11:36] And to make it logical. [11:36] eg. ordering by importance, the first 200000 bugs or so are a single importance. [11:36] And having them arbitrarily ordered would be odd. [11:36] Those indices are just a start, but they satisfy all the common bug search cases. [11:36] But no need to pull in product.name and friends [11:37] We may eventually want something more selective on status, duplicateof, etc. [11:37] No. [11:37] Is this the review of bugtaskflat? [11:37] There are some orders that I'm probably going to ban on large sets of bugs. [11:37] Assignee name, tag, location name, etc. [11:37] They're not useful, and very expensive on large sets. [11:38] And for small sets it's fine to do the sort as the last stage. [11:38] I think we should consider telling the user they are being nonsensical if the query results are nonsensical. If the first 200000 bugs are a single importance, the answer isn't important because it is rather useless. [11:38] stub: Indeed. [11:38] stub: But that's the default sort order :) [11:38] Yes, the principal remains :) [11:39] stub: Half these indices are to satisfy eg. https://launchpad.net/launchpad/+bugs [11:39] Just wrapping my head around what we have here [11:39] StevenK: Yes [11:39] With just a straight walk down the index. [11:39] In 2-3ms. [11:39] Person:+bugs is going to be interesting. It's not clear what indices are best there. [11:40] Fortunately we have feature flags to disable BugTaskFlat use where it doesn't work yet :) [11:40] s/doesn't work yet/turns out to be slow sometimes without further indices/ [11:41] The indices *will* need further work, but this seems to be a good start for most things. [11:42] wgrant: So Celery can use PostgreSQL as a backend. Perhaps these triggers should just launch Celery jobs :-) [11:43] These are about 100x faster than bugsummary in some cases, and I am rewriting bugsummary to be less insane, so it will be a net speedup :) [11:46] * cjwatson would love review of https://code.launchpad.net/~cjwatson/launchpad/proposed-as-staging-pocket/+merge/99911 [11:49] Anyone mind if I upgrade mawson? [11:53] cjwatson: Go ahead. [11:53] Hopefully the DB upgrade won't break. [11:54] Anything I need to watch out for in particular? Or is this the stuff that's been afflicting NDTs? [11:54] Nah, just mawson sometimes misses some of the migrations. [11:54] And occasionally gets manual BugTaskFlat patches that could conflict. [11:54] But I think it should be OK [11:54] If it breaks, yell and I'll fix. [11:55] running [11:55] cjwatson: Only if you happen to 'upgrade' to something that's 100 revisions behind. [11:55] 150, TYVM [11:55] Indeed. [11:55] That was a fun morning. [11:55] How did that happen? [11:56] cjwatson: Worse, it was on prod. [11:56] 'tis a mystery [11:56] And we're in the middle of two rather large migrations for disclosure. [11:56] hmm, Text conflict in lib/lp/scripts/garbo.py [11:56] bzr resolve --take-other [11:56] That's from when I was manually running a single garbo job to complete a migraiton [11:59] mkay [11:59] mawson's bzr is too old for resolve --take-other, I used revert instead, hope that was ok [12:00] Yeah, that's fine. [12:09] cjwatson: You win the award for lowest SNR in a Launchpad merge proposal, but approved :) [12:13] wgrant: I assumed everyone else's merges were like that nowadays too as they desperately scrabbled for LoC. Maybe not [12:14] cjwatson: We tend to split branches when the get like that. It's not a strict rule that every *branch* must not be LOC-positive. [12:15] OK, I'll try to remember that. I guess I find it hard to keep track otherwise [12:16] cjwatson: Indeed, that's the problem :) [12:16] cjwatson: Can you set a commit message? [12:16] done [12:16] Ah, mawson at least thinks it's done now. [12:32] http://people.canonical.com/~cjwatson/tmp/loc.png - I was curious what LoC delta per revision actually looks like since the new policy ... [12:33] different view from ohloh's [12:36] I've been meaning to get around to repurposing community-contributions.py to provide some kind of analysis like that. [12:38] net +1901 since new policy [12:40] which is not really obvious from that graph === matsubara-afk is now known as matsubara [13:04] so, perhaps we should limit the length of a bug report title: pad.lv/943974 [13:07] hah, that's great. [13:07] I think the limit in the db is 2GB [13:26] wtf [13:26] that is a big title. === jcsackett changed the topic of #launchpad-dev to: http://dev.launchpad.net/ | On call reviewer: jcsackett, rick_h* | Firefighting: - | Critical bugtasks: 4*10 [14:29] I'd be happy to help get another deploy today, but I must admit I have no clue how to qa cjwatson's changes. [14:30] I think all of our soyuz experts are australian now, too. hmmmm [14:30] deryck: I just finished QAing it. [14:31] cjwatson, ah very good! Thanks, man. [14:32] adeuring, now we're just waiting on your revision. [14:32] I'd like that deployed on ftpmaster at some point; I don't know what the deployment procedures for that look like these days. [14:32] deryck: argh, got distracted... [14:33] adeuring, np. :) Can you ping me when it's done, so I can put up a ndt deploy request? [14:33] deryck: sure [14:33] cjwatson, I don't know either. But I'll check into it when I put the deploy request up. [14:35] ftpmaster (well, the bit of it that matters) is currently on 15032, so not that far back. [14:36] OK, LPS says it's still a separate 5-minute window. [14:36] ah yeah, just saw that too. [14:36] so we'll have to schedule that. [14:36] mrevell, we're doing a deploy later today that we need deployed to ftpmaster, and that needs 5 minute downtime. How do we schedule that now? [14:36] mrevell, do you or danhg set that up? [14:48] deryck, Hey, for five minutes just ask czajkowski to announce it to the status feed. Antu [14:49] deryck, Anything more than that and I can find out when would have least impact on our stakeholders and users generally. [14:49] mrevell, ah ok. I'll schedule with webops then and ping czajkowski when I know when they can do it. [14:49] deryck: just let me know the details more than 5 mins before hand and then I can get it out [14:52] czajkowski, will do, thanks === matsubara is now known as matsubara-lunch === Ursinha_ is now known as Guest92471 [15:41] wgrant: hm, I meant to ask, did you feed my branch to EC2? [15:41] I guess I'll find out by the time you read this. === deryck is now known as deryck[lunch] === salgado is now known as salgado-lunch === al-maisan is now known as almaisan-away [16:36] wgrant: ... never mind. :-) === matsubara-lunch is now known as matsubara [17:03] rick_h, jcsackett. Do you have time to review https://code.launchpad.net/~sinzui/launchpad/obsolete-js/+merge/99978 [17:04] deryck[lunch]: am heading offline for EOD but will be back later if you want an annoucement put out. [17:04] sinzui: will look at it now === deryck[lunch] is now known as deryck [17:07] czajkowski, ack. I think it will likely be done tomorrow now. waiting on QA for a branch. [17:07] deryck: ok well mail me and I can still annouce it in places for tomorrow [17:07] czajkowski, ok, thanks. [17:16] rick_h, can you clarify the space issue now that I see it? I see two spaces...but I like code to be 4 spaces. Do you want me to make it 2 or 4 spaces [17:17] sinzui: sorry, mean the space between the keyword 'function' and the parens [17:17] sinzui: I think most LP people have no space between them, my background nad jslint are for a space [17:18] sinzui: complete nitpick thing [17:19] okay. I see that. [17:20] other than that, thanks for finding and cleaning that up. One less thing for my long term JS clean up todo list :) [17:23] sinzui: i have followed up on rick_h, and have nothing to add. r=me. [17:37] thanks jcsackett. I just extracted the script and ran it though lint. There were some == issues that also needed fixing [17:37] doh, I should have caught those. Evil JS in .pt files... [17:39] sinzui: have a sec for a quick ? on the subscribers stuff? [17:39] sure [17:39] sinzui: I'm trying to see where/how you test that once you have the notification bits working, that the event is bound correctly/working in the actual app layer through your configure.zcml bits? [17:40] all the tests manually generate or call the event method that gets fired [17:41] sorry, thunderbird-aka-shitehawk was stealing focu [17:41] s [17:43] rick_h, we have a utility that subscribes to the event that allows us to see it what was passed. [17:43] * sinzui looks for it in answers or registry [17:46] rick_h, sorry, this time I could not find. it We use TestEventListener [17:46] * sinzui looks for real example of use [17:46] ok, will search for that thanks [17:47] that's ok, I can peek, just need a hint. Wasn't seeing it in the existing tests I was looking at [17:48] rick_h, http://pastebin.ubuntu.com/905984/ === salgado-lunch is now known as salgado [17:48] ^ the setup is odd because of the registration/deregistration of the listener [17:49] ty much sinzui [21:00] sinzui: i *might* be a few minutes late to the standup. i have to drive my wife to work. hopefully traffic won't be too bad [21:01] okay [22:21] wgrant, wrong protocol on port -> http://pastebin.ubuntu.com/906352/ [22:22] sinzui: Yeah, that's speaking HTTPS to an HTTP listener. [22:27] StevenK, I was thinking of bug #367533 [22:27] <_mup_> Bug #367533: Collapsible fieldsets don't degrade gracefully when Javascript isn't available < https://launchpad.net/bugs/367533 > [22:28] g'd evenin' launchpadders [22:29] Morning jelmer. [22:34] StevenK, and bug #677339 [22:34] <_mup_> Bug #677339: filebug per-project help is below the fold < https://launchpad.net/bugs/677339 > [22:53] wgrant, sinzui: https://www.destroyallsoftware.com/talks/wat === wallyworld_ changed the topic of #launchpad-dev to: http://dev.launchpad.net/ | On call reviewer: wallyworld | Firefighting: - | Critical bugtasks: 4*10