[15:01] <Ursinha> time for the weekly show
[15:01] <al-maisan> me
[15:01] <Ursinha> #startmeeting
[15:01] <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.
[15:01] <MootBot> Meeting started at 09:01. The chair is Ursinha.
[15:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:01] <Ursinha> weeee I love MootBot
[15:01] <Ursinha> me!
[15:01] <sinzui> me
[15:01] <al-maisan> me
[15:01] <flacoste> me
[15:01] <intellectronica> me
[15:01] <herb> me
[15:01] <Ursinha> rockstar, ping
[15:01] <rockstar> me
[15:01] <Ursinha> henninge is not here
[15:02] <henninge> me
[15:02] <Ursinha> :)
[15:02] <Ursinha> cool, everyone is here
[15:02] <Ursinha> apologies from matsubara and bigjools, both on leave
[15:02] <Ursinha> [TOPIC] Agenda
[15:02] <Ursinha>  * Next meeting
[15:02] <Ursinha>  * Actions from last meeting
[15:02] <Ursinha>  * Oops report & Critical Bugs-
[15:02] <Ursinha>  * Operations report (mthaddon/herb/spm)
[15:02] <MootBot> New Topic:  Agenda
[15:02] <Ursinha>  * DBA report (stub)
[15:02] <Ursinha> right
[15:02] <Ursinha> [TOPIC] * Next meeting
[15:02] <Ursinha> it will be xmas day :) so, no meeting
[15:02] <MootBot> New Topic:  * Next meeting
[15:02] <Ursinha> the thursday after will new year's day, so next meeting will be on Jan 8th, is that okay for you guys?
[15:03] <flacoste> stub is offline doing an internet upgrade
[15:03] <rockstar> That's more than okay with me.
[15:03] <Ursinha> flacoste, I saw jtv's mail, thanks!
[15:03] <Ursinha> awesome
[15:03] <Ursinha> jan 8th will be
[15:03] <henninge> I'll be here ... ;)
[15:03] <Ursinha> [TOPIC] * Actions from last meeting
[15:03] <Ursinha> None!
[15:03] <MootBot> New Topic:  * Actions from last meeting
[15:03] <Ursinha> cool
[15:03] <rockstar> Ursinha, I was just going to ditch the next two meetings.  :)
[15:03] <henninge> Wow!
[15:04] <Ursinha> henninge, what?
[15:04] <Ursinha> today it'll be fast!
[15:04] <Ursinha> [TOPIC] * Oops report & Critical Bugs-
[15:04] <Ursinha> two oopses and two bugs
[15:04] <MootBot> New Topic:  * Oops report & Critical Bugs-
[15:04] <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
[15:05] <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
[15:05] <al-maisan> Ursinha: will do.
[15:05] <Ursinha> and the newaccount one I guess it's registry
[15:05] <Ursinha> al-maisan, thank you!
[15:05] <Ursinha> [ACTION] al-maisan to take a look at OOPS-1083D1281
[15:05] <MootBot> ACTION received:  al-maisan to take a look at OOPS-1083D1281
[15:05] <Ursinha> sinzui, hi
[15:06] <Ursinha> sinzui, can you or someone look at that timeout oops, please?
[15:06] <Ursinha> erm
[15:06] <Ursinha> let's move to the bugs
[15:06] <Ursinha> two bugs for bugs team, api related
[15:06] <Ursinha> bug 308982, bug 296293
[15:07] <Ursinha> intellectronica, hi :)
[15:07] <intellectronica> Ursinha: i'm dealing with both
[15:07] <Ursinha> intellectronica, awesome! can you set the attributes on the second one, please?
[15:07] <Ursinha> I'd love to have that fixed
[15:07] <sinzui> Ursinha: I can, but I think the problems are in the syouz domain
[15:07] <intellectronica> sure, doing that now
[15:08] <Ursinha> sinzui, the +newaccount one?
[15:08]  * Ursinha looks again
[15:08]  * sinzui opened the second oops twice. oops
[15:08] <al-maisan> sinzui: how so?
[15:08] <al-maisan> ah
[15:08] <Ursinha> oh :)
[15:09] <henninge> ee?
[15:09] <rockstar> oi
[15:09] <Ursinha> lol
[15:09] <Ursinha> sinzui, so, what do you think?
[15:09] <sinzui> Ursinha: This may be a duplicate. bac is has a fix for some readonly items in review now
[15:10] <Ursinha> sinzui, right, I'll talk to him about it
[15:10] <Ursinha> didn't have the time to investigate, oops was unavailable
[15:10] <Ursinha> [ACTION] Ursinha to talk to bac about OOPS-1083H1147
[15:10] <MootBot> ACTION received:  Ursinha to talk to bac about OOPS-1083H1147
[15:10] <Ursinha> right
[15:11] <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
[15:11] <sinzui> The specific issue in the oops is that the bugs API is not properly documented
[15:11] <Ursinha> sinzui, oh, you're talking about bugs' bugs
[15:12] <intellectronica> well, it's not really a documentation problem. when the annotations are fixed the documentation should pick it up just fine
[15:12] <sinzui> bug 308982 indicates that the bug API exported some of the attributes as mutable, and they are not
[15:12] <intellectronica> exactly
[15:13] <Ursinha> well, are you going to keep them intellectronica?
[15:13] <intellectronica> keep them exported, but correct the annotation, yes
[15:13]  * sinzui now sees the real oops
[15:13] <Ursinha> okay
[15:14] <Ursinha> can you comment on the bug properly? guess you're already doing that, but anyway :)
[15:14] <Ursinha> intellectronica, ^
[15:14] <intellectronica> doing that
[15:15] <Ursinha> intellectronica, thanks
[15:15] <Ursinha> sinzui, and the oops...
[15:16] <sinzui> Ursinha: I investigated the logintokens this morning. They work (by work, I stole someone's account--they really work)
[15:16] <sinzui> Ursinha: There was definitely something wrong in the DB yesterday that caused this.
[15:16] <sinzui> Ursinha: replication perhaps
[15:17] <Ursinha> sinzui, right. I'll watch it for the next hours/days
[15:17] <Ursinha> will bring the issue to attention if occurs again
[15:17] <Ursinha> [ACTION] Ursinha to watch for new occurrences of OOPS-1083H1147 the next hours/days
[15:17] <MootBot> ACTION received:  Ursinha to watch for new occurrences of OOPS-1083H1147 the next hours/days
[15:17] <Ursinha> thanks sinzui
[15:17] <Ursinha> we have three critical bugs
[15:17] <Ursinha> all fix committed
[15:18] <Ursinha> one is that launchpad-bugzilla one that was always there
[15:18] <Ursinha> one is soyuz and another coswe
[15:18] <Ursinha> argh
[15:18] <Ursinha> *code
[15:18] <al-maisan> aha :)
[15:18] <Ursinha> rockstar, can you set the right status, please please please? :)
[15:18] <Ursinha> rockstar, good morning, btw :P
[15:18] <rockstar> Do we need to close out 2.1.12?
[15:19] <Ursinha> rockstar, we'll need to close it, yeah
[15:19] <rockstar> I think I'll probably just do the two birds/one stone thing then.
[15:19] <Ursinha> two birds? lol
[15:19] <Ursinha> rockstar, thanks :)
[15:20] <henninge> "Close out" is setting all the statusses on bugs and blueprints to Released, right?
[15:20] <Ursinha> rockstar, but setting the status of the critical to fix release is fine for now
[15:20] <Ursinha> henninge, right :)
[15:20] <Ursinha> all of you, please, having pending items to close, let's do it!
[15:20] <henninge> Pleeease do that.
[15:20] <Ursinha> or close or redirect to 2.2.1
[15:20] <Ursinha> henninge, what do you mean?
[15:21] <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.
[15:21] <al-maisan> we did that for the Soyuz 2.1.12 milestone today
[15:21] <al-maisan> i.e. close it out.
[15:21] <Ursinha> al-maisan, great, thanks a lot
[15:21] <Ursinha> henninge, hmm
[15:21] <Ursinha> mrevell, hi :)
[15:22] <mrevell> hey there Ursinha
[15:22] <Ursinha> want to be the special guest ?
[15:22] <Ursinha> :)
[15:22] <Ursinha> see what henninge said above, please
[15:22] <mrevell> Sorry, I haven't been following the meeting, I'm about to go on a call.
[15:22]  * mrevell looks
[15:22] <Ursinha> mrevell, no problem, you don't have to
[15:22] <Ursinha> join the meeting, that is
[15:23]  * henninge used "Mat" on purpose ... ;)
[15:23] <mrevell> :) Yes, I do see what henninge says and I agree but I think we should fix it by updating statuses
[15:23] <mrevell> not by removing the link from the release notes :)
[15:23] <henninge> that is what I mean!
[15:23] <henninge> :-)
[15:23] <Ursinha> :)
[15:23] <Ursinha> right, so let's all do the effort to close the items out
[15:23] <Ursinha> right all?
[15:23] <Ursinha> soyuz already done
[15:24] <rockstar> Yes, but often, many of us are not awake when they go from committed to released.
[15:24] <Ursinha> rockstar, I know that
[15:24] <Ursinha> but they'll be online later, right? :)
[15:24] <Ursinha> they always come back
[15:25] <Ursinha> let's try to close it all for the end of Friday
[15:25] <Ursinha> I think it's a good day
[15:25] <Ursinha> everyone ok with that?
[15:25] <Ursinha> hope so
[15:25] <Ursinha> let's move on
[15:25] <Ursinha> thanks mrevell
[15:26] <Ursinha> and everyone else :)
[15:26] <Ursinha> [TOPIC] * Operations report (mthaddon/herb/spm)
[15:26] <MootBot> New Topic:  * Operations report (mthaddon/herb/spm)
[15:26] <herb> * Yesterday (2008-12-17) - Rolled out r7469 as 2.1.12
[15:26] <herb> * Bugs #156453 and #118625 continue to be a problem, resulting in restarts of codebrowse multiple times this week.
[15:26] <Ursinha> hi herb
[15:26] <herb> * Bug #260171 continues to be a problem as well
[15:26] <herb> hi
[15:26] <herb> * Bug #252807 has cropped up a couple of times this week.
[15:26] <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.
[15:26] <Ursinha> holy cow
[15:26] <Ursinha> rockstar, the loggerhead one you can comment, I guess
[15:27] <Ursinha> also the codebrowse hanging other
[15:27] <rockstar> I can, but I only saw the cherrypick, don't know the context.  I know we've been trying.
[15:27] <rockstar> Python sucks.
[15:27] <rockstar> :)
[15:27] <Ursinha> don't say that
[15:27] <Ursinha> :)
[15:27] <Ursinha> rockstar, what can you do about it?
[15:28] <Ursinha> talk with beuno?
[15:28] <sinzui> loggerhead's app and infrastructure sucks
[15:28] <rockstar> We're working hard to try and get those leaks down, but right now, it's black magic.
[15:28] <rockstar> sinzui, it's gotten a lot better, but the memory usage hasn't gone down...  :/
[15:28] <Ursinha> rockstar, well... the same thing as every week... comment on the bug and stuff
[15:29] <rockstar> I could expand that to "Python's tool support sucks"
[15:29] <Ursinha> even if the comment is "man, no idea wha't happening"
[15:29] <al-maisan> this is a really cheerful meeting :)
[15:29] <al-maisan> all technology sucks BTW :)
[15:29] <Ursinha> al-maisan, you should come over every weelk :)
[15:29] <rockstar> Well, I can do that once a week if you like.  I'll probably just use the API and a cron job.
[15:29] <Ursinha> al-maisan, :)
[15:29] <al-maisan> sure ;)
[15:30] <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.
[15:30] <rockstar> herb: I'm 95% sure that the two are closely related.
[15:30] <herb> rockstar: I suspect so.
[15:31] <herb> rockstar: but I didn't want to focus on the memory issue and lose the performance problem in the process.
[15:31] <rockstar> Well, I'm pretty free for the next two weeks, so I'll probably check it out at some point.
[15:31] <Ursinha> rockstar, great
[15:31] <Ursinha> please
[15:31] <Ursinha> I pay you a coke on allhands
[15:31] <rockstar> :)
[15:32] <Ursinha> :)
[15:32] <Ursinha> right, the other problems
[15:32] <Ursinha> bug 260171 is also code
[15:33] <Ursinha> bug 49676, sinzui, is this registry?
[15:33] <Ursinha> damn private bugs..
[15:33] <sinzui> Ursinha: yes
[15:34] <Ursinha> sinzui, well, is something to be done about that?
[15:34] <rockstar> I know nothing about 260171 -- I'll have to wait for AsiaPac to wake up.
[15:34] <Ursinha> rockstar, I see that are other code bugs
[15:34] <Ursinha> or you or me can talk to them later
[15:35] <rockstar> Ursinha, yea, I'll bug 'em.  I need to bug mwh anyway.
[15:35] <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
[15:35] <rockstar> But we're almost all on leave for the next two weeks.
[15:36] <sinzui> I don't want to commit to when these items will be fix until I really know their priority.
[15:36] <Ursinha> [ACTION] Ursinha and rockstar to talk to code people about 260171 and 252807
[15:36] <MootBot> ACTION received:  Ursinha and rockstar to talk to code people about 260171 and 252807
[15:36] <Ursinha> sinzui, fair enough.
[15:37] <Ursinha> [ACTION] sinzui to find out the priority of automatizing manual processes such as bug 49676
[15:37] <MootBot> ACTION received:  sinzui to find out the priority of automatizing manual processes such as bug 49676
[15:37] <Ursinha> is that ok?
[15:37] <rockstar> Ursinha, 252807 is being solved bf abentley's work.  It'll probably be in 2.2.1
[15:37] <rockstar> s/bf/by
[15:37] <Ursinha> rockstar, right
[15:38] <Ursinha> rockstar, can you ask him to do a follow-up in the bug
[15:38] <Ursinha> please?
[15:38] <Ursinha> and assign it to 2.2.1 milestone, if appropriated
[15:38] <rockstar> Ursinha, he's on leave 'til next year.
[15:39] <Ursinha> rockstar, well, I can do that so
[15:39] <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.
[15:39] <Ursinha> [ACTION] talk to abentley about the status of bug 252807
[15:39] <MootBot> ACTION received:  talk to abentley about the status of bug 252807
[15:39] <Ursinha> that's okay
[15:40] <Ursinha> anything else for herb?
[15:40] <Ursinha> moving on
[15:40] <Ursinha> [TOPIC] * DBA report (stub)
[15:40] <Ursinha> as jvt mail said, also flacoste, stub is offline, so isn't here
[15:40] <Ursinha> everything went fine in the rollout
[15:40] <MootBot> New Topic:  * DBA report (stub)
[15:40] <Ursinha> anything for stub?
[15:40] <Ursinha> I'll mail him later, if needed
[15:41] <Ursinha> if not, and everyone's okay with that, and have nothing to say, I'll declare finished our last production meeting of 2008
[15:41] <flacoste> objectivion!
[15:41] <flacoste> i have something
[15:41] <Ursinha> you always do :)
[15:41] <Ursinha> go ahead
[15:41] <flacoste> :-)
[15:41] <flacoste> there has been one r-c branched landed after the roll-out
[15:41] <flacoste> cprov's branch
[15:41] <flacoste> is there any other r-c issues today
[15:41] <flacoste> ?
[15:42] <Ursinha> flacoste, not that I'm aware of
[15:42] <flacoste> anything that we need to fix and make as part of a follow-up roll-out?
[15:42] <rockstar> Not from code
[15:42] <Ursinha> no weird oopses
[15:42] <Ursinha> no strange bugs, afai checked
[15:42] <flacoste> i've seen one, but i'm not sure yet if we should worry about it
[15:42] <Ursinha> flacoste, oops?
[15:42] <Ursinha> or bug?
[15:43] <Ursinha> or what
[15:43] <flacoste> yeah OOPS-1082A2155
[15:43] <flacoste> 14 of those
[15:43] <Ursinha> this one I was investigating before the meeting
[15:43] <Ursinha> but couldn't do it on time
[15:43] <Ursinha> flacoste, are you doing the same?
[15:44] <flacoste> Ursinha: yes, i'll have a look at it
[15:44] <Ursinha> thanks flacoste
[15:44] <flacoste> sinzui, cprov, henninge: anything else?
[15:44] <Ursinha> [ACTION] flacoste to look at OOPS-1082A2155
[15:44] <MootBot> ACTION received:  flacoste to look at OOPS-1082A2155
[15:44] <henninge> nope
[15:44] <flacoste> cprov: does you r-c landing warrants a re-roll?
[15:44] <Ursinha> flacoste, I'll let you know if something weird appears
[15:44] <al-maisan> cprov i snot here
[15:44] <al-maisan> is not here
[15:44] <Ursinha> flacoste, I guess cprov is out
[15:44] <Ursinha> as al-maisan said :)
[15:45] <al-maisan> I believe he is collecting his wife from the airport
[15:45] <sinzui> flacoste: nothing from me
[15:45] <al-maisan> I don't know of any rc's in Soyuz land
[15:45] <Ursinha> al-maisan, do you know if he will return?
[15:46] <al-maisan> Ursinha: he certaily will .. the question is when :)
[15:46] <Ursinha> lol
[15:46] <Ursinha> sorry
[15:46] <al-maisan> *certainly*
[15:46] <Ursinha> I mean today
[15:46] <flacoste> the landing was about:
[15:46] <flacoste> Clearer PPA signing key UID format
[15:46] <flacoste>         ('Launchpad %(ppa.title)s').
[15:46] <Ursinha> al-maisan, https://dev.launchpad.net/SoyuzTestPlan/2.1.12
[15:46] <Ursinha> the items needstesting in there
[15:46] <Ursinha> I guess
[15:46]  * al-maisan takes a look
[15:47] <Ursinha> the one flacoste pointed
[15:47] <Ursinha> exactly :)
[15:47] <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
[15:47] <Ursinha> flacoste, okay
[15:47] <al-maisan> re. cprov, he is also not feeling well today .. he might have to go and see a doctor
[15:48] <Ursinha> worth a quick call to him?
[15:48] <Ursinha> very quick
[15:48] <al-maisan> what do you mean?
[15:48] <Ursinha> or asking kiko maybe
[15:48] <al-maisan> call him on the phone?
[15:49] <Ursinha> al-maisan, yes, the old technology
[15:49] <Ursinha> :)
[15:49] <al-maisan> kiko is travelling
[15:49] <Ursinha> so we have no way out
[15:49] <Ursinha> flacoste, what do you suggest?
[15:49] <flacoste> Ursinha, al-maisan: i'll call his cell
[15:49] <Ursinha> flacoste, great, thanks
[15:49] <Ursinha> anything else?
[15:49] <al-maisan> why is the call necessary?
[15:49] <al-maisan> what is the matter of urgency?
[15:50] <flacoste> al-maisan: to decide if we are doing another roll-out today or not
[15:50] <Ursinha> to decide about the re-roll
[15:50] <Ursinha> yes
[15:50] <flacoste> al-maisan: iow, does this branch needs to be in production
[15:50] <al-maisan> this one: r7471 [testfix][release-critical] Fixing test failure in the previous revision. ?
[15:50] <flacoste> al-maisan: the previous one
[15:50] <Ursinha> al-maisan, no, the previous one
[15:51] <al-maisan> ah, I see.
[15:51] <flacoste> well, both of them actually
[15:51] <flacoste> since they go together :-)
[15:51] <Ursinha> :)
[15:51] <al-maisan> proposal: I will check later to see whether cprov is back on-line
[15:51] <flacoste> al-maisan: cool
[15:51] <al-maisan> if not, I can give him a call and ask the question
[15:51] <Ursinha> al-maisan, alright
[15:51] <Ursinha> thanks
[15:52] <Ursinha> well
[15:52] <Ursinha> anything else?
[15:53] <Ursinha> soooo
[15:53] <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.
[15:53] <Ursinha> #endmeeting
[15:53] <MootBot> Meeting finished at 09:53.
[15:53] <rockstar> Thanks Ursinha!
[15:53] <Ursinha> yay!
[15:53] <Ursinha> thank you all guys
[15:53] <henninge> Happy holidays to you, too!
[15:53] <Ursinha> henninge, thanks!
[15:54] <al-maisan> Bye!
[15:55] <intellectronica> thanks Ursinha
[20:50] <Rinchen>  /msg ChanServ DROP #launchpad-code c78a48bd:bd76b7dc
[20:50] <mwhudson> Rinchen: hi :)
[20:50] <Rinchen> ah, a space!
[20:50] <Rinchen> thanks
[20:50] <Rinchen> we're moving from launchpad-code on freenode to launchpad-dev
[20:51] <Rinchen> so I dropped the reserved channel
[20:51] <thumper> Rinchen: we are moving now?
[20:51] <Rinchen> no
[20:51] <mwhudson> launchpad-code on irc.internal to launchpad-dev on freenode, you mean?
[20:51] <Rinchen> I'm just doing housekeeping
[20:51] <mwhudson> or??
[20:51] <mwhudson> ah, ok
[20:51] <Rinchen> yes
[20:51] <Rinchen> yes mwhudson
[20:52] <Rinchen> it was going from -code to -code but we decided today to go to launchpad-dev to adhere with freenode conventions
[20:52] <Rinchen> and of course, we already have the channel
[20:52] <Rinchen> it's just locked up tighter than thumper's daughters
[20:52] <thumper> :)


