[01:03] What's happening with vostok these days? [01:08] Project parallel-test build (12): STILL FAILING in 2 hr 11 min: https://hudson.wedontsleep.org/job/parallel-test/12/ [01:26] mwhudson: hey [01:26] mwhudson: so in the person merge code [01:26] there is an XXX from you [01:26] about recipes and a function to write. [01:26] but no bug # [01:26] ah oops [01:26] did you forget to put the bug # in, or is the bug mythical? It seems like an important before-live-todo, to me [01:27] i don't remember filing a bug :/ [01:27] perhaps you could ? [01:27] this is about person merge not blowing up if you merge two accounts that have a recipe of the same name [01:27] I would assume so [01:28] also, I have sent a needs-to-be-digested mail to the list about code structure [01:28] I'm totally sure its impenetrable due to jetlag :) [01:28] well, i'm pretty sure it would be to me :-) [02:02] Hard / Soft Page ID [02:02] 266 / 0 Archive:EntryResource:getBuildSummariesForSourceIds [02:02] 162 / 260 BugTask:+index [02:02] 133 / 161 CodeImportSchedulerApplication:CodeImportSchedulerAPI [02:02] 121 / 43 Person:+commentedbugs [02:02] 107 / 282 Distribution:+bugs [02:02] 100 / 0 MailingListApplication:MailingListAPIView [02:02] 29 / 53 Archive:+packages [02:02] 26 / 1956 Archive:+index [02:02] 21 / 25 Milestone:+index [02:02] 15 / 85 POFile:+translate [02:15] lifeless: did arsenic get new code? [02:16] lifeless: MailingListApplication:MailingListAPIView lives there [02:16] lifeless: and while I did only one method, it should have helped [02:16] lifeless: see my note about getting the method used into the pageid for xmlrpc calls [02:17] no [02:17] its a SPOF at the moment [02:18] there is an RT to fix that [02:18] when thats done, it will be in the nodowntime set [02:18] thumper: I replied about the xmlrpc pageid [02:18] thumper: 'yes we can change it, there is a bug already I think [02:18] paraphrasing [02:19] lifeless: did you? must of missed it [02:19] 11:58 < lifeless> whats arsenic [02:19] 11:59 < lifeless> yes, there is a bug already [02:19] ah [02:20] yes, see it now [02:20] * thumper goes to make a coffee [02:29] wgrant: when are your exams done with ? [02:29] lifeless: 23rd. [02:30] of nov? [02:31] Ja. [02:31] kk [02:31] lots of prep time then ;) [02:31] gl [02:31] Thanks. [02:32] wgrant: how many exams? [02:32] thumper: Just the three. [02:32] not too bad then :) [02:32] Since the fourth subject was the project, which lacks an exam. [02:33] Indeed. [02:33] 10, 11, 23 [02:43] I remember my first year exams, Saturday am, Tuesday am, Tuesday pm, Thursday am, Thursday pm, Friday pm, then two weeks break before the last two [02:44] Weekend exams? Cruel. [02:45] yeah [02:51] try having your 21st birthday in the middle of exam week. :-( [02:53] spm: I got married the day before I turned 21 :) [02:53] thumper: so what I'm hearing, unhappy for pretty much the same reason??? :-P [02:53] no comment [02:53] heh [02:57] there is something wrong if the builds are taking 7 hours :( [03:46] lifeless: sinzui mentioned that you did some research into the whole distro milestone +index timeout when there are lots of bugs. It seems that it is just spending a ton of time creating all the storm objects. Do you have any other insight? [03:51] * thumper marvels at the amount of yak hair in blueprints [03:51] * thumper has the clippers out [03:54] EdwinGrubbs: I setup eager loading [03:54] EdwinGrubbs: for both bugs and milestones [03:55] EdwinGrubbs: but I have only turned it on in one code path (to ensure I could actually deliver) [03:55] EdwinGrubbs: which pageid / bug are you looking at. [03:55] lifeless: https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1765ED1258 [03:55] bug 638924 [03:55] <_mup_> Bug #638924: Milestone:+index timeouts with many bugs [03:59] thumper: Was Blueprint touched significantly after its initial drop? [03:59] wgrant: not much no [04:00] wgrant: I now have a pipeline: ~/src/launchpad/blueprint-yak-shaving [04:00] if anything was a test for not needing a review, this is [04:05] Heh. [04:06] thumper: So, I've done something surprising. [04:06] thumper: Robert Ancell was talking to me about specs not being exported over the API, so I made them be, in anger, on two plane flights. [04:06] StevenK: you've moved to NZ? [04:07] thumper: its certainly a consideration [04:07] StevenK: have you moved the security checks? [04:07] lifeless: There's security checks? [04:07] StevenK: james_w has a branch that exports specs over the API; its blocked on that change. [04:07] Rargh, didn't know that [04:07] StevenK: yeah, too many checks done in the browser code [04:07] Speaking of, I should charge my laptop [04:07] I've started shaving blueprints... [04:08] but it will take some time to see the shape of things [04:08] under all that hair :) [04:08] StevenK: but just think of the fun you had :) [04:08] Hah === EdwinGrubbs is now known as Edwin-zz === Edwin-zz is now known as Edwin-zzz [04:08] It wasn't that bad, I'm just curious why I could only get close, but not all the way [04:09] StevenK: old LP code did security checks at the browser layer [04:09] StevenK: blueprints is old LP code [04:09] (I can grab a specifications object from lplib, and iterate over it, but it returns nothing) [04:10] heh [04:10] StevenK: it has an entry, but nothing exported [04:10] StevenK: mildly shit [04:11] thumper, lifeless: To be perfectly honest, I did it for shits and giggles, while I was bored, so I'm happy enough to toss the work away. [04:11] StevenK: no worries [04:11] StevenK: I would love to see it happen [04:11] thumper: Oh, I fixed that. I can post a diff if you have tissues to stem the bleeding [04:12] StevenK: I've more a problem with who sets what [04:12] :) [04:12] I was also curious why I couldn't export Choice() elements where the vocab is in quotes, but can if it's a real object. [04:13] Right, now I get what james_w is blocked on. [04:13] Edwin-zzz: ah, yes [04:13] Edwin-zzz: so thats high python time [04:13] StevenK: it'll have to do with the method trying to work out what is valid [04:13] lifeless: When did you get home, by the way? [04:13] Edwin-zzz: I'd get a profile trace of that on [qa]staging. Will mail you. [04:15] thumper: Hm, I hadn't considered that, but it would make sense [04:16] Starting to seriously consider a nanna-nap, and it's only 3:16pm [04:25] StevenK: 10:20am arrival [04:25] lifeless: At home, or the airport? [04:25] jtv: so, we're experimenting in testtools and a few other projects with [04:25] StevenK: airport, home @11 [04:26] lifeless: Landed at 0825, home at 1140 [04:26] StevenK: The empty collection is probably because of the lack of a launchpad.View adapter for ISpecification. [04:26] jtv: wishlist = fallback, medium = 'something we thought worked doesn't', critical = 'blocks project doing a release' [04:26] lifeless: the awkward marriage between the "problem reporting" and "task tracking" faces of bug trackers has bothered me for a long time, so I'm all on board… if you've been thinking about this, I'd be happy to introduce you to kirit for constructive discussion. [04:26] jtv: I had a great discussion with persia - theres a commons problem too. [04:27] bugs are global scope; work prioritisation is local (FSVO local) scope [04:27] wgrant: Ahh. However, I'm now not going to talk about it, since james_w has already done work on it. [04:27] spm: Do you know much about Puppet, and is it something we should be looking at for Launchpad configuration, scheduling or anything? [04:27] stub: I know a bit :) - no, no and no. [04:28] stub: the sysadmins will be using it to manage a growing set of services; for what we're doing/developing we should effectively ignore it, for now. [04:28] wondering if it was useful for readonly switch, or LPCONFIG type stuff. [04:29] it may be able to replace the deployment scripts eventually. [04:29] dunno about the readonly angle; offhand anyway. [04:29] perhaps setting a feature flag would be best for readonly. [04:30] it would propogate to the slave, be found there and be locked on until someone pokes more directly. [/wildarse thought from jetlagged person] [04:30] 'cept feature flags are in the database, and changing to read-only mode switches to a database that was broken out of replication before the switch was set ;) [04:30] stub: is that ordering changable ? [04:31] No - breaking the slave out of replication involves removing the replication triggers on every table and subsequent locking. [04:31] And I guess it complicates the case where you go to read-only because you lose the master. [04:32] Anyway - we can't really ask the database if we are in read-only mode, because we need to know if we are in read-only mode to decide what database to talk to. [04:34] gotcha [04:34] the ini file you added is probably simplest for now [04:34] wgrant: And ohloh is still counting lines of source code, after 1 restart and, what, 3 weeks? [04:35] stub: not vast amounts no; but will be in Syd next week doing a course on same. [04:35] StevenK: At least it's on step 3 now! [04:35] But it has been for a week [04:35] I think we should stop using Zope's email delivery, instead storing emails in the database and having a cronscript or daemon that does the delivery. Pretty trivial, easier to improve later with things like delivery failure, and sidesteps the SMTP ZCML gumph. [04:35] StevenK: I think it's even slower than Launchpad git imports used to be. [04:36] stub: I'd like to know whats up before we reimplement exim/postfix - if you see what I mean. [04:36] stub: If you suggest writing EmailJob, I Will Find You [04:37] Nothing so complex :) [04:38] lifeless: At the moment appservers spool emails to the SMTP server during request. If we fix queued delivery, the appservers spool emails to the SMTP server in a separate thread. But why have the appservers do it at all? [04:39] stub: the expansion from intent->mails I'm delighted to move out of webapp request handling [04:39] stub: I don't really care if thats a Job or a thread. [04:40] spm: just realized the humorous chance I missed Sydney… to go around telling everyone how great their city and country are and, if this is just a local capital, how incredible Canberra must be then. [04:40] stub: mail sending is sometimes massively slower than expected, and we should fix that. [04:40] stub: at the moment the appservers spool *after* the commit *before the request ends* [04:40] which is a little odd :) [04:40] lifeless: Yes. In request delivery is slow, queued delivery is broken. We can fix queued delivery upstream, or move to a different model which I think is better in the long run. [04:41] I'm suggesting still allowing the appservers to assemble the actual emails, but stuff them into the database rather than do the delivery themselves. [04:42] Probably the same amount of work as fixing queued delivery. [04:45] stub: perf wise I'd expect it to be slower [04:45] stub: local mail spools /should/ be millisecond fast to accept things [04:46] anyhow [04:46] halt() [04:46] Anything sending more than a couple of emails from a request is probably a bug. [04:46] pickle vs. store.execute() [04:47] wgrant: Such as, say, updates to bugs? [04:47] StevenK: They don't. [04:47] StevenK: They use an external process. [04:47] StevenK: But still manage to be mortifyingly slow. [04:47] Pity, I was hoping to be ironic [04:48] wgrant: Agreed. But we can't control how long the SMTP server we are talking to will take before the email is handed off, unless we get a dedicated one we can turn off stuff like DNS checks etc. [04:48] stub: True. [04:49] stub: we have a dedicated SMTP server [04:49] stub: *per appserver* [04:49] We talking to localhost now? Ok. [04:59] yeah [05:09] thumper: Just reading meeting notes. Thanks for reducing the mailman query counts! Its a big burden on the db. [05:11] jtv: heh [05:12] jtv: it's .... different. big country town with the amenities (to some degree) of a city. [05:12] You're saying it's a bureaucratic amusement park at the end of a fat fibre-optic cable? [05:13] close [05:13] "You're saying it's a bureaucratic amusement park at the end" [05:21] It just became a whole lot less impressive. [05:22] It's Canberra. It is far less impressive than even your least impressive impression. [05:27] some of the more ... rigid bureaucratic side has changed, but it's still very much a town that revolves around federal govt. and that has implications right thru the entire place. unf, usually in painful ways. [05:28] flip side. I'm a 20min drive from the city centre; yet from our back deck can see paddocks with sheep/horses across the valley. We get Kangaroos < 50metres from our front door (I have pics!). That's pretty special. [05:37] haven't we fixed this: http://launchpadlibrarian.net/58406579/vcs-imports-wordpress-trunk.log at least twice already? [05:38] spm: ^^ [05:38] ugh [05:38] actually - I wonder - I came across this doing some simple bzr ops last week - don't recall which server offhand. [05:39] mwhudson: which importd what that? [05:39] was* that [05:39] spm: i'm a twenty minute _walk_ from wellington cbd and not much further from rural bliss than you :-p [05:39] :-) [05:39] spm: well, https://code.launchpad.net/~vcs-imports/wordpress/trunk [05:40] spm: ahh, seems there's more than one kind of failure :( [05:40] spm: seems it's galapagos that's doing the nowhoami thing [05:41] ta [05:48] spm: I'm 20m from another entire city ;) [06:31] stub: np, I might tackle the methods one by one, but I want the xmlrpc server less loaded [07:43] https://launchpad.net/~mwhudson/+karma -> "Michael Hudson-Doyle's karma has expired. "Total karma: 20838" [07:43] um? [07:43] Does anybody have an idea how we can get out of testfix again? [07:44] mwhudson: could that mean "Some of you karma has expired?" [07:44] mayhap [07:45] It can also mean that the karma cache is being updated. [07:45] Sometimes a couple of the karma totals will vanish for a few minutes while that happens. [07:45] Or, in this case, all of them. [07:46] could be [07:46] Everyone is similarly afflicted. [07:46] Which is rather suspicious indeed. [07:55] It looks like more windmill test failures. [07:56] * jelmer waves to mwhudson, wgrant [07:56] Morning jelmer. [09:12] Hello [09:37] Hi mrevell! [09:38] hello henninge [09:38] mrevell: I just thought that you might not yet be aware of the fact that we moved the 10.11 release back by a week. [09:39] The guy in #launchpad looks like he could do with some commercial subscription help. [09:39] mrevell: sorry for having kept you out of the loop here. [09:40] henninge, Thanks for letting me know now. So we're going for the 17th? [09:40] wgrant: thanks, will talk to him. [09:40] wgrant, thanks [09:40] heh [09:40] mrevell: yes, I just emailed the list. [09:40] Ah, I see your mail henninge [09:40] mrevell: you go and talk ;) [09:41] What's this December "Bug Jam" thing? Does the following cycle not start until January? [09:42] henninge, I saw a discussion where I think the release was going to 00.00 UTC. Is that still the case? [09:43] mrevell: no, I am proposing 10:00 UTC [09:43] wgrant, The idea was that rather than having a mini-cycle in December, we'd spend a couple of weeks doing nothing other than close bugs (not necessarily fix...) [09:43] Heh. [09:43] OK. [09:44] mrevell: I had proposed 22 UTC for the 10th because I already knew that Tom would not be around. [09:44] wgrant, So, we could just have one week of bug jam and a full-sized December cycle [09:44] henninge, Ah, I see. [09:44] mrevell: but with more LOSAs not there, we scratched the 10th completely and since Tom is there on the 17th, we can do it at 10:00 [09:44] henninge, Are we pretty confident of the date and time? I mean, can I announce it? [09:44] mrevell: it's not finalized yet, no [09:44] oop, public channel ... [09:45] ;-) [09:45] but I don't expect any more problems. [09:45] heh, that's not a problem :) === almaisan-away is now known as al-maisan [10:51] jelmer: Hi. [10:51] Hey, I'm running make on a new branch on a clean Maverick install ... I'm getting a permission error when I run make (clean, schema and run so far) [10:51] Any ideas? [10:51] wgrant: Hi [10:52] mrevell: Can you pastebin the trace? [10:52] jelmer: I've addressed your comment on https://code.edge.launchpad.net/~wgrant/launchpad/destroy-distroseries-lucilleconfig/+merge/38648. Anything else? [10:53] wgrant: Yes, I need to land your branch. :-) I'll send it off to ec2 today. [10:54] StevenK, Thanks, Here it is: http://pastebin.ubuntu.com/523776/ .... that's just the last few lines ... do you need the full thing? [10:54] jelmer: Thanks! [10:55] mrevell: I normally fix that with "sudo rm -r /var/tmp/bazaar.launchpad.dev". [10:55] I think Apache creates it or something. [10:56] Oh, simple as that eh? Thanks wgrant, I'll give that a go. [10:57] whoop, that worked for make clean ... thanks wgrant and StevenK [11:15] Morning, all. === al-maisan is now known as almaisan-away === mrevell is now known as mrevell-lunch === deryck_ is now known as deryck === mrevell-lunch is now known as mrevell [14:57] * lifeless yawns === stub1 is now known as stub === almaisan-away is now known as al-maisan [15:25] hi jml [15:25] lifeless: hi [15:27] flacoste: jml: since we're all awake, perhaps we should continue our long running voice discussion [15:31] lifeless: on another call right now. [15:37] kk [15:56] gmb or allenap, could one of you spare time for an easy review? [15:56] deryck: Sure. [15:56] allenap, thanks! https://code.edge.launchpad.net/~deryck/launchpad/allow-reporter-fixed-released-unsetting-664096/+merge/39754 [16:03] lifeless: maybe we could have a call later today [16:03] sure [16:06] sinzui: hello [16:07] hi jml [16:08] sinzui: when do you think we're supposed to have our call [16:08] next week -1 hour? [16:09] sinzui: I'm happy with that. Britain changed timezones during my flight home today === benji is now known as benji-lunch [16:09] okay [16:09] sinzui: so I'm not sure when anything is [16:10] jml: you are my only meeting on Mondays. You can fit me in at your convenience [16:10] sinzui: cool. [16:10] sinzui: did you want to chat today? [16:10] sure [16:10] now? [16:10] yeah. === deryck is now known as deryck[lunch] [16:22] Ursula: hi [16:22] https://devpad.canonical.com/~lpqateam/qa_reports/deployment-stable.html is empty? [16:22] Ursula: bah, browser fail. ignore that question. [16:24] Ursula: however [16:24] Ursula: please do look - Revision 11801 is bad: possible blocker. is reported 4 or 5 times :) [16:26] gary_poster: hey, an LP user has asked me for any info on this issue in #launchpad https://answers.launchpad.net/moin-openid/+question/110123; you were looking at it at one point, any notions about it or who i might point the user to for more info? [16:29] Bug 664060 needs QA [16:29] <_mup_> Bug #664060: bug supervisor should be able to configure bugtracker for projects [16:42] lifeless: so, now that edge is almost gone, are you going to tackle the other subdomains next? [16:43] jml: thats a more complex question, and would benefit from specific discussion about it. [16:44] jml: the complexities for it are: [16:44] - are they part of the UI/ease of use story? [16:44] - impact on performance (more domains == more SSL handshakes, but also potentially more parallelism [though we don't do this :P so its a bit of a no-brainer today] [16:45] - impact on vostok [16:45] jml: I have no immediate plans to do anything to/for/or about the bugs etc domains [16:45] jml: but perhaps you meant some other set of subdomains [16:56] https://bugs.launchpad.net/software-center-agent/+bug/627608 needs qa [16:56] <_mup_> Bug #627608: Got a 401 on a fresh purchase [16:58] jml: We did ~ 2200 commits to trunk in the last year. [16:59] jml: our velocity in terms of commits-per-month for the last two months is about the same as for the last 12. [16:59] jml: 20 hours per commit [16:59] per dev [17:01] (given a nominal 2000 hours/year work period) [17:16] lifeless: interesting [17:16] lifeless: because anecdotally I'd say committing to trunk is getting harder. [17:16] jml: there sure is a lot of friction we need to fix. [17:18] lifeless: fwiw, I meant the bugs etc subdomains. [17:18] lifeless: but I do realize it's a big question. [17:18] 11824-7230 = 4594 over the last two years [17:19] jml: I think the team size has grown a bit over two years? === benji-lunch is now known as benji === deryck[lunch] is now known as deryck === lifeless changed the topic of #launchpad-dev to: Performance Tuesday | Launchpad Development Channel | Week 1 of 10.11 | PQM is open | firefighting: - | https:/​/​dev.launchpad.net/​ | Get the code: https:/​/​dev.launchpad.net/​Getting [17:25] lifeless: I'm not convinced it has. Anyway, it's easy enough to see how the number of distinct committers has changed [17:25] jml: indeed, I'm doing very crude stats just now - log | less :) [17:25] lifeless: well, easy-ish. bzr has a way to go before querying logs is as easy as SQL === al-maisan is now known as almaisan-away [17:41] lifeless: reckon it's worthwhile to file bugs on the remaining parallel testing work? [17:52] * jml gone, back later [18:03] jml: not really; there is a parallel test job; looking at that will show whats broke [18:15] statik: shall we skip our call today? we caught up late last week .. [18:16] lifeless: that sounds good to me [18:27] are there known bugs in reading archives of private mailing lists that a lp user is subscribed to? [18:27] I'm unable to pass the openid "Continue" button. [18:29] ugh [18:30] http://python.mirocommunity.org/video/1186/djangocon-2009-django-is-obsol is quite interesting [18:31] Is this a follow up to iamcal's "Why I Hate Django" ? ;) [18:31] no [18:31] its about evolution [18:32] in a way, so was cal's talk [18:32] well, it might be then :P [18:32] but, I'll refrain from commenting further until I've watched the presentation [18:37] lifeless, would be nice if there was a transcript there - it would be nice to just skim the facts of the argument [18:38] hah.. onions spoil all kinds of apps [18:38] Some might say "minimize window" is an onion. [18:45] SpamapS: you'll like the 'templates will finally die' line [18:47] I stopped at about 15 minutes.. I get his point.. rethink.. multi-threaded.. etc. ;) [18:47] SpamapS: he switches themes [18:47] lifeless: even livejournal figured out that you can do the various bits of the template asynchronously server-side using gearman. [18:48] lifeless: oh very well.. starting back up.. ;) [18:48] lol [18:48] SpamapS: only if you're interested [18:48] I'm very interested [18:48] One thing I am starting to think about.. is why hadoop is the only one anybody mentions [18:49] map/reduce isn't that hard! [18:49] he mentioned cassandra dinomite etc [18:49] Yeah I mean the map/reduce frameworks. [18:55] lifeless: so the last time I heard this argument, it was for xslt [18:56] CSS is obviously a much simpler way to do presentation than xslt.. [18:56] yeah [19:13] flacoste: ping [19:41] awol for a bit [20:05] leonardr: hi there, is there a way to define a method in lazr that returns void? I have a write_operation method which seems to cause a subsequent GET on the server because launchpadlib seems to do self.resource.lp_refresh() if the return code is 200 and the method is post [20:06] leonardr: I tried to redefine the method in question as a factory operation but then it expects the method to return the object created rather than void, which results in a ComponentLookupError for None [20:06] cr3: https://bugs.launchpad.net/launchpadlib/+bug/249950 [20:06] <_mup_> Bug #249950: Stop refreshing after every POST named operation [20:07] no :| [20:07] leonardr: thanks for the reference, good to know [20:08] cr3, hopefully it's just an annoyance? [20:09] leonardr: a performance annoyance where each call results in two calls [20:10] leonardr: a crappy workaround might be to convert the method from a write_operation to a read_operation, but I'm not sure how much data I could encode in the url [20:11] cr3: if it helps, i'm about to start on a big web service project and i could fix this problem as a side effect [20:13] leonardr: in the meanwhile, how acceptable would it be for me to define my own decorator called export_void_operation which would derive export_write_operation and setStatus(201) in the overridden call method? [20:14] cr3: that's not good. you don't want to send 201 at all--you'd be lying [20:14] how bad a performance problem is this? [20:14] if it's absolutely awful i can spend some time pretty soon figuring out the best way to fix it [20:15] * mars \o/ devel is Green once again! [20:16] leonardr: it's not that awful, it's just that I know myself well enough that I'll probably forget to fix this later. I can take a note and wait, no worries [20:17] cr3: what we want is something like export_void_operation + sending a Cache-Control header or something that says 'you just made the object dirty, you need to refresh' [20:31] leonardr: if I want to return an object which contains a reference to another object in the same call, can that be done? [20:31] cr3: you mean send both objects at one? [20:31] that's not possible [20:32] unless you can return a list of objects--that might work, but i doubt it [20:32] leonardr: yeah, both at once to spare the subsequent get on the referenced object [20:33] cr3: there's a general feature planned that will let a client tell the server it wants certain objects expanded, but it's not planned for a long time--i need to rationalize the web service design first [20:34] leonardr: maybe it's a lesson for me to create even coarser grained objects [20:35] cr3: could be, if this is a really bad problem. would it help if this data was cached on the client side, or is even getting it once a big performance problem? [20:36] leonardr: whats the big web service project? [20:39] lifeless: refactoring the named operations into a few 'families' (search/filter operations and so on) so that each resource type in the web service doesn't have 5-20 miscellaneous and unstandardized operations dangling from it [20:39] make it easier to learn and use [20:39] i'm working with jml on it, but the desktop thing has intruded for several months [20:43] lifeless: per the db-patch rules, i believe i need a review from you on this: https://code.edge.launchpad.net/~jcsackett/launchpad/migrate-official-bool-data-627631/+merge/39583 [20:44] jcsackett: you need one from stub to assign the patch id, to land it [20:44] lifeless: i know, but the docs say i need one from the architect as well. that would be you. :-) [20:44] yes [20:44] but not to land [20:45] the docs also say that :) [20:45] dig. i was just pointing out the mp to you. my understanding is that stub is out, so i'll have to chase him down later. [20:45] there's already a request for him on the MP as well. [20:46] there is a 'request a review' buttton on the mp - my preference is for you to use that for me too :). Thanks for letting me know. [20:46] lifeless: i used that for you too, but it was while you were at uds, so this was sort of pushing it back into awareness. :-) [21:06] rockstar: abentley: thumper: standup? [21:16] matsubara-afk, Ursula: ping [21:53] jelmer: Did you get around to EC2ing that branch? [22:11] sinzui: hey [22:31] lifeless: so what is the process then for landing something without a review? [22:32] lifeless: I have my very boring enum change for blueprints [22:33] https://dev.launchpad.net/PolicyAndProcess/OptionalReviews [22:33] Activities [22:33] Submit the branch to create an MP (our toolchains can look at this and it provides a location for a post landing review if the branch has that done to it). Self review with review type 'unreviewed'. Land via the normal landing process. [22:34] we may find this needs tuning [22:34] e.g. review type none/code [22:36] jml: have you crashed? [22:41] thumper: one of my branches got merged into db-devel rather than devel. i need to do stuff that depends on it. do i have any option other than to work on a db-devel branch? [22:41] wallyworld_: land it again. [22:41] wallyworld_: to the right place. [22:41] wallyworld_: did you branch from db-devel? [22:41] ok [22:41] wallyworld_: just be sure that you don't suck all of db-devel in. [22:42] no i branched originally from devel [22:42] wallyworld_: or more importantly, did you branch or merge from db-devel since the last rollout? [22:42] wallyworld_: in which case, land it on devel as well [22:42] thumper: 'release' - not rollout ;) [22:42] wallyworld_: bzr's merge detection will handle it [22:42] with that branch i have only merged into it from devel [22:43] not sure why it landed in db-devel [22:43] the default is bong. [22:43] mailing [22:43] lifeless: the default is due to branch stacking [22:43] lifeless: and that is all [22:44] thumper: i think we are still in textfix mode so i'll have to wait to land it again [22:44] thumper: its the series, we can change it right ? [22:45] lifeless: if we had an easy way to say push and stack on db-devel when needed (that is tested and simple to use) then we could switch relatively easily [22:45] thumper: I realise we need to do a repo fetch [22:45] thumper: we can switch trivially [22:45] lifeless: devel isn't stacked [22:45] thumper: right, but branches stacked on db-devel may need db-devel only revisions. [22:45] lifeless: right [22:45] so its devel.fetch(db_devel), then change the default series. [22:46] 4 lines of python + a losa [22:46] we don't need any code changes [22:46] right [22:46] just the fetch [22:49] no [22:49] not even the fetch [22:49] branches are stacked on aboslute paths [22:49] not shortcuts [22:49] it is more the overhead of new db-devel branches [22:49] but if we don't care... [22:49] * thumper shrugs [22:49] thumper: devel branches are the common case [22:50] thumper: they pay massively today ;) [22:50] thumper: please do it [22:50] thumper: and let launchpad-dev know [22:50] * thumper nods [22:50] (unless you think its wrong to change it) [22:53] Nothing depends on the lp:launchpad alias? [23:11] flacoste: ppr needs 'max', I think :) [23:18] losa ping [23:18] yo [23:18] https://pastebin.canonical.com/39248/ [23:18] can you add that into [23:18] https://edge.launchpad.net/+feature-rules [23:20] sure. what does it all do? timeouts against specific pages? [23:20] yes [23:20] as per https://dev.launchpad.net/LEP/FeatureFlags [23:20] just never seen that style before [23:20] if you look at the lpnet timeout report [23:20] these are the current hard timeouts [23:20] lifeless: Exempting all the main timeouts and slashing the limit again? [23:21] I looked at the PPR to get a feel for how things are going [23:21] wgrant: raising slightly for stuff hurt by 8.4 [23:21] haha [23:21] Bah. [23:21] lifeless: OOPS-1766ED2295 [23:21] wgrant: will lower the timeout again once we've caught up with that [23:21] spm: rotlf [23:22] spm: that was near-instant, right ? [23:22] yah, purty much [23:22] spm: what was the traceback ? [23:22] Retry: duplicate key value violates unique constraint "feature_flag_unique_priority_per_flag"

[23:22] ah [23:22] I had 4 duplicated [23:22] yes. given the timeouts... [23:22] change the second ' 4 ' to ' 5 ' and so own down the page. [23:22] s/own/on/ [23:24] hrm/ I think that's applied. it doesnt' exactly let you know that it has done anything. [23:24] please do file bugs on this interface [23:24] yeah, has. [23:24] its your primary knob for controlling LP in real time. [23:24] Hm,. [23:24] Do we really need such a massive freeze now that most stuff should be QA'd immediately? [23:24] its bare bones now, but it doesn't have to stay this way. [23:24] A week to QA db-devel changes seems excessive. [23:24] wgrant: the thing I proposed has a much smaller critical section [23:25] wgrant: we're still a week behind in QA right now. [23:25] wgrant: until we've caught up, we haven't caught up. [23:25] True. [23:26] spm: thanks, in 60 minutes we should see a drop to near-zero hard timeouts on lpstats [23:27] lifeless: Don't worry, Soyuz will fix that :) [23:34] sinzui: Why does DistributionMirror live in Registry? [23:37] aren't you meant to be stufying ? [23:37] Silence.