=== mwhudson_ is now known as mwhudson === mrevell is now known as mrevell-lunch === mrevell-lunch is now known as mrevell === gmb_ is now known as gmb === mera_naam is now known as gauravdott === salgado is now known as salgado-lunch [18:06] hello MootBot [18:17] Rinchen: is there a meeting [18:17] ? [18:18] Rinchen, bigjools: The calendar says it's at 18:00 UTC... [18:18] wtf [18:19] 7pm - will definitely not be making that then [18:19] We really need to move this meeting next week [18:20] +1 [18:20] I may be the only North American that supports that. [18:21] On the 6th I think is when NZ does their timezone change [18:21] The argument would be in the European favour too if it wasn't for all us cheap Americans. [18:21] sinzui, spoken like a true Canadian [18:22] * sinzui gets out the visa [18:22] and the mastercard [18:22] lol [18:22] badumtish [18:22] :-) [18:23] I'VE ALWAYS LOVED CANADA [18:23] at the very least we can go to 17:00 next week. That should be 7am for thumper [18:24] I still hold Canada responsible for global warming [18:24] And Brian Adams [18:24] and maple syrup [18:24] wait...that's nice! [18:25] * sinzui likes maple syrup [18:25] preferably doused on some pancakes [18:25] bigjools: There is a fashion in the US to lace sausages and bacon with it. [18:26] ewww gross [18:26] there's only one thing to have with bacon [18:26] bigjools: the first bite is fine, it's the second bite that you think 'ewww gross' [18:26] more bacon [18:26] bigjools: I think I agree with you [18:26] except if it's Jono [18:26] lol [18:27] There ca be only one [18:27] mmm bacon. You're making me hungry for lunch [18:27] bacon === salgado-lunch is now known as salgado [18:38] jsk! [18:49] jsk? [18:49] jsk: translations is hiring [18:50] jtv... did you notice the similarities between SKJ and jsk ? :-) [18:50] jsk: come back, all is forgiven! [18:51] Rinchen: for that reason alone we must have him back. :-) [18:51] hnnnnnnnnnnngh [18:51] Rinchen: ah, and the K in SKJ became a GTF Contributor today. [18:51] * gmb hands mwhudson a large coffee. [18:52] jtv, well, add JJS = Joseph James Stanford (joey) and you can add me [18:52] too [18:52] Rinchen: no, that sucks :) [18:52] Rinchen: you're already in the GCP, no? [18:52] lol [18:53] jtv, no idea [18:54] Rinchen: but you're in the GTF now, right above Journal of Japanese Studies. [18:54] lol [18:54] domo [18:57] mwhudson: I feel the same way [18:58] morning thumper [18:58] Rinchen: morning [18:58] ahoy hoy [18:58] * flacoste cheers kiko [18:58] ahoy me matey [18:59] 45 seconds on the atomic clock [18:59] i say, free supply of meth to the down under participants if they agree to hold the meeting an hour earlier [18:59] * Rinchen laughs. [18:59] Hmm.. my clock must be out [18:59] intellectronica, I don't think Thumper needs meth [18:59] T - 5 [19:00] and on that note..... [19:00] #startmeeting [19:00] Meeting started at 20:00. The chair is Rinchen. [19:00] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [19:00] Welcome to this week's Launchpad development meeting. For the next 45 minutes or so, we'll be coordinating Launchpad development. [19:00] [TOPIC] Roll Call [19:00] New Topic: Roll Call [19:00] me! [19:00] me [19:00] me [19:00] me [19:00] me [19:00] me [19:00] me [19:00] me [19:00] me [19:00] me [19:00] me [19:00] me [19:00] me [19:00] me [19:00] me [19:00] me for 30 mins [19:00] me [19:00] me [19:00] me [19:00] me [19:00] me [19:00] me [19:00] mrevell, mpt ? [19:00] me [19:00] me [19:00] me [19:00] barry is still sick< [19:01] apologies from allenap [19:01] me [19:01] me [19:01] I'm sick too [19:01] Rinchen: mpt said somethng about going to the other side of the world earlier, so maybe he's on a flight. [19:01] me [19:01] anyone missing from your teams flacoste, statik ? [19:02] nope [19:02] SteveA? [19:02] all present and me'd [19:02] Rinchen: apart barry, no one [19:02] cool thanks [19:02] [TOPIC] Agenda [19:02] New Topic: Agenda [19:02] Rinchen: besides i'd love to have statik on my team, but he got one of his own :-) [19:02] * Next meeting [19:02] * Actions from last meeting [19:02] * Oops report (Matsubara) [19:02] * Critical Bugs (Rinchen) [19:02] * Bug tags [19:02] * Operations report (mthaddon/herb) [19:02] * DBA report (stub) [19:02] * Sysadmin requests (Rinchen) [19:02] * New packages required (salgado) [19:02] * A top user-affecting issue (mrevell) [19:02] * Doc Team report (mrevell) [19:02] * Blockers [19:03] [TOPIC] Next meeting [19:03] New Topic: Next meeting [19:03] There was some rather vocal pre-meeting discussion about how the 18:00 UTC meeting time no longer works for the European team members now that the Northern Hemisphere is on DST. [19:03] DST ends in NZ on the 6th which would mean that next week could start the meeting at 17:00 UTC and this would restore the meeting time to the usual hour. I understand this is still not convenient for the eastern Europeans but it would be 7am in NZ allowing those folks to participate. [19:03] ah, 17:00 UTC is 5am [19:04] Or midnight for me [19:04] Even *I* think that would be harsh... [19:04] hmm I must have misread timeanddate.com then [19:04] for NZ take UTC and add 12 hours [19:04] I could do 6am [19:04] but 5am is a little harsh [19:05] yeah, indeed [19:05] we could move the meeting up [19:05] but even at 14:00 it'll be 2am [19:05] me [19:05] vote? [19:05] votes suck [19:05] :-) [19:05] yeah, the antipodeans are underpresented [19:06] because they are mostly asleep still [19:06] thumper: we can vote on that too :) [19:06] let's open a Launchpad poll!! [19:06] flacoste: I think you mean under*rep*resented. [19:06] * carlos hides [19:06] kiko, opinions [19:06] Unless they're sartorially shoddy... [19:06] gmb: that also ;-) [19:06] it's going to suck for *someone* whatever we do [19:06] I think we shouldn't change the date, as much as it pains northerners [19:07] or the time [19:07] me [19:07] yeah, even the meeting spreadsheet doesn't help us due to our diversity [19:07] how about rotation, so it only sucks some of the time? [19:07] this meeting time is totally geared towards tim -- if we change it to be one hour closer to death from him, we've failed [19:07] my only suggestion would be to have rotation [19:07] intellectronica: exactly [19:07] a lot of people would miss meetings, I suspect [19:08] rotations are really confusing [19:08] well, here's my proposal [19:08] they are [19:08] thumper: just move back to London :) [19:08] I agree because they wouldn't know when the meeting would be [19:08] The sparsest population is San Francisco and Denver. Should we move the meeting to 13:00 [19:08] an email reminder can help [19:08] thumper decides whether it's 18:00 or 17:00 UTC [19:08] and we try a rotation for the team leads meeting for 2 weeks [19:08] if it works for that smaller group we can try it for the larger group [19:08] (which starts on Monday) [19:09] 18:00 [19:09] is that workable for the next 2 weeks? [19:09] ok by me but I'm not affected [19:09] anyone deeply opposed? [19:09] any chance to get a more relaxed excuses for missing meetings then? [19:10] I'd say take that discussion up with your manager. [19:10] ...who is sitting right next to him [19:10] I have no problem with it so long as it's not a regular occurrence and someone covers for you [19:10] covers and provides feedback about the meeting of course [19:10] danilos, it's only one meeting a week -- it's not like you don't get a lot of flexibility otherwise. [19:11] Is this meeting still considered essential for everyone now the teams have grown and been reorganized? (assuming yes, but I don't know if this has been discussed) [19:11] I can see that if it's after 10pm or before 7am it's nasty [19:11] I think the meeting is one thing that helps ensure people are on the same page in a number of things [19:11] kiko: that's true, but see stub [19:11] danilos, I'm really sympathetic to stub, jtv and thumper for that reason [19:11] let's discuss this again after you've experimented with rotation for for the team leads meeting. no point going on about this for hours here and how [19:11] okay [19:11] fair enough. thanks [19:12] kiko: i don't care what you do, just be sure to send a very clear email to the list stating when the next meeting is ;) [19:12] barry, in what timezone? :) [19:12] heh [19:12] [AGREED] try rotating the team leads meeting to see how well that works for everyone. If it works well we'll consider rotating the larger LP meetings. [19:12] AGREED received: try rotating the team leads meeting to see how well that works for everyone. If it works well we'll consider rotating the larger LP meetings. [19:12] [AGREED] keep meeting at 18:00 for the next 2 weeks [19:12] kiko: us eastern of course [19:12] * kiko kicks fucking MootBot [19:12] [AGREED] keep meeting at 18:00 for the next 2 weeks [19:12] AGREED received: keep meeting at 18:00 for the next 2 weeks [19:13] [TOPIC] Actions from last meeting [19:13] New Topic: Actions from last meeting [19:13] both have been worked on [19:13] flacoste, any commentary on the librarian? [19:14] none is ok [19:14] Rinchen: kiko and I had a call, and it seems that the issue is similar to the app server [19:14] Rinchen: so i'm investigating that first [19:14] k, thanks. We'll come to that topic shortly [19:14] [TOPIC] Oops report (Matsubara) [19:14] New Topic: Oops report (Matsubara) [19:14] Today's oops report is about bugs 209892, 211394, 211423 [19:14] Launchpad bug 209892 in launchpad-bazaar "LaunchpadValidationError raised while registering a branch using the xmlrpc interface" [Undecided,New] https://launchpad.net/bugs/209892 [19:14] Launchpad bug 211394 in launchpad-bazaar "OOPS deleting a branch" [Undecided,New] https://launchpad.net/bugs/211394 [19:14] Launchpad bug 211423 in malone "OOPS in the email interface when inactive account tried to file a new bug" [Undecided,New] https://launchpad.net/bugs/211423 [19:14] mwhudson, since you commented on #209892, and wrote that code, can you take it? [19:15] thumper, who from your team should take 211394? [19:15] intellectronica, can you take 211423? [19:15] matsubara: oh right yes [19:15] matsubara: I'll work with abentley on 211394 [19:15] matsubara: i can take a look at 211423, since i'm doing emaily stuff anyways [19:15] that was smooth! thanks guys [19:15] I'm done Rinchen. back to you [19:15] [AGREED] mwh to work on bug 209892 [19:15] AGREED received: mwh to work on bug 209892 [19:16] [AGREED] intellectronica to look at bug 211423 [19:16] AGREED received: intellectronica to look at bug 211423 [19:16] Launchpad bug 211423 in malone "OOPS in the email interface when inactive account tried to file a new bug" [Undecided,New] https://launchpad.net/bugs/211423 [19:16] I'm trying to do more of these per feedback from the Ozzies [19:16] [AGREED] Thumper and abentley to look at bug 211394 [19:16] AGREED received: Thumper and abentley to look at bug 211394 [19:16] [TOPIC] Critical Bugs (Rinchen) [19:16] New Topic: Critical Bugs (Rinchen) [19:16] Launchpad bug 211394 in launchpad-bazaar "OOPS deleting a branch" [Undecided,New] https://launchpad.net/bugs/211394 [19:16] two for today [19:16] Rinchen: +1 [19:16] [LINK] https://bugs.edge.launchpad.net/launchpad/+bug/206654 [19:16] This is the memory issue. flacoste, SteveA - is there anything anyone else can do to help? [19:16] LINK received: https://bugs.edge.launchpad.net/launchpad/+bug/206654 [19:17] Rinchen, SteveA and flacoste have a good plan [19:17] Rinchen, flacoste's working hard on some diagnostic code -- let's wait to see that deployed. [19:17] good deal. I didn't think there was much we could add [19:17] [LINK] https://bugs.edge.launchpad.net/rosetta/+bug/209859 [19:17] jtv, what's your plan for your popularity issue? [19:17] LINK received: https://bugs.edge.launchpad.net/rosetta/+bug/209859 [19:17] Rinchen: ? [19:17] Rinchen: ah, that. [19:18] Rinchen: memory errors are fixed now, so it's not quite as urgent anymore. [19:18] Rinchen: so will look into that in more detail later. [19:18] jtv, should it be high rather than critical? [19:18] yes [19:18] Rinchen: now, yes. [19:18] jtv, have we confirmed the memory error fix works as expected? [19:18] jtv, would you do the honours? [19:18] mthaddon: yes, thanks for the quick rollout [19:19] * jtv does honours [19:19] [AGREED] downgraded bug 209859 to high as it's not as much of an issue now [19:19] AGREED received: downgraded bug 209859 to high as it's not as much of an issue now [19:19] Bug 209859 on http://launchpad.net/bugs/209859 is private [19:19] Bug 209859 on http://launchpad.net/bugs/209859 is private [19:19] heh [19:19] thanks [19:19] [TOPIC] Bug tags [19:19] New Topic: Bug tags [19:19] we have 1 [19:19] intellectronica, javascript [19:19] * kiko snickers as he fixed his! [19:19] https://help.launchpad.net/TaggingLaunchpadBugs [19:20] I approve javascript [19:20] +1 [19:20] +1 [19:20] +2 [19:20] Any objections? [19:20] sounds like a consensus to me [19:20] no [19:20] no [19:20] [AGREED] javascript bug tag approved, intellectronica to update the wiki [19:20] AGREED received: javascript bug tag approved, intellectronica to update the wiki [19:21] [TOPIC] Operations report (mthaddon/herb) [19:21] New Topic: Operations report (mthaddon/herb) [19:21] 2008-03-31 - edge2 died. nothing in nohup.out. restarted. [19:21] 2008-03-31 - Cherry pick 5977 [19:21] 2008-04-02 - edge3 died, no coredump. restarted. [19:21] 2008-04-02 - Cherry pick 5992 [19:21] 2008-04-02 - edge1 died during logrotate. restarted. [19:21] We're going to be testing a new staging update script which might cause staging update errors over the next couple of days. Tom and I will be watching closely. [19:21] Cherry pick 5992 had issues due to the new config format. [19:21] Multiple restarts of both edge and production app servers daily due to memory leaks. [19:21] I'd also like to bring up the issue of rocketfuel-built inconsistencies that I'd mailed to the list [19:22] herb, what's the issue with the staging update script? [19:22] kiko, we're adding an option to allow non DB-import version [19:22] kiko, no issue, just a change in the way we deploy the code. [19:23] kiko, at the moment, non-DB import on staging is manual - we're adding it as an option to the script so it can be consistent and quicker in the future [19:23] gotcha [19:23] nice job! [19:23] Anything else for herb or mthaddon ? [19:23] thx, rocketfuel-built inconsistencies, anyone? [19:23] the deaths of edge due to links? [19:23] ah yes [19:23] mthaddon, you got a reply on list about that? [19:23] it's something to take up with lifeless afaik [19:24] err [19:24] kiko, yeah, but wasn't very revealing - okay, will take up with lifeless [19:24] the deaths of edge due to leaks? [19:24] kiko, most likely. [19:24] leaks make a lot more sense than links :) [19:24] mthaddon, the inconsistencies were pretty minor, right -- just perms? [19:24] LarstiQ, talking on the phone at the same time ruins me :-/ [19:24] kiko, yeah, just perms, but creates noise on a new production code checking script we're putting in place [19:25] further discussion? [19:25] but anyway, that's it from me [19:25] gotcha [19:25] thanks [19:25] [TOPIC] DBA report (stub) [19:25] New Topic: DBA report (stub) [19:25] Currently our full text indexes are only indexing the first 2.5k of text for a row. This is screwing up package searchi (Bug 207969). I'll be landing a patch that turns off this limit so we can test on staging to see if anything blows up. I think the limit is left over from limitations on earlier PG versions. [19:25] I want to have the auth/person split finalized next week and implementation started. I need to go over the options and recommendations with Mark first. [19:25] I've been seeing more idle open transactions being killed by our transaction reaper - fiera and poexport I think. These should be obvious in the OOPS report (server closed connection). If this is a problem and can't be fixed in the short term let me know and we can discuss increasing the timeouts. [19:25] Launchpad bug 207969 in soyuz "ppa search fail to return expected results on some cases" [High,Fix committed] https://launchpad.net/bugs/207969 [19:25] We have two options for migrating to PG 8.3. Do it whenever while the data centre machines are running dapper and take around a 3.5 hour downtime hit, or wait until the DC machines are running hardy and we can run Slony-I. This will allow us to do the migration with a few minutes of downtime. I'm thinking waiting for Hardy unless elmo wants to delay DC upgrades for some reason. [19:25] All for now. [19:26] stub: fyi, those 'poexport' leftovers could be from manual killings of poexport script to solve some problems [19:26] stub, I'm hoping for hardy soon, too [19:26] let's see what the release looks like [19:27] Ok. I can't tell from my end. [19:27] * stub nods [19:27] Thanks stub [19:27] anything further for stub? [19:27] [TOPIC] Sysadmin requests (Rinchen) [19:27] New Topic: Sysadmin requests (Rinchen) [19:28] Hi! Is anyone blocked on an RT or have any that are becoming urgent? [19:28] I know about the usual suspects from last week [19:28] Rinchen, BjornT will be wanting to talk to elmo about setting up a debbugs instance [19:28] Rinchen: #30384 is pretty important to us. [19:28] But it's brand-new. [19:29] kiko: we'll be having a call about it tomorrow [19:29] BjornT, owwsom [19:29] BjornT, let me know how it goes. [19:29] jtv, got it [19:29] any others? [19:29] Rinchen: any eta for mine? [19:29] bigjools, none, or kiko's either. IS is working on several things, many to prep for hardy as I understand [19:30] yeah [19:30] but I'll keep after them [19:30] [TOPIC] New packages required (salgado) [19:30] New Topic: New packages required (salgado) [19:30] jtv, isn't that just setting up launchpad_langpack? [19:30] if any of the branches you're working on right now depends on any library which is not part of the launchpad-dependencies package, come talk to me ASAP. [19:30] salgado, there is a big hardy shakeout happening eh? [19:30] mthaddon: basically, though no longer as standby for production [19:30] will that affect lp-devel-deps [19:31] I thought we'd agreed to use launchpad_staging for that? [19:31] kiko, hardy shakeout? [19:31] yeah, what should we do about python-xml? [19:31] well, the upgrade causing issues left and right with our dependencies [19:31] mthaddon: we feel like messing with the schema. [19:31] mthaddon: it's just for a big branch we are working on [19:31] mthaddon: in general stating is enough [19:31] jtv: well that didn't last long... :( [19:31] s/stating/staging/ [19:31] s/stating/staging/ [19:31] I think in the long term we should replace python-xml with something else [19:32] mthaddon, hey, this is software engineering! :) [19:32] I'm currently running and older copy per salgado's email [19:32] engineering is blowing stuff up. [19:32] salgado: i suggest the ElementTree API [19:32] (which means we make it up as we go along) [19:32] what flacoste said [19:32] jtv, carlos, danilos, is that feasible? [19:32] * intellectronica blows his nose [19:32] stub, (you and me think alike) [19:32] salgado: several libraries provide that interface (lxml, cElementTree, ElementTree, there is even a BeautifulSOupwrapper for it) [19:32] flacoste, ah, there's a wrapper you tell me now!! [19:32] salgado: would need investigation, we are parsing DTD, not XML [19:32] we also use py xml for new branch creation when running make schema [19:33] kiko: not the way we need for our pagetests though [19:33] flacoste, kiko: it to use the ELementTree API with BeautifulSoup [19:33] Rinchen: eh, really? is that not something that just gets imported by the by? [19:34] mwhudson? [19:34] make-dummy-hosted-branches [19:34] mwhudson, I haven't checked it in detail though [19:35] I am concerned that the hardy upgrade will cause big shakeouts in lp-deps and we are skewed further from production [19:35] but I guess we'll just need to keep a special eye out for version upgrades [19:35] and file bugs against ubuntu [19:35] btw [19:35] please escalate ubuntu packaging bugs to joey [19:35] and I'll work with him to make sure they are fixed [19:35] deal [19:35] before hardy releases [19:36] kiko, I don't see what is your concern. the only problem we've seen so far is with python-xml and python-pkg-resources [19:36] this is really important, because otherwise we're at a distro blind spot just filing bugs [19:36] Rinchen: https://bugs.edge.launchpad.net/bzr/+bug/208418 [19:36] Launchpad bug 208418 in bzr "ValueError when trying to pull/merge from a remote repository" [Critical,Confirmed] [19:36] salgado, that's two packages already [19:36] the latter not being in lp-deps so not really a problem [19:36] and counting [19:36] well.. so yes, this problem goes beyond deps, salgado [19:36] what's your point? should we not worry? :) [19:37] we should [19:37] okay! :) [19:37] I just don't expect it to be a big deal [19:37] maybe I'm just too optimist [19:37] well, it's a big deal if we need to pin or downgrade packages past the hardy release [19:37] let's make sure we get these fixed before that. [19:37] over and out! send bugs to Rinchen [19:37] [AGREED] there is concern that hardy will affect our dependencies. e.g. python-xml no longer contains a module we need. Devs to provide bugs of this sort to Rinchen for follow up [19:37] AGREED received: there is concern that hardy will affect our dependencies. e.g. python-xml no longer contains a module we need. Devs to provide bugs of this sort to Rinchen for follow up [19:38] [TOPIC] A top user-affecting issue (mrevell) [19:38]