[07:44] What's the bestest way of running a single story nowadays? [10:59] Morning, all. === deryck changed the topic of #launchpad-dev to: Launchpad Development Channel | Week 4 of 10.03 | PQM is open | https://dev.launchpad.net/ | Get the code: https://dev.launchpad.net/Getting | On-call review in irc://irc.freenode.net/#launchpad-reviews | Use http://paste.ubuntu.com/ for pastes === wgrant changed the topic of #launchpad-dev to: Launchpad Development Channel | Week 0 of 10.04 | PQM is open | https://dev.launchpad.net/ | Get the code: https://dev.launchpad.net/Getting | On-call review in irc://irc.freenode.net/#launchpad-reviews | Use http://paste.ubuntu.com/ for pastes === salgado_ is now known as salgado [14:33] maxb, around? have you tried running the python2.6 branch of LP recently? [14:45] gmb: ping [14:48] barry, Hi [14:50] gmb: hi. responded to your email. thanks for your help with this! [14:50] barry, No worries. Sorry for letting myself get sidetracked *again* [14:51] barry, FYI, I've converted Mark's export to Launchpad interchange format and I'm going to try doing the import locally to see what happens to the patches. [14:51] awesome, thanks [14:51] I'll reply to the thread with what I find out. Hopefully should have some answers today. [14:52] cool [15:06] barry: got a sec? In my spare time I'm working on bug #231023 [15:06] Bug #231023: on status change, show new status in Subject: [15:07] barry: ... and although I'm adding all sorts of instrumentation to lib/canonical/launchpad/mailnotification.py:BugNotificationBuilder.build [15:07] I can't seem to get any of it to take effect in launchpad.dev. Is that the right place? [15:07] kfogel: sure [15:08] barry: and lib/lp/bugs/doc/bugnotification-email.txt should also pass/fail based on changes I make in that code, right? [15:10] kfogel: that's what i would think. did you put a break point in .build()? [15:11] barry: well, I'm doing this: http://paste.ubuntu.com/409510/ [15:11] barry: IOW, I added an "x" suffix to "Bug" just to make sure things are working, and then log the whole subject to a tmpfile. [15:12] salgado: hey. Not recently, no [15:12] barry: last week, I'd run that code and then go into launchpad.dev and make all sorts of bug changes -- but my tmpfile never showed up. [15:12] barry: trying again now [15:13] kfogel: it's always helpful to stick a pdb.set_trace() in there and see if the code you think is getting hit actually is ;) [15:13] barry: that's a good idea [15:41] maxb, I've asked because I'm trying to resurrect it but am blocked on what seems to be http://reinout.vanrees.org/weblog/2009/11/13/distribute-buildout-recursion-fixed.html (which should be fixed on our version of buildout) [15:41] Ah. For any insane buildout behaviour, I would direct you towards gary :-) [15:43] maxb, if only he were around today... :< [15:43] :( [15:51] barry: even this patch http://paste.ubuntu.com/409529/ is not throwing me into the debugger [15:52] barry: this is when I go to https://bugs.launchpad.dev/firefox/+bug/5 and make various changes (I add a comment, change status, change assignee, etc) [15:52] barry: I'm wondering if there's something I'm supposed to do to get the entire notification system "turned on"? [16:04] mars, hi. Do you have a minute to help me work out something for a Windmill test? [16:04] deryck, yes, in a few minutes [16:05] mars, ok, thanks! Just ping when you have 2-3 minutes. [16:20] deryck: you have backscroll to see my above conversation with barry? If you know why I can't seem to get launchpad.dev's bug notification system operating, pls let me know. [16:21] deryck, online, let me know when you have a moment, and I can help you [16:24] kfogel, so lp's notifications system is really just a set of calls to notify() and then running the notification script. I would guess the script acts based on config settings, but I've not actually run it locally. [16:25] mars, cool. thanks. So I'm working on bug 494257 [16:25] Bug #494257: Users not notified in email when subscribed by someone else