[00:38] <StevenK> wgrant: https://code.launchpad.net/~stevenk/launchpad/format-imports-ad-infinitum/+merge/122981
[00:59] <wallyworld_> wgrant: there's another existing css in choiceedit.js (similar to the one fixed in pickers) which i'll deal with as well
[01:05]  * StevenK stabs Unity
[01:10] <wgrant> StevenK: The diff in lib/lp/codehosting/__init__.py is slightly suspicious, but possibly harmless
[01:11] <StevenK> wgrant: Right, I wasn't really sure about that one. Probably best to revert and land, I guess?
[01:12] <wgrant> You can keep it if you throw it through ec2
[01:36] <wgrant> wallyworld_: Bug #1045135, bug #1044546, bug #1044370 are all fixed now, right?
[01:36] <_mup_> Bug #1045135: Changing a sharing policy can leave unused access policies lying around <disclosure> <easy> <qa-ok> <sharing> <Launchpad itself:In Progress by wallyworld> < https://launchpad.net/bugs/1045135 >
[01:36] <_mup_> Bug #1044546: +sharing shows '{policy_name}' for information types granted but not permitted by current combination of branch and bug sharing policies <qa-ok> <sharing> <ui> <Launchpad itself:In Progress by wallyworld> < https://launchpad.net/bugs/1044546 >
[01:36] <_mup_> Bug #1044370: update sharing policies via ajax needs to refresh +sharing details <disclosure> <sharing> <Launchpad itself:In Progress by wallyworld> < https://launchpad.net/bugs/1044370 >
[01:37] <wallyworld_> wgrant: yes
[01:37] <wgrant> Also bug #1008538
[01:37] <_mup_> Bug #1008538: Bug Supervisors are not notified when the project is not shared <bugs> <disclosure> <sharing> <Launchpad itself:In Progress by wallyworld> < https://launchpad.net/bugs/1008538 >
[01:38] <wallyworld_> yes, that's the one just applied via the sql
[01:38] <wgrant> Right, just wanted to check. All closed now
[01:48] <wallyworld_> wgrant: https://code.launchpad.net/~wallyworld/launchpad/css-fix-empty-sharing-table/+merge/122983
[01:48]  * StevenK tries to work out the cause of bug 1036775
[01:48] <_mup_> Bug #1036775: Launchpad shows bugs in projects that do not use Launchpad bugs <bug-columns> <bugs> <lp-bugs> <regression> <Launchpad itself:Triaged by stevenk> < https://launchpad.net/bugs/1036775 >
[01:50] <wgrant> wallyworld_: I wonder if it would be cleaner to create a
Pillar Name's private information blah blah
 in one Y.Node.create, then set tr/td/span's text
