#format IRC
<Ursinha> #startmeeting
<Ursinha> Welcome to this week's Launchpad Production Meeting.  For the next 45 minutes or so, we'll be coordinating the resolution of specific Launchpad bugs and issues. 
<MootBot> Meeting started at 09:01. The chair is Ursinha.
<MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
* flacoste (n=francis@canonical/launchpad/flacoste) has joined #launchpad-meeting
<Ursinha> weeee I love MootBot 
<Ursinha> me!
<sinzui> me
<al-maisan> me
<flacoste> me
<intellectronica> me
<herb> me
<Ursinha> rockstar, ping
<rockstar> me
<Ursinha> henninge is not here
* henninge (n=henning@i577A9673.versanet.de) has joined #launchpad-meeting
<henninge> me
<Ursinha> :)
<Ursinha> cool, everyone is here
<Ursinha> apologies from matsubara and bigjools, both on leave 
<Ursinha> [TOPIC] Agenda
<Ursinha>  * Next meeting
<Ursinha>  * Actions from last meeting
<Ursinha>  * Oops report & Critical Bugs-
<Ursinha>  * Operations report (mthaddon/herb/spm)
<Ursinha>  * DBA report (stub)
<MootBot> New Topic:  Agenda
<Ursinha> right
<Ursinha> [TOPIC] * Next meeting
<Ursinha> it will be xmas day :) so, no meeting
<Ursinha> the thursday after will new year's day, so next meeting will be on Jan 8th, is that okay for you guys? 
<MootBot> New Topic:  * Next meeting
<flacoste> stub is offline doing an internet upgrade
<rockstar> That's more than okay with me.
<Ursinha> flacoste, I saw jtv's mail, thanks!
<Ursinha> awesome
<Ursinha> jan 8th will be
<henninge> I'll be here ... ;)
<Ursinha> [TOPIC] * Actions from last meeting
<Ursinha> None!
<MootBot> New Topic:  * Actions from last meeting
<Ursinha> cool
<rockstar> Ursinha, I was just going to ditch the next two meetings.  :)
<henninge> Wow!
<Ursinha> henninge, what? 
<Ursinha> today it'll be fast!
<Ursinha> [TOPIC] * Oops report & Critical Bugs-
<Ursinha> two oopses and two bugs
<MootBot> New Topic:  * Oops report & Critical Bugs-
<Ursinha> the oopses: timeout on +newaccount (OOPS-1083H1147), and ubuntu/+builds (OOPS-1083D1281), but I couldn't access them in time, they were giving me the permission denied message
<ubottu> https://devpad.canonical.com/~jamesh/oops.cgi/1083H1147
<ubottu> https://devpad.canonical.com/~jamesh/oops.cgi/1083D1281
<Ursinha> al-maisan, can you take a look at the ubuntu/+builds one? I don't know if it's alright, but I don't recall seeing those before
<al-maisan> Ursinha: will do.
<Ursinha> and the newaccount one I guess it's registry
<Ursinha> al-maisan, thank you!
<Ursinha> [ACTION] al-maisan to take a look at OOPS-1083D1281
<ubottu> https://devpad.canonical.com/~jamesh/oops.cgi/1083D1281
<MootBot> ACTION received:  al-maisan to take a look at OOPS-1083D1281
<ubottu> https://devpad.canonical.com/~jamesh/oops.cgi/1083D1281
<Ursinha> sinzui, hi
<Ursinha> sinzui, can you or someone look at that timeout oops, please?
<Ursinha> erm
<Ursinha> let's move to the bugs
<Ursinha> two bugs for bugs team, api related
<Ursinha> bug 308982, bug 296293 
<ubottu> Launchpad bug 308982 in malone "ForbiddenAttribute error when setting private field over webservice" [High,Triaged] https://launchpad.net/bugs/308982
<ubottu> Launchpad bug 296293 in malone "Trying to search through the API for bugtasks passing milestone="url" gives a 500, Internal Server Error" [Undecided,New] https://launchpad.net/bugs/296293
<Ursinha> intellectronica, hi :)
<intellectronica> Ursinha: i'm dealing with both
<Ursinha> intellectronica, awesome! can you set the attributes on the second one, please?
<Ursinha> I'd love to have that fixed
<sinzui> Ursinha: I can, but I think the problems are in the syouz domain
<intellectronica> sure, doing that now
<Ursinha> sinzui, the +newaccount one?
* Ursinha looks again
* sinzui opened the second oops twice. oops
<al-maisan> sinzui: how so?
<al-maisan> ah
<Ursinha> oh :)
<henninge> ee?
<rockstar> oi
<Ursinha> lol
<Ursinha> sinzui, so, what do you think?
<sinzui> Ursinha: This may be a duplicate. bac is has a fix for some readonly items in review now
<Ursinha> sinzui, right, I'll talk to him about it
<Ursinha> didn't have the time to investigate, oops was unavailable
<Ursinha> [ACTION] Ursinha to talk to bac about OOPS-1083H1147
<ubottu> https://devpad.canonical.com/~jamesh/oops.cgi/1083H1147
<MootBot> ACTION received:  Ursinha to talk to bac about OOPS-1083H1147
<ubottu> https://devpad.canonical.com/~jamesh/oops.cgi/1083H1147
<Ursinha> right
<bac> sinzui: i did not address those bugs as it looked like intellectronica was on it.  i can include in my branch if we want
<sinzui> The specific issue in the oops is that the bugs API is not properly documented
<Ursinha> sinzui, oh, you're talking about bugs' bugs
<intellectronica> well, it's not really a documentation problem. when the annotations are fixed the documentation should pick it up just fine
<sinzui> bug 308982 indicates that the bug API exported some of the attributes as mutable, and they are not
<ubottu> Launchpad bug 308982 in malone "ForbiddenAttribute error when setting private field over webservice" [High,Triaged] https://launchpad.net/bugs/308982
<intellectronica> exactly
<Ursinha> well, are you going to keep them intellectronica?
<intellectronica> keep them exported, but correct the annotation, yes
<Ursinha> okay
* sinzui now sees the real oops
<Ursinha> can you comment on the bug properly? guess you're already doing that, but anyway :)
<Ursinha> intellectronica, ^
<intellectronica> doing that
<Ursinha> intellectronica, thanks
<Ursinha> sinzui, and the oops...
<sinzui> Ursinha: I investigated the logintokens this morning. They work (by work, I stole someone's account--they really work)
<sinzui> Ursinha: There was definitely something wrong in the DB yesterday that caused this.
<sinzui> Ursinha: replication perhaps
<Ursinha> sinzui, right. I'll watch it for the next hours/days
<Ursinha> will bring the issue to attention if occurs again
<Ursinha> [ACTION] Ursinha to watch for new occurrences of OOPS-1083H1147 the next hours/days
<ubottu> https://devpad.canonical.com/~jamesh/oops.cgi/1083H1147
<MootBot> ACTION received:  Ursinha to watch for new occurrences of OOPS-1083H1147 the next hours/days
<ubottu> https://devpad.canonical.com/~jamesh/oops.cgi/1083H1147
<Ursinha> thanks sinzui 
<Ursinha> we have three critical bugs
<Ursinha> all fix committed
<Ursinha> one is that launchpad-bugzilla one that was always there
<Ursinha> one is soyuz and another coswe
<Ursinha> argh
<Ursinha> *code
<al-maisan> aha :)
<Ursinha> rockstar, can you set the right status, please please please? :)
<Ursinha> rockstar, good morning, btw :P
<rockstar> Do we need to close out 2.1.12?
<Ursinha> rockstar, we'll need to close it, yeah
<rockstar> I think I'll probably just do the two birds/one stone thing then.
<Ursinha> two birds? lol
<Ursinha> rockstar, thanks :)
<henninge> "Close out" is setting all the statusses on bugs and blueprints to Released, right?
<Ursinha> rockstar, but setting the status of the critical to fix release is fine for now
<Ursinha> henninge, right :)
<Ursinha> all of you, please, having pending items to close, let's do it!
<henninge> Pleeease do that.
<Ursinha> or close or redirect to 2.2.1
<Ursinha> henninge, what do you mean?
<henninge> Mat includes a link to the milestone page in the release announcement and I find the current state of that page less than fitting to be released publicly.
<al-maisan> we did that for the Soyuz 2.1.12 milestone today
<al-maisan> i.e. close it out.
<Ursinha> al-maisan, great, thanks a lot
<Ursinha> henninge, hmm
<Ursinha> mrevell, hi :)
<mrevell> hey there Ursinha
<Ursinha> want to be the special guest ?
<Ursinha> :)
<Ursinha> see what henninge said above, please
<mrevell> Sorry, I haven't been following the meeting, I'm about to go on a call.
* mrevell looks
<Ursinha> mrevell, no problem, you don't have to
<Ursinha> join the meeting, that is
* e-jat (n=fenris@ubuntu/member/fenris-) has joined #launchpad-meeting
* henninge used "Mat" on purpose ... ;)
<mrevell> :) Yes, I do see what henninge says and I agree but I think we should fix it by updating statuses
<mrevell> not by removing the link from the release notes :)
<henninge> that is what I mean!
<henninge> :-)
<Ursinha> :)
<Ursinha> right, so let's all do the effort to close the items out
<Ursinha> right all?
<Ursinha> soyuz already done
<rockstar> Yes, but often, many of us are not awake when they go from committed to released.
<Ursinha> rockstar, I know that
<Ursinha> but they'll be online later, right? :)
<Ursinha> they always come back
<Ursinha> let's try to close it all for the end of Friday
<Ursinha> I think it's a good day
<Ursinha> everyone ok with that?
<Ursinha> hope so
<Ursinha> let's move on
<Ursinha> thanks mrevell 
<Ursinha> and everyone else :)
<Ursinha> [TOPIC] * Operations report (mthaddon/herb/spm)
<MootBot> New Topic:  * Operations report (mthaddon/herb/spm)
<herb> * Yesterday (2008-12-17) - Rolled out r7469 as 2.1.12
<Ursinha> hi herb
<herb> * Bugs #156453 and #118625 continue to be a problem, resulting in restarts of codebrowse multiple times this week.
<herb> * Bug #260171 continues to be a problem as well
<herb> hi
<herb> * Bug #252807 has cropped up a couple of times this week.
<ubottu> Launchpad bug 156453 in loggerhead "production loggerhead branch leaks memory" [Critical,In progress] https://launchpad.net/bugs/156453
<ubottu> Launchpad bug 118625 in launchpad-bazaar "codebrowse sometimes hangs" [High,Triaged] https://launchpad.net/bugs/118625
<herb> * Bugs #49676 & #45419 are becoming more and more important as we spend more and more time dealing with spam on launchpad, a process which is far too manual.
<ubottu> Bug 260171 on http://launchpad.net/bugs/260171 is private
<ubottu> Bug 252807 on http://launchpad.net/bugs/252807 is private
<ubottu> Bug 49676 on http://launchpad.net/bugs/49676 is private
<Ursinha> holy cow
<Ursinha> rockstar, the loggerhead one you can comment, I guess
<Ursinha> also the codebrowse hanging other
<rockstar> I can, but I only saw the cherrypick, don't know the context.  I know we've been trying.
<rockstar> Python sucks.
<Ursinha> don't say that
<rockstar> :)
<Ursinha> :)
<Ursinha> rockstar, what can you do about it?
<Ursinha> talk with beuno?
<sinzui> loggerhead's app and infrastructure sucks
<rockstar> We're working hard to try and get those leaks down, but right now, it's black magic.
<rockstar> sinzui, it's gotten a lot better, but the memory usage hasn't gone down...  :/
<Ursinha> rockstar, well... the same thing as every week... comment on the bug and stuff
<rockstar> I could expand that to "Python's tool support sucks"
<Ursinha> even if the comment is "man, no idea wha't happening"
<al-maisan> this is a really cheerful meeting :)
<al-maisan> all technology sucks BTW :)
<Ursinha> al-maisan, you should come over every weelk :)
<rockstar> Well, I can do that once a week if you like.  I'll probably just use the API and a cron job.
<Ursinha> al-maisan, :)
<al-maisan> sure ;)
<herb> rockstar: I think we can tolerate the memory usage being in the 1.5-2GB range if the app didn't go on walk about from time to time.  1.5-2GB and responding quickly is fine.  1.5-2GB and taking 10+ seconds to respond, no so much.
<rockstar> herb: I'm 95% sure that the two are closely related.
<herb> rockstar: I suspect so.
<herb> rockstar: but I didn't want to focus on the memory issue and lose the performance problem in the process.
<rockstar> Well, I'm pretty free for the next two weeks, so I'll probably check it out at some point.
<Ursinha> rockstar, great
<Ursinha> please
<Ursinha> I pay you a coke on allhands
<rockstar> :)
<Ursinha> :)
<Ursinha> right, the other problems
<Ursinha> bug 260171 is also code
<ubottu> Bug 260171 on http://launchpad.net/bugs/260171 is private
<Ursinha> bug 49676, sinzui, is this registry?
<ubottu> Bug 49676 on http://launchpad.net/bugs/49676 is private
<Ursinha> damn private bugs..
<sinzui> Ursinha: yes
<Ursinha> sinzui, well, is something to be done about that?
<rockstar> I know nothing about 260171 -- I'll have to wait for AsiaPac to wake up.
<Ursinha> rockstar, I see that are other code bugs 
<Ursinha> or you or me can talk to them later
<rockstar> Ursinha, yea, I'll bug 'em.  I need to bug mwh anyway.
<sinzui> i am still planning a follow to my CHR email, the one where I ask how many man hours are we wasting doing manual labour when we could have built tools to do it for us
<rockstar> But we're almost all on leave for the next two weeks.
<sinzui> I don't want to commit to when these items will be fix until I really know their priority.
<Ursinha> [ACTION] Ursinha and rockstar to talk to code people about 260171 and 252807
<MootBot> ACTION received:  Ursinha and rockstar to talk to code people about 260171 and 252807
<Ursinha> sinzui, fair enough.
<Ursinha> [ACTION] sinzui to find out the priority of automatizing manual processes such as bug 49676
<MootBot> ACTION received:  sinzui to find out the priority of automatizing manual processes such as bug 49676
<ubottu> Bug 49676 on http://launchpad.net/bugs/49676 is private
<Ursinha> is that ok?
<ubottu> Bug 49676 on http://launchpad.net/bugs/49676 is private
<rockstar> Ursinha, 252807 is being solved bf abentley's work.  It'll probably be in 2.2.1
<rockstar> s/bf/by
<Ursinha> rockstar, right
<Ursinha> rockstar, can you ask him to do a follow-up in the bug
<Ursinha> please?
<Ursinha> and assign it to 2.2.1 milestone, if appropriated
<rockstar> Ursinha, he's on leave 'til next year.
<Ursinha> rockstar, well, I can do that so
<rockstar> I don't know the details of his work though, so I can't make a solid commitment on when it'll land though.
<Ursinha> [ACTION] talk to abentley about the status of bug 252807
<MootBot> ACTION received:  talk to abentley about the status of bug 252807
<ubottu> Bug 252807 on http://launchpad.net/bugs/252807 is private
<ubottu> Bug 252807 on http://launchpad.net/bugs/252807 is private
<Ursinha> that's okay
<Ursinha> anything else for herb?
<Ursinha> moving on
<Ursinha> [TOPIC] * DBA report (stub)
<Ursinha> as jvt mail said, also flacoste, stub is offline, so isn't here
<Ursinha> everything went fine in the rollout 
<MootBot> New Topic:  * DBA report (stub)
<Ursinha> anything for stub?
<Ursinha> I'll mail him later, if needed
<Ursinha> if not, and everyone's okay with that, and have nothing to say, I'll declare finished our last production meeting of 2008
<flacoste> objectivion!
<flacoste> i have something
<Ursinha> you always do :)
<Ursinha> go ahead
<flacoste> :-)
<flacoste> there has been one r-c branched landed after the roll-out
<flacoste> cprov's branch
<flacoste> is there any other r-c issues today
<flacoste> ?
<Ursinha> flacoste, not that I'm aware of
<flacoste> anything that we need to fix and make as part of a follow-up roll-out?
<rockstar> Not from code
<Ursinha> no weird oopses
<Ursinha> no strange bugs, afai checked
<flacoste> i've seen one, but i'm not sure yet if we should worry about it
* fenris_ (n=fenris@248.97.48.60.wmu01-home.tm.net.my) has joined #launchpad-meeting
<Ursinha> flacoste, oops?
<Ursinha> or bug?
<Ursinha> or what
<flacoste> yeah OOPS-1082A2155
<ubottu> https://devpad.canonical.com/~jamesh/oops.cgi/1082A2155
* e-jat has quit (Read error: 60 (Operation timed out))
<flacoste> 14 of those
<Ursinha> this one I was investigating before the meeting
<Ursinha> but couldn't do it on time
<Ursinha> flacoste, are you doing the same?
<flacoste> Ursinha: yes, i'll have a look at it
<Ursinha> thanks flacoste 
<flacoste> sinzui, cprov, henninge: anything else?
* fenris_ is now known as e-jat
<Ursinha> [ACTION] flacoste to look at OOPS-1082A2155
<ubottu> https://devpad.canonical.com/~jamesh/oops.cgi/1082A2155
<MootBot> ACTION received:  flacoste to look at OOPS-1082A2155
<ubottu> https://devpad.canonical.com/~jamesh/oops.cgi/1082A2155
<henninge> nope
<flacoste> cprov: does you r-c landing warrants a re-roll?
<Ursinha> flacoste, I'll let you know if something weird appears
<al-maisan> cprov i snot here
<al-maisan> is not here
<Ursinha> flacoste, I guess cprov is out
<Ursinha> as al-maisan said :)
<al-maisan> I believe he is collecting his wife from the airport
<sinzui> flacoste: nothing from me
<al-maisan> I don't know of any rc's in Soyuz land
<Ursinha> al-maisan, do you know if he will return?
<al-maisan> Ursinha: he certaily will .. the question is when :)
<Ursinha> lol
<Ursinha> sorry
<al-maisan> *certainly*
<Ursinha> I mean today
<flacoste> the landing was about:
<flacoste> Clearer PPA signing key UID format
<flacoste>         ('Launchpad %(ppa.title)s').
<Ursinha> al-maisan, https://dev.launchpad.net/SoyuzTestPlan/2.1.12
<Ursinha> the items needstesting in there
<Ursinha> I guess
* al-maisan takes a look
<Ursinha> the one flacoste pointed
<Ursinha> exactly :)
<flacoste> Ursinha: ok, so i'll postpone the decision for a re-roll to the investigation of the OOPs and cprov prodiving info on the branch
<Ursinha> flacoste, okay
<al-maisan> re. cprov, he is also not feeling well today .. he might have to go and see a doctor
<Ursinha> worth a quick call to him?
<Ursinha> very quick
<al-maisan> what do you mean?
<Ursinha> or asking kiko maybe
<al-maisan> call him on the phone?
<Ursinha> al-maisan, yes, the old technology
<Ursinha> :)
<al-maisan> kiko is travelling
<Ursinha> so we have no way out
<Ursinha> flacoste, what do you suggest?
<flacoste> Ursinha, al-maisan: i'll call his cell
<Ursinha> flacoste, great, thanks
<Ursinha> anything else?
<al-maisan> why is the call necessary?
<al-maisan> what is the matter of urgency?
<flacoste> al-maisan: to decide if we are doing another roll-out today or not
<Ursinha> to decide about the re-roll
<Ursinha> yes
<flacoste> al-maisan: iow, does this branch needs to be in production
<al-maisan> this one: r7471 [testfix][release-critical] Fixing test failure in the previous revision. ?
<flacoste> al-maisan: the previous one
<Ursinha> al-maisan, no, the previous one
<al-maisan> ah, I see.
<flacoste> well, both of them actually
<flacoste> since they go together :-)
<Ursinha> :)
<al-maisan> proposal: I will check later to see whether cprov is back on-line
<flacoste> al-maisan: cool
<al-maisan> if not, I can give him a call and ask the question
<Ursinha> al-maisan, alright
<Ursinha> thanks 
<Ursinha> well
<Ursinha> anything else?
<Ursinha> soooo
<Ursinha> Thank you all for attending this week's Launchpad Production Meeting, the last one of the year 2008! Happy Holidays everyone, see you all next year! See the channel topic for the location of the logs.
<Ursinha> #endmeeting