[16:25] deryck, ok [16:26] mars, and the issue there is that the notify(ObjectCreatedEvent()) stuff happens in browser code, not model code. So it's never hit from JS use of API... [16:26] mars, so I want a windmill test to verify this and do TDD on the fix for it. So see: http://bazaar.launchpad.net/~deryck/launchpad/not-notified-someone-else-subscribed-494257/revision/10607 [16:27] mars, the event listener stuff there doesn't seem to work, and I'm wondering if BugsWindmillLayer will support this approach to testing this? [16:29] deryck, the first thing I have to ask about this is: does windmill share process and configuration with the application server? [16:29] I know that we can now use the ObjectFactory with windmill [16:31] but that fact does not imply that the event listener in your windmill test is being registered with the application server process [16:34] deryck: "notify()", huh? Sounds like that's a major entry point that I've... not encountered yet in code, though I've heard it referred to ;-). Where is the "notification script"? Is it ./cronscripts/send-bug-notifications.py ? [16:34] kfogel, yes, that's the script. and look through model/bug.py for notify calls. [16:35] deryck: thx [16:35] np [16:35] rockstar, ping, do you remember who set up the windmill objectfactory integration? [16:35] rockstar, it was done recently IIRC [16:35] mars, I think it was flacoste and BjornT at various times, but neither is available today, I believe [16:36] deryck, yeah, may have been BjornT [16:36] mars, this is actually what I'm asking you, is can this be done? i.e. is there access to the app server in windmill in this way [16:36] deryck, I don't know. [16:37] mars, ok, cool. thanks anyway :-) [16:37] no problem. Hopefully BjornT knows. [16:37] I thought BjornT might be the only one to know. but was casting about for help. :-) [16:39] I think he is the only person who knows the entire system structure. Others know parts of it, and can assemble the whole thing if need be. === salgado is now known as salgado-brb === matsubara is now known as matsubara-lunch [17:54] sinzui, hi [17:54] sinzui, is bug 548578 really ready to qa? I mean, are you able to qa that on staging or edge? [17:54] Bug #548578: scripts/cache-country-mirrors.py is generating files with perms 0600 [17:55] or anywhere else === salgado-brb is now known as salgado [18:02] Ursinha, yes it is ready for QA because it will be test by spm on the machine that is affected [18:02] sinzui, right === beuno is now known as beuno-lunch === matsubara-lunch is now known as matsubara === beuno-lunch is now known as beuno === salgado_ is now known as salgado === matsubara is now known as matsubara-afk === Ursinha_ is now known as Ursinha === jelmer is now known as Guest72846 [20:31] morning [20:31] hi thumper === jelmer_ is now known as jelmer [21:31] Whoa. pqm.launchpad.net says "Now playing... * 1 request(s) for other project(s). [21:31] " [21:31] What does that mean? [21:33] kfogel, it means it thinks the submission's target is not a LP branch [21:34] salgado: ah, okay. Pity it's not more... informative about that. [21:35] yeah, it could do a lot better [21:35] salgado: I guess I'm trying to find out if those messages are about the two branches I just submitted. [21:35] salgado: I should wait for the email? [21:37] kfogel, yeah, you'll get FAILURE emails shortly, but you might re-run the pqm-submit commands with --dry-run to find out what's wrong [21:37] unless you're not landing launchpad branches? [21:37] salgado: my intention was certainly to land launchpad branches. [21:37] salgado: what PQM thinks my intention is, I cannot say. [21:39] kfogel, and to make things worse it won't clearly tell you what went wrong in the FAILURE emails. we can only infer that by looking at what was sent to PQM, [21:45] salgado: Yes. In retrospect, it was probably a mistake to put PQM in charge of all NATO air defense systems. === salgado is now known as salgado-afk === bfiller is now known as bfiller_afk [22:50] Can I set bug 544387 to fix released? [22:50] Bug #544387: date_created for a bug subscription not exported in the API [22:54] bdmurray: Yes.