[01:54] <wallyworld_> wgrant: i tend to find that Y.Node.create doesn't like everything in one statement, nt sure why
[01:54] <wallyworld_> i can try it again, but every other time it returns something not quite right
[01:55] <wgrant> wallyworld_: Hm, it should work, and it tends to be a bit cleaner I find
[01:55] <wgrant> This particular case isn't that bad, but once you get another layer of nesting it ends up hideous
[01:59] <wallyworld_> wgrant: it worked for this case. in the past, it has not gone well if i then try and set text on the node later, when it is created with nested elements in the string
[01:59] <wallyworld_> i've pushed the changes
[02:00] <wgrant> Thanks
[02:03] <wgrant> wallyworld_: Hm, didn't you just revert that basically?
[02:03] <wgrant> Now the only diff from devel is moving the Y.Node.create into the function
[02:04] <wallyworld_> ffs, yes
[02:07] <wallyworld_> wgrant: so here's the problem - Y.Node.create('

') doesn't work, so that's why i did it as a create of the tr node, then an append child for the td
[02:08] <StevenK> Ah ha, I think I get it
[02:08] <wallyworld_> i guess i need to do a .one(td) to set the text
[02:08] <wgrant> Huh, that's really strange
[02:09] <wgrant> I wonder if it's something about
s not wanting to exist without a surround

