[01:10] sinzui: you available to answer a question? [02:25] * wallyworld goes to have lunch with bigjools [03:21] * StevenK stabs mail handling [03:28] StevenK: Oh? [03:30] Two reasons. 1. Why does LP insist on sending me 5 mails about an MP that I just created and approved, and 2. I can't find what sends mail when a bug you created is marked as a dupe [03:31] StevenK: See BugDuplicateChange in bugchange.py [03:32] Oh fuck me, it's an *adapter* [03:32] I've been looking in model code [03:34] Right, this code is utterly disgusting. [03:35] StevenK: 'notification service' [03:36] lifeless: This is the same argument about bug changes. You don't get mailed about changes *you yourself* performed [03:36] StevenK: actually you do [03:36] Unless you are crazy and ask for them to not be sent. [03:36] StevenK: unless you have a) a new account or b) have turned the option off [03:37] Perhaps we want to drop the number from this notification. [03:38] It's difficult. [03:38] "** This bug has been marked a duplicate of private bug %d" [03:38] StevenK: the bug number they cannot see ? [03:38] Because the notifications are global. [03:38] For branch links it was solved by not notifying about private linkages. [03:38] But that can't be done hter.e [03:38] StevenK: so basically, a) apport is broken, and b) until its fixed we're committed to supporting something insane. [03:38] StevenK: there is an agreed upon fix for apport that pitti will, sometime, get to. [03:38] That's what I said on the call this morning :) [03:38] Anda few months ago] [03:39] StevenK: I think tackling this before that fix is just churn, and hard. But we could do the fix ourselves, its retracer side not on-cd-side [03:39] I'd like to fix this "properly" and not give people links in mail that they can't actually follow. [03:41] Impossible. [03:41] Without rewriting the bug notification system. [03:42] wgrant: Then why didn't you say so on the call this morning? :-) [03:42] Huh? [03:42] I said to kick apport. [03:42] Maybe you discussed this during my fglrx crashes. [03:43] I never heard discussion about changing notifications. [03:44] Possibly [03:44] I said that I'd like to do that on the call and Curtis said it sounded great to him. [03:45] But that may have been the cold and flu meds talking. :-) [03:55] * StevenK ponders calling this new service 'audit system service' ... changing that into an acroymn as an exercise for the reader [04:01] sinzui, Can I be allowed here? https://launchpad.net/launchpad/+sharing :) pleease [04:02] No, you can't be. [04:02] Not yet. [04:03] lifeless: O hai. Any thoughts on a witty name for this audit service? :-) [04:04] StevenK: Any progress on the AP garbo job tests? [04:04] wgrant: I'd like some help. You mentioned yesterday it might be transaction boundaries [04:05] Break into it after garbo runs with pdb and see what's in the DB. [04:06] I've done printf debugging pulling things from the store [04:08] StevenK: http://pypi.python.org/pypi/auditor [04:09] Not found [04:09] :-P [04:09] We do like stomping on the global namespace, don't we. [04:09] Haha [04:09] Well, like lifeless said, we would like others to use it [04:10] Sure, but we're not the One True Auditor. [04:10] my-first-auditor [04:12] lp-audit-service? [04:12] It's not LP [04:13] I don't want to proclaim canonical- either [04:13] auditord [04:13] auditd [04:13] also unused there [04:13] First fix Python namespacing, then call it lazr.auditd [04:13] there is an auditd in ubuntu [04:13] wgrant: deprecated [04:14] lifeless: Only because Python namespacing is the most awful thing in the world. [04:14] And it doesn't touch zope [04:14] wgrant: it is, and also it is awful [04:14] mcollective-plugins-centralrpclog might be interesting to look at [04:14] It's the most awful thing in the world, and it's also awful? [04:14] yes [04:15] Good good [04:15] excatly [04:15] you could call it scientologyd [04:15] Right. Flights to Christchurch booked. [04:15] Now lifeless will pay. [04:16] when do you want the spare bed put up ? [04:17] Plan is to kick you in the face for that last comment and then fly home. :-P [04:17] well, it audits [04:17] seriously, auditord IMNSHO is fine [04:17] You said auditor first [04:17] I did [04:17] thats fine too [04:18] but the namespace thing is true [04:18] so auditord for the server, probably auditor-client for the client if you decide it needs one [04:18] (I don't think it does) [04:19] I was going to write a module under lp.services that translates a given object into a string represantation of its EID, but I don't think it needs a client, given we can just scream HTTP at it [04:19] yup yup [04:24] lifeless: Only because Python namespacing is the most awful thing in the world. [04:24] wgrant: have you written anything in common lisp? [04:24] mwhudson: nothing common about it [04:25] Perl namespacing is pretty good [04:25] Python namespacing is fine, but packaging of it is a nightmare. [04:33] ah yes, no arguments there [04:45] To be fair, it also omits one of SystemD's greatest strengths: Roman numeral-compliant project naming. System D is obviously way better than System V. [04:45] -- Steve Langasek [04:45] * StevenK cackles [04:52] StevenK: Distro quotes section of LWN? [04:52] Yup [04:55] wgrant: http://pastebin.ubuntu.com/864582/ [04:58] StevenK: Diff? [04:58] wgrant: http://pastebin.ubuntu.com/864586/ [05:09] wgrant: Confused yet? [05:10] * wgrant tries. [05:11] wgrant: I can push a branch if you wish [05:22] StevenK: Sorry, actally looking now. [05:22] Let's see. [05:24] Hah [05:39] wgrant: Did you get distracted again? [05:44] The tests take about 10 years to run, so yeah. [05:44] Easy to get distracted [05:44] Haha [05:56] Heh === almaisan-away is now known as al-maisan [06:28] StevenK: http://pastebin.ubuntu.com/864662/ [06:32] wgrant: It's just the where clause? [06:33] Hm, it's a different query entirely [06:37] StevenK: And I used itertools.product instead of the nested list comprehension. [06:38] I'm not quite sure why the old one wasn't working, and the debug cycle is too slow, so I just rewrote it from scratch instead. [06:42] Hmm, now I get SilentLaunchpadScriptFailure instead [06:42] I HATE debugging garbo failures [06:47] StevenK: make schema to check the security is right? [06:56] huwshimi, thanks for reviewing the workitems-widget branch! I'll switch so we have whiteboard first and then the work items text area. and I'll have a go at adding a edit mode message to the whiteboard [06:56] mabac: OK great! [06:59] huwshimi, do you (or anyone else :) have an example of something similar in lp? that is a message that looks or behaves like what you're after? [06:59] rats [07:13] wgrant: Interdiff between yours and mine: http://pastebin.ubuntu.com/864684/ [07:13] wgrant: But DistributionAddition gives SilentLaunchpadScriptFailure :-( === wallyworld changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: - | Firefighting: - | Critical bugtasks: 4*10 === al-maisan is now known as almaisan-away [08:56] good morning [09:00] I'm trying to find a way to show a message on blueprints when the whiteboard is being edited. I think I'm on to something using tal:condition in specification-index.pt. Does anyone know how I can detect the state of a TextAreaWidget? [09:03] If there's a standard way to do something like this, I'd be happy to learn about that instead. :) === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === stub1 is now known as stub [10:59] salgado: ping [10:59] hi czajkowski [11:00] salgado: ready for G+ [11:00] czajkowski, yep, will be there in a sec. do you have a URL for the hangout? [11:01] salgado: setting up now [11:02] salgado, quick question for you. :) how would you go about displaying a message when the whiteboard is being edited? it's for alerting the user to not put work items in it. [11:03] salgado, I've run into a dead end with tal conditionals in the template. [11:10] mabac, maybe that text widget thing has a way to specify some help text to be shown below it? [11:10] salgado: nice to meet you [11:10] czajkowski, nice to meet you too, and thanks for the help! :) [11:10] np [11:11] once mrevell has the post done I';ll post it to the loco contacts list, add it to my blog so it ends up on the loco radar and then onto jono [11:11] morning [11:13] salgado, didn't find anything like that. so I'm going for something simple and dynamic. I got a pointer to the js from danilos so I'll try that [11:15] rick_h_: g'day [11:16] mabac, btw, if the JS widget is capable of supporting something, do not hesitate to expose it in the lazrjs.py TextAreaEditorWidget either :) [11:17] danilos, ok let's see what I can find :) [11:28] mabac, ok, good look with that; notice that after you change anything in a .js file you'll need to run 'make jsbuild' to see them on the browser [11:29] salgado, ok thanks. I would have missed that [11:29] that's about everything I know about javascript in LP: cover your eyes, make changes, run 'make jsbuild' and hope it will work [11:30] :) that'll be easier soon [11:31] :) [11:32] I've been hacking on tools for that, but a bit complicated to setup atm [11:37] salgado, I did this but hiding it when the whiteboard is not being edited got tricky: http://dl.dropbox.com/u/400334/whiteboardnotice.png [11:44] mabac, yeah, we'd need to have hooks with the widget to do that, I think. I'm checking the docs of YUI's widget class to see if there's anything there that could be useful [11:48] what widget salgado ? [11:49] rick_h_, the base for InlineEdit: http://yuilibrary.com/yui/docs/widget/ [11:49] ok, so widgets have a ton of events to watch for [11:51] looking you *might* be able to watch for the visibleChange attribute? [11:51] you're looking to fire something when you click edit right? [11:52] rick_h_, yup that'd be good enough [11:53] mabac: I'm just not 100% sure that the visible is following the editor part of the widget or not [11:53] salgado, Is launchpad.dev the only place I can play with the work items box? [11:55] mrevell: yea, it's through testing/pqm, but don't think it's on qastaging yet [11:55] so salgado tests passed and such this morning it looks like [11:55] cheers [12:05] mrevell, rick_h_, yes, only launchpad.dev for now. mabac is trying to add a warning to let people know they should not enter work items on the whiteboard === danilo_ is now known as danilos [12:05] salgado, Is it not behind a feature flag? [12:06] mrevell, nope. do you think it's worth doing that? [12:07] salgado, If it's going to end up on production before it's ready for use, then yes. [12:08] mrevell: sorry, that's my confusion [12:08] I landed a different branch for salgado yesterday [12:08] the work items is still in reivew/changes [12:09] Sorry, I'm confused. So what's landing now? [12:12] mrevell, it will not land before it's ready [12:13] mrevell, the new UI is still under review [12:13] Gret :) [12:13] Can someone who isn't me log into carob and look at the pqm logs to see what the heck the buildbot-poller is doing? [12:13] Or rather, great === almaisan-away is now known as al-maisan [12:16] StevenK: where do I look to see "what the heck the buildbot-poller is doing? [12:16] rick_h_: /srv/pqm-logs or some such, there's a log for it [12:16] You may need to sync logs [12:18] StevenK: how often does it poll? [12:19] StevenK: https://pastebin.canonical.com/61452/ is last bit from the buildbot log [12:20] I was trying to *not* think about how crap buildbot and its poller is at 2320 on a Friday night. :-( [12:21] rick_h_: Sync pqm logs [12:21] sorry, someone an expert on buildbot? /me's never used it before until LP so don't know what I'm looking for [12:21] rick_h_: buildbot and buildbot-poller are distinct systems. [12:21] And buildbot-poller was written by us. === matsubara-afk is now known as matsubara [12:22] so am I looking to sync the buildbot system or a different one? [12:23] StevenK: and am I supposed to be looking at something other than /srv/lp-pqm-logs/pqm_logs/buildout.log then for the poller logs? [12:24] rick_h_: That log you pasted is the right one. [12:24] ok, requested buildbot sync, not seeing anything new yet [12:24] It will use 'write' to tell you when the sync is completed [12:24] IE, you'll notice. [12:24] ah ok [12:29] StevenK, does this have anything to do with the fact that devel has not been merged into stable yet? [12:30] That's one of things the poller does, yes. [12:37] StevenK: so sync completed, nothing new in the log [12:37] StevenK, hmm, my changes were actually committed to ~launchpad-pqm/launchpad/stable before they were blessed by buildbot, it seems. I see them committed ~8h ago [12:37] No, that's because it merged your revision [12:37] oh, that's because we pull? [12:37] I'm not sure what the poller does, but it's magical. [12:37] heh, ok [12:38] It sends a message to PQM, and it does it. [12:39] what's the difference between staging and qastaging? [12:40] staging runs off db-stable, and qastaging runs off stable [12:40] Typical staging is used to test DB changes nowdays [12:40] salgado: production-{devel,stable} from your time are long dead, we deploy to production from stable [12:41] Something seems to have kicked, qa bot updated tag/status for my change now [12:41] but log still seems same [12:41] rick_h_: Can you kick that manager of yours to do his two items of QA? [12:42] StevenK: will do [12:42] StevenK, right, makes sense :) === danhg_ is now known as danhg [14:35] adeuring, abentley, rick_h_ -- hey. firing up hangout. [14:35] ok [14:39] deryck: I don't see you. [14:39] abentley, hey, are you trying? https://plus.google.com/hangouts/extras/talk.google.com/orange-standup [14:44] sinzui: have you been spring cleaning the licience reviews? [14:47] I review the all other/* licenses every Friday. I close projects, give canonical project licenses, send out license renewals [14:48] sinzui: ah ok, as I was waiting on one to change its status and wondered where it had gotten to . [14:48] Today I gave out a license and mark a project approved since it changed their license to gpg affero [14:48] oops [14:48] sorry [14:48] nods that was the one I was wondering about [14:48] as you had a note on the whiteboard [14:49] That note was from 2009 I think [14:49] czajkowski, You reported a bug about the batching for all /projects... [14:49] sinzui: aye as it came via a RT and it does seem rather strange we'd display a negative figure tbh. [14:50] ...only the pathological user with a historical interest will ever use it... [14:50] ok [14:50] eg me because I read the license info of 5,000 projects when we decided all projects had to have a license [14:51] heh ok [15:16] adeuring: chat? [15:24] abentley: sure. mumble? [15:24] adeuring: sure. [15:31] abentley: still there? [15:33] rick_h_, salgado I changed the workitems-widget branch a little so it displays a message when editing the whiteboard. I suspect it might be considered somewhat hackish so if you guys would like to have another look, it'd be great. :) https://code.launchpad.net/~linaro-infrastructure/launchpad/workitems-widget/+merge/94790 === al-maisan is now known as almaisan-away [15:36] mabac, on a call now, will check in a minute [15:37] salgado, thanks. going afk now. might be able to check in again later. maybe ping huw if he comes online to have a look too? [15:37] mabac: peeking [15:38] rick_h_, thanks. if it's to hideous, comment on the mp and I'll deal with it as soon as I can. [15:41] amI online? [15:42] yes [15:42] thanks [15:44] sinzui: No :D [15:46] adeuring: Internet is back. Shall we try again? [15:46] abentley: sure [15:50] nigelb, :) [15:51] :D === matsubara is now known as matsubara-lunch [16:17] rick_h_, salgado just wanted to check back in. is there a verdict? :) [16:18] mabac: not a huge fan of the hook at the moment. I'm going to propose an alternative. I need to get a checkout and play with it a little bit. [16:18] abentley: btw, nice to see ec2 moved [16:18] I was wondering if we should put lp-dev-utils in the launchpad PPA [16:19] mabac, I'll defer to rick_h_ on this one as I know close to nothing about YUI and LP's widgets [16:19] mabac: personally the editor needs to provide an event you can just listen for. It seems it doesn't right now, so I want to add it [16:19] rick_h_, thanks, that'd be great. any help is very welcome on this. [16:20] mabac: thanks for your patience [16:20] salgado, it's obvious from my patch that I have no clue. :) [16:21] rick_h_, no problem. I spent too much time to get that hack working so I'm happy you want to assist me. I'll pop out for the weekend then. [16:21] jelmer: I guess that gives it a better install story, but I think there's a bunch of packaging needed. [16:44] mrevell, you didn't forget that text for the help popup, did you? ;) [16:44] I did not salgado :) [16:44] mrevell, if we could get it by Monday it'd be great; no need to hurry too much [16:44] I started later on it that I'd have liked but it's under way. [16:44] No prob [16:45] mrevell, great, thanks! [17:13] hmm. I've got a job on the garbo hourly script and it doesn't seem to be running enough iterations of it for the whole work to be done [17:13] my job runs for only a couple minutes [17:14] is there a limit on the time or number of iterations that I'm not seeing? [17:18] lifeless, around? [17:32] anybody up for a quick review? https://code.launchpad.net/~salgado/launchpad/workitem-migration-allow-inactive-milestones/+merge/95624 === matsubara-lunch is now known as matsubara [17:56] salgado, what happens the work items when I make their active milestone deactivated (untargetable) [17:57] sinzui, there should be no milestones to which a WI cannot be targeted [17:58] that's what I'm changing, so that they can be targeted to inactive milestones === deryck is now known as deryck[lunch] [17:58] * sinzui looks again [17:58] ah [17:58] sinzui, the UI/DB allows that (I confirmed a few minutes ago); it's just the migrator script that was broken [17:59] Right. Lp UI often does not permit it, but the API will let you do it [18:00] salgado, r=me [18:00] sinzui, also, I'm thinking of moving the migrator script from garbo-hourly to garbo-frequent as it takes a couple minutes on the first 2 or 3 runs and then will run much faster than that. does that sound ok to you? [18:01] yes [18:01] sinzui, do you mind if I sneak that change in this same branch? [18:01] no [18:02] sinzui, great, if you could have another look there ;) [18:03] come on, LP, update my diff [18:04] still looks okay [18:04] I'll just add a comment to the review [18:05] sinzui, great! can you land it for me as well? [18:05] yes [18:05] sinzui, superb, thanks a bunch! === salgado is now known as salgado-lunch [18:17] salgado-lunch: ping when you get back [18:59] salgado-lunch: hi === deryck[lunch] is now known as deryck === salgado-lunch is now known as salgado [19:22] rick_h_, hi [19:22] salgado: howdy, so I replied to mabac's MP [19:22] salgado: I just wanted ot make sure it made sense, and since it seems we're off on TZ, wasn't sure if I should ping/update you on it to help with him [19:26] rick_h_, I agree with you that it's probably better to do it in specification-index.pt instead of trying to generalize it at this point [19:27] salgado: ok cool. Sorry to make trouble/more work [19:27] salgado: totally not against adding a generate notification to the editor, but want ot be more thorough on it as a longer term thing [19:28] rick_h_, I completely understand that :) [19:29] cool, so hopefully that diff helps makes the fix simple, that's working and tested from his branch [19:29] just have to undo the other stuff [19:31] rick_h_, you're giving us code that's simple and documented; it's a huge help! [19:31] I'm sure mabac will be thankful, and so am I :) [19:59] abentley (or anyone): you know that thing where lp-propose stops using the template from lpreview body? how does one go about fixing that? :-P [20:00] jcsackett: first, run "bzr plugins -v" to ensure lpreview body is installed, and running from where you expect. [20:02] abentley: confirmed; it's installed and running from my .bazaar/plugins [20:03] jcsackett: now try running lp-propose and see if the target branch matches "lp:(~launchpad-pqm/)?launchpad(/(db-)?devel)?" [20:04] target is lp:launchpad [20:04] hrm. that's the same branch, but not a mach for that format. [20:05] oh, wait, i may have misread that regex. i think that is a match. [20:06] jcsackett: Hrm. I think the displayed target branch is not what it checks against. [20:08] abentley: ah. [20:10] jcsackett: So the submit branch's public URL should match 'bzr\+ssh://bazaar.launchpad.net/~launchpad-pqm/launchpad/(db-)?devel' [20:10] abentley: ok. [20:10] abentley: as in the setting in locations.conf? [20:11] jcsackett: Yes, though bzr info will tell you what bzr thinks the setting is. [20:14] abentley: ok, the submit branch had gotten borked when i mucked with my locations the other day. stuff works now. [20:14] thanks! [20:14] jcsackett: np [21:18] jcsackett, r=me