[02:12] <wallyworld_> wgrant: the set text kills any nested nodes, so i needed to do a .one() to get the innermost node. that worked. changes on their way up
[02:13] <wgrant> wallyworld_: I was thinking a .one('tr td span').set('text', pillar_name) would work
[02:13] <wallyworld_> i don't need the span
[02:13] <wallyworld_> and if i doa .one(td) on the row node, that works
[02:13] <wgrant> Well, if you don't use the span then you need to also set the rest of the text
[02:14] <wgrant> Which is really part of the template
[02:14] <wgrant> But it doesn't really matter
[02:14] <wallyworld_> i can just set the text of the table cell can't i
[02:15] <wgrant> Right, but then you have to include the "'s private information blah blah blah blah" in the set() call
[02:15] <wgrant> Rather than just the pillar_name
[02:17] <wallyworld_> oh, i see what you are saying. but it works as is
[02:19] <wgrant> wallyworld_: Are your latest changes pushed?
[02:19] <wgrant> 'cause they're still bad
[02:19] <wgrant> Oh, no they're not
[02:19] <wgrant> Your order is just slightly confusing :)
[02:27] <wallyworld_> wgrant: ok, i used a span, looks better i think
[02:34] <wgrant> wallyworld_: Indeed, thanks
[02:34] <wgrant> r=me
[02:35] <wallyworld_> thanks
[02:58] <StevenK> wgrant, wallyworld_: https://code.launchpad.net/~stevenk/launchpad/hide-search-for-unofficial/+merge/122993
[02:58] <StevenK> Somewhat misnamed, but oh well
[03:44] <StevenK> wallyworld_, wgrant: No review for me? :-(
[04:02] <StevenK> Clearly not.
[04:27] <wallyworld_> StevenK: sorry, was at lunch with bigjools
[04:28] <wallyworld_> looking now
[04:31] <StevenK> wallyworld_: Ah, then maybe you can help me with bug 984871, which has JS written all over it.
[04:31] <wallyworld_> ok
[04:32] <StevenK> wallyworld_: In Chromium, you load the page and you see the number of results, and then some AJAX events happen and it disappears.
[04:33] <wallyworld_> but it works in ff
[04:33] <StevenK> Yes, but we have to support both.
[04:33] <StevenK> Unless they do stupid things like encode ~'s
[04:34] <wallyworld_> sure, just remarking
[04:34] <wallyworld_> i'll have a look at the js
[04:37] <wallyworld_> StevenK: in your mp, i can't see where in the diff the !ServiceUsage.UNKNOWN block mentioned in the covering letter used to be
[04:38] <StevenK> wallyworld_: It's not in the diff.
[04:39] <StevenK> Line 74 of buglisting-default.pt
[04:39] <wallyworld_> the covering letter implies it was changed
[04:41] <wallyworld_> oh i see
[04:41] <wallyworld_> the outer conditional stays but we are adding a new conditional deeper inside
[04:41] <StevenK> Right, exactly.
[04:42] <StevenK> wallyworld_: There is other stuff handled in the block that I've left alone.
[04:42] <wallyworld_> StevenK: why not use should_show_bug_information as on line 89?
[04:43] <wallyworld_> that seems to fit with using an external tracker or not
[04:43] <wallyworld_> especially the explanatory text
[04:44] <StevenK> wallyworld_: Mainly because that TAL is a mess.
[04:45] <wallyworld_> one issue for me is that we would be using two different ways of determining the use of an external tracker - view/should_show_bug_information and the enum check
[04:46] <wallyworld_> can't the form stuff just be added to hat same construct?
[04:46] <wallyworld_> with the not: removed?
[04:46] <StevenK> Ah, I see.
[04:48] <StevenK> wallyworld_: The construct further down is for portlets
[04:51] <wallyworld_> StevenK: you mean because class="top-portlet" ?
[04:51] <wallyworld_> the search form is inside this block
[04:52] <wallyworld_> so i think the correct thing to do is use view/should_show_bug_information
[04:52] <wallyworld_> just like the block above
[04:54] <StevenK> wallyworld_: http://pastebin.ubuntu.com/1188320/
[04:54] <wallyworld_> i don't quite fully understand line 55 of the diff - "action search_url|string:" is ultimately replaced with just search_url without the "|string:". I guess this is a consequence of removing the f-flag and stopping the use of tal attributes?
[04:55] <wallyworld_> StevenK: yes, i think that new diff makes sense to my untrained eye.
[05:02] <StevenK> wallyworld_: I have no idea about that bit -- I'm just trying to rip out the class python: bit
[05:05] <wallyworld_> StevenK: i think you need action search_url|string: since it will handle an empty search_url
[05:05] <wallyworld_> and just render action="" instead maybe of action=None or something like that
[05:10] <StevenK> steven@undermined:~/launchpad/lp-branches/hide-search-for-unofficial% bzr grep 'search_url\|string:'
[05:10] <StevenK> lib/lp/bugs/templates/bugtarget-macros-search.pt:    <a tal:attributes="href advanced_search_url|string:?advanced=1"
[05:12] <wallyworld_> the |string bit will only be in the tal. the search_url will be set elsewhere
[05:15] <wallyworld_> so given that attribute is not part of the feature flag removal, why not just leave it there as it was?
[05:18] <StevenK> wallyworld_: http://pastebin.ubuntu.com/1188340/
[05:19] <wallyworld_> StevenK: it needs to be a tal attribute
[05:19] <wallyworld_> for the expression to be evaluated i think
[05:26] <StevenK> wallyworld_: Ah, http://pastebin.ubuntu.com/1188345/
[05:28] <wallyworld_> StevenK: yes, that looks right i think
[05:29] <wallyworld_> tests will test us for sure :-)
[05:29] <StevenK> Yeah, indeed
[05:29] <StevenK> Let me commit and push
[05:29] <wallyworld_> ok, i'll wait for the final diff to update
[05:38] <wallyworld_> StevenK: r=me. that chrome issue doesn't happen for me locally sadly, just with lp.net
[05:40] <StevenK> wallyworld_: Do you have buglisting turned on?
[05:40] <StevenK> There's a feature flag involved.
[05:40] <wallyworld_> ah, maybe not. i always forget that. i wish it had been added to sample data
[05:42] <wallyworld_> right, fails now. good.
[05:54] <wallyworld_> StevenK: it's a hack that was added in for an issue with Chromium's history handling
[05:55] <wallyworld_> i don't understand what the issue was or what the fix does, but removing the hack stops the failure
[05:55] <wallyworld_> because it no longer updates history with an 'incorrect' copy of the model missing 'total'
[05:55] <wallyworld_> but i don't know what else will break removing this
[06:07] <StevenK> Strange
[06:07] <StevenK> wallyworld_: Where's the hack?
[06:08] <wallyworld_> StevenK: listing_navigator.js, around line 166
[06:09] <StevenK> So I wonder if we could fix it by injecting total into e.prevVal
[06:10] <StevenK> But no idea how to do that
[06:11] <wallyworld_> i'd like to fully understand it all before we make changes
[06:11] <wallyworld_> why was the change made, what was the issue etc
[07:34] <adeuring> good morning
[07:34] <mgz> good morning adeuring
[08:22] <jml> lifeless: hi
[08:22] <jml> lifeless: re the LP SOA docs
[08:23] <jml> lifeless: where should test implementations of services live?
[08:24] <lifeless> for use when testing things that act as clients?
[08:24] <lifeless> They should be provided by the concrete service, or at least interface tested by it to prevent skew,
[08:24] <lifeless> .
[08:25] <jml> lifeless: yeah, for that use
[08:25] <jml> lifeless: so clients will probably have testing dependencies on the server code tree?
[08:26] <lifeless> or a pypi package or deb package
[08:26] <jml> right
[08:27] <lifeless> they shouldn't need to import it however. better if they can't in general - use processes to use it
[08:27] <jml> hmm
[08:28] <jml> lifeless: you have told me before but I can't recall (sorry). Why is it better if they can't?
[08:31] <lifeless> it makes it harder to tightly couple these loosely coupled things
[08:32] <lifeless> e.g. language neutrality - if you want to redo a client into go, you don't need to touch the server.
[08:32] <lifeless> test or otherwise
[08:33] <lifeless> you can argue that this is silly, you can always do that work later... and if it was the only advantage, I'd say sure
[08:34] <lifeless> but you also get enforced layer safety; you don't need to worry about conflicting library versions and so forth.
[08:37] <jml> right. discipline in that regard rarely works
[08:37] <jml> at least, not for me :)
[08:38] <lifeless> indeed, you can't be a little bit (binary state)
[08:38] <jml> probably not today or tomorrow, but maybe next week, I'd like to set this up for libdep-service.
[08:39] <lifeless> can I do anything to help ?
[08:40] <jml> hmm.
[08:41] <jml> You mean, other than you already have?
[08:41] <lifeless> :)
[08:41] <lifeless> boom-tish
[08:41] <jml> Answering questions is the only thing I can think of.
[08:41] <lifeless> ok, well I stand ready.
[08:41] <lifeless> is libdep-service django ?
[10:37] <stub> wgrant: http://paste.ubuntu.com/1188697/ has some changes to dbpolicy.py and test_error.py. Had some fallout, and think I've ended up tracking a problem that was bugging gary and benji for ages
[10:38] <stub> still haven't done a full test run though
[10:38] <wgrant> stub: What'd you have to change?
[10:38] <wgrant> And what sort of fallout? It looked relatively sensible.
[10:39] <stub> getUtility(IZStorm).get('foo') could emit an OperationalError rather than a DisconnectionError if the db was down and the Store needed to be constructed
[10:39] <stub> Opened a bug on that one
[10:39] <wgrant> Huh
[10:39] <wgrant> That's surprising.
[10:40] <stub> Also, the test_error was triggering our 'store left in a disconnected state' checks.
[10:40] <wgrant> They are the stuff of nightmares
[10:40] <stub> Yeah, and I think I've fixed it now
[10:41] <stub> The stores look like they were being created in that state, and I'm now ensuring they always get registered with the transaction manager so transaction abort puts them into a state we expect them to be in.
[12:16] <bac> mgz: hi, were you going to review that MP i posted yesterday?  if not, i'll get someone else.
[12:21] <adeuring> jelmer: could you please have a look at this mp: https://code.launchpad.net/~adeuring/launchpad/specification-grants/+merge/123062 ?
[12:21] <jelmer> adeuring: looking
[12:21] <adeuring> jelmer: thanks!
[12:48] <mgz> bac: I shall post something to it, did look over the code
[12:49] <bac> mgz, thanks.  gary is also doing it but i'd like your comments since you've already looked
[14:05] <bac> mgz: gary has posted his comments on my MP.  i'd like to land this shortly so if you have helpful comments could you add them soonish?  thanks.
[14:14] <mgz> bac: posted a few comments
[14:14] <bac> thanks mgz!
[14:17] <mgz> I see gary asked about the participants thing as well.
[14:17] <mgz> so it's not just me not knowing launchpad :)
[14:38] <bac> mgz: yep.  well commented now.
[14:44] <adeuring> jcsackett: thanks for your review!
[14:50] <jcsackett> adeuring: you're welcome!
[15:36] <rick_h_> deryck: ping, got a sec?
[15:36] <deryck> rick_h_, on call with abentley right now
[15:36] <rick_h_> deryck: rgr
[15:45] <deryck> rick_h_, free now.  What's up?
[15:46] <rick_h_> deryck: looking at the sql count test failure stuff and I think part of it is the storm clearing or something. http://paste.mitechie.com/show/774/ is the test failure, which shows the product insert, but the test as a "Store.of(product).invalidate()" which I would expect to reset the queries?
[15:46]  * deryck looks....
[15:47] <abentley> deryck: Should we be posting design decisions like "blueprints support only PUBLIC and the proprietary types" somewhere?
[15:47] <deryck> abentley, hmmm, good question.
[15:47] <deryck> abentley, yeah, let's follow up to the dev list with that.
[15:48] <deryck> abentley, actually, wait, no I don't think we need to for that.
[15:48] <deryck> abentley, we're really just matching what we had before, plus privacy, or what people think of when they say privacy.
[15:49] <deryck> rick_h_, so the selects are the new queries?  And you think these are left over from a different test?
[15:50] <rick_h_> deryck: so I'm investigating part of it. I think it might be my code's fault and I'm investigating, but the INSERT being listed made me wonder if the invalidate() wasn't working/what I was thinking
[15:51] <deryck> rick_h_, invalidate just tells storm to through away its own cache of the objects, to force it to get new objects.
[15:52] <rick_h_> deryck: ok, so this is in fact saying the insert/update are part of the recorded queries then
[15:56] <deryck> rick_h_, right.  I'd run this in devel and see what you get and compare the two.
[15:56] <rick_h_> deryck: ok, digging. Thanks for the quick sanity check.
[15:56] <deryck> np
[17:04] <abentley> deryck[lunch]: I noticed that the set of allowed information_types for blueprints will exactly match that for projects.
[17:08] <deryck> abentley, nice
[18:10] <rick_h_> deryck: ping again, halp!
[18:10] <deryck> rick_h_, give me just a few minutes and I can help.
[18:10] <rick_h_> deryck: ok thanks
[18:10] <deryck> np
[18:22] <deryck> rick_h_, ok, what's up?
[18:26] <rick_h_> deryck: hangout?
[18:27] <deryck> rick_h_, sure.
[18:51] <rick_h_> sinzui: halp please! have a few min for a hangout?
[18:51] <sinzui> I do
[18:51] <rick_h_> sinzui: invite coming
[18:52] <deryck> sinzui, and if you can spare 5 minutes after rick_h_, I'd like a quick chat about something, too.
[19:14] <abentley> jcsackett: could you please review https://code.launchpad.net/~abentley/launchpad/limit-blueprint-info-types/+merge/123150 ?
[19:15] <jcsackett> abentley: certainly.
[19:17] <jcsackett> abentley: r=me.
[19:17] <abentley> jcsackett: thanks.
[20:09] <deryck> sinzui, are you still chatting with rick_h_?
[20:09] <sinzui> no
[20:09] <sinzui> did rick_h_fall off the face of the earth?
[20:10] <rick_h_> he wants you sinzui, not me.
[20:10]  * rick_h_ runs away NOT IT!
[20:10] <deryck> I'm losing cable modem now anyway.  ignore me.
[20:10] <deryck> cable guy is wiring up voip phone and needs to disable lines to test.
[20:10] <rick_h_> deryck: yea, you've been very jittery today
[20:11] <deryck> I'll return when he's done. :)
[20:17] <deryck> sinzui, let's try to chat, he has cut me yet.  should be brief.
[20:17] <deryck> hasn't cut me
[20:17] <sinzui> okay
[20:23]  * sinzui thinks he is talking to himself
[20:24] <sinzui> rick_h_I am here?
[20:24] <sinzui> Am I alive?
[20:24] <rick_h_> sinzui: yes
[20:24] <sinzui> thank you for the validation of my existence
[20:24] <sinzui> next up, find a purpose
[20:25] <rick_h_> sinzui: I find it best to tie them together. I exist to serve a purpose, my purpose is to exist. Next question.
[21:51] <lifeless> hmmm
[21:51] <lifeless> new oauthkeys now notify with a from of<EMAIL_ADDRESS>[21:51] <lifeless> :/
[22:52] <sinzui> wallyworld_, https://bugs.launchpad.net/launchpad/+bugs?field.tag=escalated
[22:55] <lifeless> jcsackett: btw, you didn't land https://code.launchpad.net/~coreygoldberg/lp-dev-utils/ppr-access-parser/+merge/119409 for some reason ?
[22:57] <jcsackett> lifeless: Looks like I just forgot. If you can land, feel free--storm just took out Internet, and cell phone can't land. :-)
[22:58] <lifeless> jcsackett: cool, I will do so
[22:59] <jcsackett> lifeless: Cool, thanks, and sorry for the forgetfulness.
[22:59] <lifeless> no matter
[23:00] <jcsackett> sinzui: A storm has taken out Internet, and it appears my phone can't handle mumble on 3G alone.
[23:00] <sinzui> okay


[19:53] <djsiegel1> vish: hey
[19:53] <djsiegel1> vish: why did you mark that gwibber bug fix committed?
[19:53] <vish> djsiegel1: o/
[19:54] <djsiegel1> I don't think it was committed....
[19:54] <vish> djsiegel1: you added the branch and it had a merge proposal
[19:54] <djsiegel1> yeah but it wasn't merged or even reviewed yet
[19:54] <djsiegel1> that's like marking a bug fixed just because it has a patch
[19:54] <djsiegel1> it isn't fixed
[19:55] <vish> djsiegel1: iirc , the status for bugs if they are present in a branch is fix committed... let me check
[19:55] <djsiegel1> nope
[19:57] <vish> djsiegel1:  ah.. oops ,
[19:57]  * vish  fixin it
[20:04] <djsiegel1> thanks :)


[16:12] <yano> lol, http://www.cleveland.com/brooklyn/index.ssf/2015/01/post_66.html
[16:12] <jenni> [ Two men caught trying to shoplift meat in their pants: Brooklyn Police Blotter | 						cleveland.com ] - https://j.mp/1wPKODA


[03:19] <MrJaguar> hi
[03:21] <MrJaguar> i am new in ubuntu-gnome and a i have a doubt
[03:24] <MrJaguar> i was searching about the extensions and the videos i watch they said that the deafault extensions that are installed don't receive the updates in the same time of the extensions in the page and they recomendo to uninstall the default and install the extensions of the page
[03:25] <MrJaguar> is that necessary?
[15:29] <ricotz> jbicha, hi, is gnome-maps completely relying on libchamplain if so falling back on a working way by patching that could be enough
[15:30] <jbicha> ricotz: patching it to do what?
[15:32] <ricotz> to a working mapsource
[15:32] <jbicha> I think the problem is finding a map server that's willing to take all our traffic without payment
[15:32] <ricotz> https://bugzilla.gnome.org/show_bug.cgi?id=768392


[00:00] <penguin42> so, this is xmas
[00:00] <daftykins> less and less each year i find!
[00:19] <zxmpi> you need to stuff a selection box into a crimbo stocking along with a bunch of cheap junk to feel it
[00:22] <zxmpi> if you're not wondering if the curlywurlys are getting smaller every year, is it even crimbo?
[00:24] <daftykins> very true
[00:24] <daftykins> although toblerone is of #1 importance
[00:24] <daftykins> just imagine of jaffa cakes suddenly shrank in diameter though :(
[00:25] <daftykins> *if
[00:25] <zxmpi> i can imagine the riots alright :-P
[00:26] <zxmpi> the best chance to get larry the cat running the country
[00:28] <zxmpi> of course you can be a real rebel :-) https://www.tastemade.co.uk/videos/giant-jaffa-cake/
[00:32] <davef> Last chance, boarding in 1hr
[00:32] <davef> zxmpi: Curley werleys are getting smaller.
[00:34]  * zxmpi emails scotland yard that the jaffa cake bandit is landing soon
[00:37] <daftykins> :O that big jaffa
[00:40] <penguin42> hang on while they update the facial rec systems to detect people eating jaffa cakes
[00:42] <zxmpi> you can tell your doc that you  bring 1 jaffa cake for lunch and be honest :)
[00:43] <zxmpi> suprised no manufacturer sells them tbh. even one 4-6" would sell well i'd say
[00:46] <penguin42> yeh I've seen individual ~2x size bourbon creams and jammy dodgers for sale in coffee shops etc
[00:47] <daftykins> ooh
[00:47] <zxmpi> giant sausage rolls are sold everywhere
[01:33] <zxmpi> "your computer is so old, it doesn't have a UART, it has a THOUART" -seen on mastodon
[01:40] <daftykins> xD
[03:24] <zxmpi> tomorrow all the unsold selection boxes will be on sale so i shall get my curlywurly :-P
[03:25] <daftykins> ooh my
[03:25] <daftykins> supermarkets won't even be open here i reckon
[03:40] <zxmpi> half the places will be open for a few hours on st. stephens day. in my first job i had to work 3 hours on crimbo day in a corner shop.
[03:40] <daftykins> D:
[03:40] <zxmpi> we sold a lot of ciggies, matches, bread, milk, eggs and batteries. all the batteries. every battery in the shop
[03:44] <daftykins> figures :) lack o' planning
[03:47] <zxmpi> no one thinks to get batteries
[03:49] <daftykins> these days you have to fire up the gadgets, charge and download updates
[03:50] <zxmpi> don't worry sony and ms will both crash update servers for all the shiny new consoles
[03:50] <daftykins> :D
[03:51] <zxmpi> in my day it was finding a plug i could steal and put on my speccy :-)
[04:05] <daftykins> best hit the hay, got lunch to attend tomorrow at the olds
[04:05] <daftykins> g'night for now!
[04:06] <zxmpi> o/
[14:44] <lunazest> do all britts watch Muppets at xmas?
[15:26] <zxmpi> how many people named britt are in the sample?  :-D
[22:54] <zxmpi> who ddiscovered america? the vikings! it's right but not the answer they're looking for
[22:55] <daftykins> genius!