[00:02] <MTecknology> jml: at least it seems like it's on the decline some
[00:03] <MTecknology> jml: some really bored people that have probably never been laid and never will be....
[00:08] <jml> what's the test plan home page?
[00:10] <jml> never mind
[00:10] <jml> (I'd like to know what it is, but at least now I've done my QA item)
[00:14] <jml> I'm really looking forward to landing my 'hot bugs' patch
[00:15] <spm> jml: you should perhaps wear your hot pants when you do so? get in the groove of the moment.
[00:16] <jml> spm, good call.
[00:17] <jml> spm, I'll take photos for you.
[00:17] <spm> jml: on this one, I'm prepared to believe *without* photos. a rare exception.
[00:17] <jml> spm, heh.
[00:24] <jml> I often want to file multiple bugs on a project at once
[00:24] <jml> I wish Launchpad made that easier.
[00:30] <poolie> mm
[00:37] <jml> I'm filing stacks of usability bugs on 'gtg'
[00:37] <jml> which means filing a bug, hitting "End", looking for the "Report another bug" thing and then clicking it.
[00:37] <jml> I filed a bug about this years ago, of course.
[00:37] <jml> since my previous bug tracker was trac, which makes this quite easy.
[00:38]  * mwhudson noms
[00:42] <MTecknology> I hate trac...
[00:42] <MTecknology> jml: just do Back; change details if you know it wasn't reported...
[00:45] <jml> MTecknology, I hate trac too, but it still does some stuff better than Launchpad.
[00:47] <MTecknology> jml: You ever try Mantis?
[00:47] <jml> MTecknology, maybe once, but never for long and not enough to remember it.
[01:08] <jml> thumper, hey, I thought code review comments would get permalinks for free
[01:11]  * jml lunching
[01:33] <poolie> jml: what's gtg?
[01:34] <poolie> btw unless it's just me (which it may be) https://bugs.edge.launchpad.net/malone/+bug/471328 seems pretty critical
[01:34] <mup> Bug #471328: Also affects search error - too many matches <bug-page> <ui> <Launchpad Bugs:Triaged> <https://launchpad.net/bugs/471328>
[01:34] <jml> poolie, "Getting Things GNOME"
[01:34] <poolie> you can't choose bzr or bzr-svn from a project picker
[01:34] <jml> poolie, it's a todo thing that has potential, a fairly active community and not the greatest code.
[01:35] <jml> poolie, I'm living in constant tension between writing my own and helping them with theirs.
[01:35] <poolie> "price: Free" :-)
[01:35] <poolie> thanks ubuntu :)
[01:37] <jml> poolie, I'm not sure how that could be a new bug
[01:37] <jml> poolie, well, at least new to this cycle
[01:38]  * poolie plays on staging
[01:38] <poolie> well
[01:38] <poolie> i didn't see it before
[01:38] <poolie> i would have noticed because i do reassign from bzr to plugins pretty often
[01:38] <poolie> maybe it's transient xmlrpc failure?
[01:39] <jml> poolie, it was filed in early november, so it'd have to affect production.
[01:39]  * poolie tests
[01:39] <jml> poolie, anyway, it does seem pretty serious. Given that all of the bugs guys are afk atm, I'm not sure of the best way to escalate it.
[01:40] <poolie> let me try to reproduce it again
[01:40] <jml> I mean, other than me actually fixing the bug.
[01:40] <poolie> :)
[01:41] <poolie> hm on https://bugs.staging.launchpad.net/bzr/+bug/385879 i don't get that problem but just a stuck spinner
[01:41] <mup> Bug #385879: EOL filter only applied to files when first checked out <content-filtering> <Bazaar:Fix Released by mbp> <Bazaar 2.0:Fix Released by ian-clatworthy> <https://launchpad.net/bugs/385879>
[01:41] <poolie> oh when i tried a second time i did get "undefined"
[01:41] <poolie> so it may be intermittent?
[01:42] <jml> sounds plausible
[03:23] <jml> mwhudson, hi
[03:23] <mwhudson> jml: hi
[03:24] <jml> mwhudson, I was wondering, now that we almost have a fully working bazaar.edge and we have a bzr buildbot...
[03:24] <jml> mwhudson, how much of a pain would it be to automatically land working bzr updates?
[03:24] <jml> mwhudson, and do you think that would be a good idea.
[03:25] <jml> mwhudson, feel free to tell me to go away -- I'm only asking out of curiosity.
[03:25] <mwhudson> jml: i guess it wouldn't make sense to go on getting bzr from an egg in this case
[03:25] <jml> mwhudson, but eggs are teh future.
[03:26] <mwhudson> jml: in fact it flies rather thoroughly in the face of the "use releases" direction buildout consciously pushes us in
[03:26] <mwhudson> jml: that doesn't mean it's a bad thing though
[03:26] <mwhudson> necessarily
[03:27] <mwhudson> jml: having an autoupdated thingy for bazaar.edge but keeping prod using releases would be nice
[03:27] <mwhudson> a bit harder to arrange though i guess
[03:27] <jml> mwhudson, I was typing the same thing, more or less :)
[03:28] <mwhudson> i guess there might be issues with new formats
[03:28] <mwhudson> you could push a new format to baz.edge but the scanner wouldn't be able to read it
[03:28] <mwhudson> well, i guess tests fail when a new format is added
[03:28] <jml> mwhudson, don't we already have that problem?
[03:28] <mwhudson> jml: yes
[03:28] <mwhudson> well, modulo what i just said
[03:29] <jml> mwhudson, yeah, but even without edge, people can still push up formats that we don't support.
[03:29] <mwhudson> jml: true i guess
[03:29] <mwhudson> maybe only over sftp
[03:29] <jml> right.
[03:31] <jml> mwhudson, anyway, it's something to keep in the back of the mind. getting it set up might save us some boring maintenance work, and give bzr better a tighter feedback loop for new server-side behaviours.
[03:32] <jml> (maybe we should get poolie to do it!)
[03:32] <poolie> saying the word 'egg' requires fighting robert
[03:33] <mwhudson> better than fighting a bear i guess
[03:33] <poolie> questionable
[03:33] <poolie> more seriously, we do have nightly debs
[03:33] <poolie> why not use them+
[03:33] <poolie> s/+/?
[03:33] <wgrant> LP has a vendetta against using packages or anything that isn't woefully insecure.
[03:34] <jml> poolie, I think this is one of those cases where whoever wants to get this done will need to possess a will of iron, regardless of implementation details
[03:34] <jml> poolie, and that given said iron will, they get to do it however they want.
[03:34] <poolie> the good thing is i do have a will of iron
[03:35] <poolie> the bad bit is it's iron filings
[03:35] <jml> hahaha
[03:35] <poolie> os
[03:35] <poolie> so
[03:36] <poolie> hm
[03:36] <poolie> i may try to get it running against the system bzrlib
[03:36] <poolie> not your own copy
[03:36] <jml> poolie, one of the things about using nightlies to consider is that the buildbot doesn't run against them.
[03:37] <jml> poolie, and we only want to update if the tests pass -- it is still a live system running against production data.
[03:41]  * jml afk
[04:30] <mwhudson> ok, i didn't expect this: http://pastebin.ubuntu.com/342383/
[04:30] <mwhudson> (i guess i need to run it with ./bin/py or python2.5)
[04:33] <wgrant> spm: buildd-manager is broken.
[04:34] <jml> mwhudson, nice
[04:34]  * jml does some illicit programming
[04:34] <jml> don't tell anyone
[04:35] <wgrant> https://edge.launchpad.net/~ubuntuone-hackers/+archive/ppa/+build/1129031 is assigned to a builder and utterly broken. I wonder if that is related.
[04:35] <spm> wgrant: I assume that's not a statement of observation; rather a pls fix? :-)
[04:35] <wgrant> spm: Yes please.
[04:36] <spm> hrm. oddness. going for a bounce on it.
[04:36] <wgrant> It might help, but there are some broken build records around...
[04:37] <mwhudson> i wonder if testcasewithfactory should flush the active stores in it's tearDown
[04:37] <spm> ahh. k. will chase them too. ta.
[04:37] <jml> someone just commented that, CACHE_DIRECTORY = os.path.expanduser('~/.launchpadlib/cache') might be a bad idea for windows
[04:37] <jml> does anyone have any good suggestions for what should be used instead?
[04:37] <jml> this is for a launchpadlib cache
[04:38] <spm> wgrant: out of not-idle curisoity, have you considered becomming our nagios system? :-P
[04:38]  * mwhudson finds that all his tests so far violate database constraints, but none of them actually issued any queries
[04:38] <mwhudson> anyway, /me eods more or less
[04:38] <mwhudson> biab
[04:38] <wgrant> spm: Ah, that build is fixed now. I wonder if the restart did that.
[04:38] <spm> haven't been able to get the (*&^(*&^ing thing to stop yet.
[04:39] <spm> I do so love issuing "stop" scripts and have them ignored
[04:39] <wgrant> spm: SIGTERM kills it in not too long for me...
[04:39] <wgrant> Hmm.
[04:39] <wgrant> Interesting.
[04:39] <spm> yeah - but there are "right" ways. I suspect the kill and kill with prejudice are in the immediate futuire here
[04:40] <wgrant> I don't see why an attempt was made to build https://edge.launchpad.net/~ubuntuone-hackers/+archive/ppa/+build/1129031 at all -- it's five months old, and for a disabled archive.
[04:41] <spm> 2009-12-16 04:37:04+0000 [-] Received SIGTERM, shutting down. <== LIES!!!
[04:42] <wgrant> I'
[04:42] <wgrant> I've not worked out why it doesn't just die quickly.
[04:42] <spm> it's pretty effing annoying...
[04:43] <spm> 2009-12-16 04:43:08+0000 [-] Server Shut Down.
[04:43] <spm> awesome. nice and fast.
[04:43] <wgrant> Is it back up yet?
[04:43] <wgrant> Hum.
[04:44] <wgrant> That build oopses sometimes, but not others. That is slightly concerning.
[04:44] <spm> yup. all looks "normal". for values of...
[04:45] <wgrant> Much better. Thanks.
[04:45] <wgrant> Any idea what killed it?
[04:49] <spm> the passage of time...
[04:49] <spm> I tried 2 'stops', one straight up kill; it actually stopped on it's own a few secs before I was going to -9 it.
[04:50] <wgrant> I mean, what broke it?
[04:50] <spm> either way. wrong. bug 497282
[04:50] <mup> Bug #497282: buildd-manager is reluctant on shutting down in a timely manner <Soyuz:New> <https://launchpad.net/bugs/497282>
[04:50] <spm> no idea.
[04:50] <spm> it looked like it was havng issues with one of the hosts. but...
[04:51] <spm> wgrant: what were the symptoms you were seeing that showed it as broken?
[04:51] <wgrant> bohrium was hung as usual, but that happened 10 hours before the breakage.
[04:51] <wgrant> spm: No build dispatched lately.
[04:51] <spm> kk
[04:51] <wgrant> https://edge.launchpad.net/~ubuntuone-hackers/+archive/ppa/+build/1129031 was also sitting on /builders, assigned to a builder but with status 'Needs build'
[04:51] <wgrant> That doesn't make sense.
[04:52] <wgrant> And now it OOPSes intermittently like OOPS-1446ED192
[04:52] <spm> weird
[04:53] <wgrant> It seems like it was pretty effectively broken, since it also wasn't updating the status of builds that were in progress.
[04:54] <poolie> jml, i think the answer to your 'does lplib follow a fixed release schedule' is 'no' :)
[04:54] <jml> poolie, it's _really_ frustrating.
[04:55] <jml> poolie, trunk has some stuff that'll make bzrlib integration much easier.
[04:55] <jml> well, a little easier.
[04:59] <wgrant> That problematic build just got hit again. I wonder if things have jammed up already.
[04:59] <spm> wgrant: aaaah. this may be a bug we've been tracking
[04:59] <wgrant> Yeah, it is.
[05:00] <wgrant> For now, kill that build and restart, I guess.
[05:00] <spm> https://bugs.edge.launchpad.net/soyuz/+bug/496574
[05:00] <mup> Bug #496574: buildd-manager fails to deal with "Fault 8002" errors <buildd-manager> <soyuz-build> <Soyuz:Triaged> <https://launchpad.net/bugs/496574>
[05:00] <spm> and there was another....
[05:00] <wgrant> Oh, could be that, I guess.
[05:01] <spm> meh. can't find it. the gist is that something in the soyuz part is borked. this has been *flooding* us with OOPSes. that you saw that oops, (as did I on a 2nd attempt) suggests that could be it.
[05:02] <wgrant> That build has hit a builder again, but other builds seem to still be working.
[05:02] <wgrant> So maybe the two horrible brokennesses are unrelated.
[05:04] <jml> mwhudson, where does your lazy-import-supporting pyflakes live?
[07:48]  * jml gone
[07:54] <adiroiban> henninge: hi. do you have 5 minutes to answer a questions? :)
[07:54] <adiroiban> here is the code http://paste.ubuntu.com/342540/
[07:54] <henninge> adiroiban: Hi!
[07:54]  * henninge looks
[07:55] <adiroiban> i would like to get rid of the permission checking from model
[07:55] <adiroiban> and only have them in security.py
[07:55] <adiroiban> also to get rid of permission_helper.py
[07:55] <adiroiban> as those checks are also implemented in security.py
[07:57] <henninge> adiroiban: I just created permission_helper.py last cycle
[07:57] <henninge> adiroiban: and I actually have a branch that extends it
[07:58] <henninge> adiroiban: I discussed this at length at the Dallas sprint
[07:58] <adiroiban> henninge: why not have that logic in security.py ?
[07:58] <henninge> adiroiban: because it is needed in the model, too.
[07:58] <henninge> adiroiban: the zope security system will only give you control over access to attributes.
[07:58] <adiroiban> but we can import the class from security.py
[07:59] <henninge> adiroiban: which class?
[07:59] <adiroiban> AdminTranslationImportQueueEntry
[08:00] <adiroiban> like the last example from the pastebin
[08:02] <henninge> but that one still uses is_admin_or_rosetta_expert. Where would that come from.
[08:02] <henninge> ?
[08:03] <henninge> adiroiban: The challange is to control which values the parameters of a method can take in relation to the user that is setting it.
[08:03] <adiroiban> henninge: true. it just replaces the self.isUbuntuAndIsUserTranslationGroupOwner(user)
[08:04] <adiroiban> and similar , we can use OnlyRosettaExpertsAndAdmins
[08:04] <henninge> adiroiban: To me, security.py is our interface to the zope policy. But we have more policy than that.
[08:04] <adiroiban> henninge: yes. but you can do the same in lib/canonical/launchpad/security.py
[08:06] <adiroiban> but with permission_helper.py, we will end up with code duplicated in security.py
[08:06] <adiroiban> as we already have a check similar to is_admin_or_rosetta_expert , in security.py
[08:06] <henninge> the idea was to move the code out of security.py to make it usable in model code
[08:06] <henninge> adiroiban: yes, and that check should use is_admin_or_rosetta_expert.
[08:06] <adiroiban> but then we still need that code for the view
[08:07] <adiroiban> yep
[08:07] <adiroiban> ok
[08:07] <adiroiban> then reference security_helper from security.py
[08:07] <adiroiban> that is also ok
[08:07] <henninge> sorry, which code do we need for the view
[08:07] <henninge> adiroiban: it does!
[08:08] <henninge> adiroiban: security has just not been converted to use these helpers
[08:08] <henninge> completely
[08:08] <henninge> security.py, I mean
[08:08] <adiroiban> henninge: yes. I see know.
[08:09] <henninge> adiroiban: may be permission_helpers is the wrong term
[08:09] <adiroiban> then I should implemenet all the translations security logic in security_helper.py
[08:09] <adiroiban> and then use that code from security.py
[08:09] <henninge> adiroiban: yes, and call it permission_checkers.py
[08:10] <henninge> adiroiban: I am moving the file out of translations into services anyway.
[08:10] <henninge> adiroiban: I will do the renaming. Can you wait until my branch is done? This should happen this morning.
[08:10] <adiroiban> henninge: ok. It make more sense now :)
[08:11] <adiroiban> yes. no hurry
[08:11] <henninge> Great ;)
[08:11] <henninge> adiroiban: actually, danilo wants me to de done with it ... ;)
[08:12] <adiroiban> henninge: but why is not a good idea to use security.py classes in the model ?
[08:13] <henninge> adiroiban: I have not thought much about that but my first impression is this:
[08:13] <henninge> security.py is our interface to the permissions mentioned in the zcml
[08:14] <danilos> I don't think it would such a bad idea, especially since they define a permission for a user to a model class
[08:15] <henninge> so, if there is a <require> statement on a class that requires a certain permission, there will be a checker or it in security.py
[08:15] <henninge> but, as I mentioned before, that does not give us finer control over method parameters.
[08:16] <henninge> so we have to add checks in the model about parameter values.
[08:16] <adiroiban> @enabled_with_permission('launchpad.Admin') can only be used in the view?
[08:16] <danilos> henninge, right, but those checks can be gotten by using different privileges... ie. if has_perm(user, 'launchpad.Admin'): allow this
[08:16] <henninge> If we want to use the classes from security.py for this, we'd have to add classes there that have no relation to the zcml
[08:17] <danilos> adiroiban, you can define in ZML what attributed/methods are accessible for each permission, but there are cases where you want to allow only certain values to be passed in by certain users (i.e. henning has an example of setStatus on translation import queue, where only admins can set any status)
[08:17] <henninge> adiroiban: on, it is used on the interface, thus on the model. But it only applies to attributes.
[08:17] <adiroiban> you know better. I see security.py as the place to store all security logic
[08:18] <henninge> adiroiban: yes, I think it is a question of what we define security.py to be and what is supposed to be in there.
[08:18] <adiroiban> danilos: yep. I saw that code. and maybe we can have those values in a different attribute
[08:18] <adiroiban> :)
[08:18] <adiroiban> or just do the check in security.py
[08:19] <henninge> adiroiban: I thought about that
[08:19] <henninge> that would have meant to have seperate "setStatusApproved", "setStatusFailed" etc
[08:19] <henninge> or "setStatusAdmin".
[08:19] <henninge> I was advised against that at the sprint.
[08:20] <adiroiban> henninge: ok. np.
[08:20] <henninge> just saying
[08:20] <adiroiban> then I will add the logic in security_helper.py
[08:20] <adiroiban> and make use of it from security.py and from the model
[08:21] <henninge> adiroiban: that is how I meant it to be
[08:21] <henninge> adiroiban, danilos: but maybe we should take that discussion to the list as this is a general discussion about the use of security.py.
[08:21] <danilos> henninge, yep, sounds like a good idea
[08:22] <henninge> ok, I will do that
[08:26] <adiroiban> henninge: i think that is ok to move code away from security.py ... as it can become a big file, but I think we should still use the security.py interface from the model. Instead of security_helper.is_admin_or_rosetta_expert() use security.OnlyRosettaExpertsAndAdmins.checkAuthenticated
[08:26] <adiroiban> or create a new permission interface
[08:27] <adiroiban> but I will wait for your branch
[08:27] <adiroiban> and the discussion from the ml
[08:28] <henninge> adiroiban: yes, the discussion will be of most interest as I don't want some-one else to come along next cycle or so and change it all over again. We need some consensus here across the team.
[08:30] <adiroiban> henninge: ok.
[08:53] <henninge> adiroiban: I just realised you cannot just use " security.OnlyRosettaExpertsAndAdmins.checkAuthenticated" from model code as checkAuthenticated is not a class method.
[08:53] <henninge> adiroiban: you'd have to instantiate OnlyRosettaExpertsAndAdmins first.
[08:54] <adiroiban> yes. I'm doing something like this OnlyRosettaExpertsAndAdmins( self).checkAuthenticated(user)
[08:55] <henninge> I see
[08:56] <adiroiban> I'm running now all tests
[08:56] <adiroiban> and see if there are problems
[09:18] <mrevell> morning
[10:07] <maxb> Hi, I have a trivial lp-dev-deps change, if someone has a moment: https://code.edge.launchpad.net/~maxb/meta-lp-deps/no-pullparser/+merge/16232
[10:35] <jtv> hi mrevell!  you have nag mail.  :-)
[10:36] <mrevell> jtv, thanks, I see it :) Will get to it today
[10:36]  * jtv cheers mrevell on
[10:36] <mrevell> heh
[10:52] <stub> henninge: A long, long time ago we specced out a system of crowds, where you would construct a crowd by combining teams and peoples. You could then query the crowd to see if a person was or was not a member of that crowd. Designed to be DB friendly, but also would make nicer things like is_admin_or_rosetta_export()
[10:53] <henninge> stub: sounds cool
[10:55] <jtv> al-maisan_: do you know if there are any current plans to move Build.sourcepackagerelease (and the stuff that relies on it) into BuildPackageJob?
[10:55] <al-maisan_> jtv: on the phone, ttyl
[10:55] <jtv> pl
[10:55] <jtv> ok
[10:56] <stub> henninge: The crowd was really just a list of Person (or even just their ids), and the 'is in' and 'isn't in' operations just single queries against the TeamParticipation table.
[11:04] <deryck> Morning, all.
[11:13] <al-maisan_> jtv: AFAIU there are no plans to relocate Build properties into BuildPackageJob
[11:13] <al-maisan_> jtv: why do you ask :)
[11:13] <jtv> al-maisan_: my question was misguided.  I don't need a Build for our prospective BuildFarmJob implementation, do I?
[11:13] <jtv> hi deryck
[11:15] <al-maisan_> jtv: you probably don't .. what data/properties do you envision being in your "TranslationFarmJob" ?
[11:15] <jtv> al-maisan_: a reference to the branch it should gets its data from.
[11:16] <al-maisan_> jtv: in that case it would seem there's no need to reference a `Build`
[11:48] <jtv> bigjools, is this the right interpretation of you described on the phone?  http://rookery.canonical.com/~jtv/farmjob.dia
[11:49] <bigjools> can you turn that into a PNG?
[11:49] <jtv> bigjools: with the power of free software, yes I can!
[11:50] <jtv> bigjools: http://rookery.canonical.com/~jtv/farmjob.png
[11:51] <jtv> bigjools: and then I gather our BuildFarmJobBehavior would receive a BuildQueue entry to work on
[11:57] <bigjools> jtv: it's a bit corrupted
[11:57] <bigjools> is the << Iwhatever >> part supposed to be an "implements" ?
[11:57] <jtv> bigjools: yes
[11:58] <jtv> although maybe the base class does that... not too important I guess :)
[11:58] <bigjools> jtv: ok it's wrong on your translations one then :)
[11:58] <jtv> bigjools: ahhh, they're both wrong actually: meant to say IBuildFarmJob on both
[11:59] <bigjools> jtv: that's the basic gist of things, yes.  Although you will need content classes and builder behaviours as well.
[11:59] <jtv> bigjools: I knew about the behaviors but left them out here because I'm focusing on db schema right now... what are the content classes for?
[12:00] <bigjools> jtv: scratch that you already have one, sorry
[12:00] <jtv> ah, branch :)
[12:01] <bigjools> bbiab
[12:17] <danilos> adiroiban, hi, have you done the QA on https://bugs.edge.launchpad.net/rosetta/+bug/406477 as well?
[12:17] <mup> Bug #406477: Need more permissions on admin template pages for ubuntu-translations-coordinators <qa-needstesting> <Launchpad Translations:Fix Committed by adiroiban> <https://launchpad.net/bugs/406477>
[12:18]  * adiroiban looking
[12:22] <maxb> salgado: Hi. If you're around, I'm going to be doing a lp-deps upload today, if you wanted to put the ssh removal in too
[12:29] <salgado> hi maxb.  I'll try to get that in before you upload, but if it's not there by the time you get to it, don't worry
[12:29] <salgado> unless you want to do it yourself and get the blame^Wcredit for it
[12:36] <jtv> adiroiban: need help with that Q/A?  I have an unprivileged account for comparison
[12:37] <adiroiban> jtv: yes. please test this link https://translations.launchpad.net/ubuntu/karmic/+source/kdepim/+pots/kxforms/+admin
[12:38] <adiroiban> do I need to create a test account on edge or staging is also ok?
[12:38] <adiroiban> I'm new to LP qa process
[12:38] <jtv> adiroiban: staging should be fine, provided you're sure that your branch has been rolled out there
[12:39] <adiroiban> i can not access staging right now
[12:41] <GOTTMODUS> Hi everyone
[12:42] <GOTTMODUS> to wich user is the svn import branch review going?
[12:42] <jtv> no need to shout!  :)
[12:42] <GOTTMODUS> i cant see ist from the default users site
[12:42] <GOTTMODUS> ??
[12:42] <GOTTMODUS> where did i shout?
[12:42] <jtv> gottmodus: your nick
[12:42] <GOTTMODUS> ah ok
[12:42] <jtv> adiroiban: same here...  and getting a "not found" for that page on edge.  We're expecting an "access denied," no?
[12:43] <adiroiban> jtv: no. I should be ok
[12:43] <jtv> gottmodus: the joke does work better with all caps, but it's a bit noisy nonetheless :-)
[12:43] <adiroiban> the Navigation is breacking that chain
[12:45] <adiroiban> jtv: I have tested as an UTC and everything is ok
[12:49] <jtv> adiroiban: it's a bit weird though that it says "there's no page with this address in Launchpad" when it should say that I'm not allowed to access the page
[12:50] <adiroiban> jtv: that was the same case in the previous implementation
[12:50] <jtv> adiroiban: in that case, no worry here.  :)
[12:51] <adiroiban> jtv: you can try on lp.net
[12:52] <adiroiban> jtv: i disabled my redirection for edge, and tested on stable and I also got a page not found error
[12:52] <adiroiban> jtv: there should not be a problem, since the user does not see the admin link
[12:53] <adiroiban> jtv: actually, neither do UTCs ... as the +templates pages times out
[12:53] <jtv> :(
[12:54] <wgrant> bigjools: Do you know if dpkg + buildds are upgraded for tomorrow's rollout?
[12:56] <jtv> adiroiban: from an unprivileged account I see neither the link to that page, nor the same for another (non-deactivated) template.  So looks good to me.
[12:57] <bigjools> wgrant: in progress, but not yet AFAIK
[13:01] <adiroiban> danilos: I don't know what to say. I have tested on my computer, and tested on edge as UTC. Everything was ok. Also the test was written to cover an anonymous, a logged in user and an Admin
[13:02] <danilos> adiroiban, right, it was mostly to do some QA, since you haven't marked it as qa-ok in the bug... also, QA is usually done on edge and/or staging, you might be surprised, but many things break only when we hit production database :)
[13:02] <jtv> adiroiban: did D. find something wrong with the branch?
[13:03] <adiroiban> jtv: I don't know. He approved it
[13:03] <jtv> just confusion over the qa process then I guess?
[13:04] <adiroiban> jtv: yes. I did not tag it with qa-ok
[13:04] <adiroiban> but only qa-needtesting
[13:04] <jtv> We're weird that way. :)  It's a pretty nice system actually.
[13:04] <adiroiban> I was thinking that I should mark qa-needtesting, whey I need someone else to also look into it
[13:09] <jtv> adiroiban: it should happen automatically (though we did have some breakage recently)
[13:10] <adiroiban> jtv: well I don't know how things should be going... so as always... I am very confused
[13:10] <jtv> adiroiban: need a summary?
[13:11] <adiroiban> jtv: or a wikipage ? :)
[13:11] <jtv> adiroiban: don't think we have one for this, since it's still only on an experimental scale...
[13:12] <adiroiban> jtv: so when my branch is merged with a fixes=lp:222 the bug report is updated to fix-comminted and qa-needtesting tag is added?
[13:12] <adiroiban> and then I have to test the commit on devel/staging and set it to qa-ok ?
[13:12] <jtv> adiroiban: the bug status is not updated to "fix committed" iirc, but otherwise, yes
[13:13] <jtv> And you try to Q/A on staging or edge, not just devel because of the unexpected differences that real-life data can make (see what D. said above)
[13:13] <adiroiban> jtv: I have tested all my bugs targeted for this release and tagged them with fix-ok
[13:14] <jtv> adiroiban: we usually just verb "QA" to avoid confusion with the test suite.
[13:15] <adiroiban> jtv: ok. thanks for the jargon update :)
[13:15] <jtv> Glad you don't mind; I know I'm pedantic but who knows what confusion it may save later :)
[13:16] <adiroiban> well I still have problems with page tests / stories / functional tests ... etc
[13:26] <beuno> BjornT, bug 497405
[13:26] <beuno> \o/
[13:26] <mup> Bug #497405: Run Windmill tests by default <story-windmill-layer> <Launchpad Foundations:In Progress by bjornt> <https://launchpad.net/bugs/497405>
[13:29] <BjornT> beuno: i'm really looking forward not having to monitor the jscheck builder constantly, and chase people to fix things. better to have buildbot take care of that :)
[13:30] <beuno> BjornT, yeah, and I'm happy to never have to stare at flacoste when we mention tests slowing people down to develop awesomeness
[13:36] <salgado> BjornT, can we use utilities/ec2 to run the windmill tests?
[13:37] <BjornT> salgado: yes. if you grab my branch, you can.
[13:44] <salgado> BjornT, wow, I was expecting a "not yet" answer.  this is great news
[13:44] <salgado> I might even review your branch
[13:57] <beuno> joey, have you changed your default font settings?
[13:58] <joey> that was fast :-)
[13:58] <joey> beuno: no
[13:58] <joey> should I?
[13:58] <beuno> joey, that that I don't trust you
[13:58] <beuno> but
[13:58] <beuno> what's the values?  :)
[13:59] <beuno> what are
[13:59] <beuno> serif, 16, monospace, 12?
[14:00] <beuno> joey, Preferences > Content > Fonts / Advanced
[14:00] <joey> Loading FF. Was in chrome
[14:01] <joey> can't find the option in chrome
[14:01] <joey> 16 and 12 in FF
[14:01] <beuno> hm
[14:02] <beuno> and you see all bug pages with the side portlets at the bottom?
[14:02] <joey> yes
[14:02] <joey> on both FF and chromium
[14:03] <joey> started about a week ago
[14:03] <joey> or more
[14:03] <joey> I was out for a few weeks
[14:03] <joey> it was like that when I came back to work
[14:03] <beuno> joey, and your fonts
[14:03] <beuno> system fonts
[14:03] <beuno> in appearance
[14:03] <beuno> are they set at 10?
[14:03] <joey> afaict, nothing has changed
[14:03] <joey> it happens on two different computers
[14:03] <joey> my desktop and my netbook
[14:04]  * joey looks at his sys fonts
[14:04] <joey> as soon as I figure out where they are. I'm not a font junkie
[14:04] <joey> all listed as 10 on my desktop
[14:04] <beuno> I'm running out of ideas
[14:05] <beuno> WFM (and I think, in general)
[14:05] <joey> try css :-)
[14:05] <beuno> one last test
[14:05] <beuno> can you start firefox with a clean profile, no addons?
[14:05] <joey> sure
[14:06] <beuno> ok
[14:06] <beuno> I can reproduce now
[14:06] <beuno> joey, not needed
[14:06] <beuno> if you have your browser wide enough
[14:06] <beuno> it happens
[14:06] <joey> yeah I JUST now noticed that
[14:06] <beuno> you probably have 1600+ res, right?
[14:06] <joey> 1920 on the desktop, 1280 on the netbook
[14:07] <joey> the clean profile I opened in a window and it was correct, and when I maximized, poof
[14:07] <beuno> I can't reproduce it in 1280, but now we know there's an issue there
[14:07] <beuno> sinzui, where you aware ^>
[14:09] <sinzui> beuno: danilo remarked upon it. I could not reproduce it to identify if we need to add a css rule or markup to base-layout.pt
[14:17] <joey> beuno: a side note... all my computers are widescreens
[14:17] <joey> beuno: so that may be why I see it at other resolutions
[14:17] <beuno> joey, yeah, very likely
[14:18] <beuno> if the width of the sidebar is seto to 17%
[14:18] <beuno> it doesn't break
[14:27] <beuno> joey, bug 493518
[14:27] <mup> Bug #493518: Side portlet moved again below the main content on wide-screen displays (1920x1200) <Launchpad Foundations:Triaged> <https://launchpad.net/bugs/493518>
[14:36] <Pilky> beuno: if it helps, Safari 4 doesn't have the issue, I can spread my browser window across 2 displays and it works fine
[14:36] <beuno> Pilky, interesting...
[14:36] <Pilky> let me just try firefox
[14:38] <Pilky> oh wait, does happen in safari
[14:38] <Pilky> had the wrong bug visible
[14:38] <beuno> ok, that's good news then  :)
[15:55] <danilos> joey, beuno, sinzui: there was a bug along those lines before, which I fixed, but it's back with a vengeance when #maincontent CSS was removed: https://bugs.edge.launchpad.net/launchpad-foundations/+bug/435346
[15:55] <mup> Bug #435346: 3.0 interface overflows sidebars and causes horizontal scrolling if you manually change browser font sizes <qa-ok> <Launchpad Foundations:Fix Released by danilo> <https://launchpad.net/bugs/435346>
[18:00] <james_w> how does a branch become owned by ~vcs-imports?
[18:00] <james_w> I just requested an import and it is under ~james-w, I assumed it went under the former
[18:01] <cody-somerville> james_w, it shouldn't be under ~james-w unless thats changed.
[18:01] <cody-somerville> james_w, whats the branch?
[18:02] <james_w> ~james-w/alsa-driver/trunk
[18:36] <salgado> sinzui, is there any reason why registry/templates/object-timeline-graph.pt doesn't use the new stylesheet?
[18:37] <sinzui> salgado: yes it is in an iframe. It should be just canvas and thus not use any css
[18:37] <sinzui> salgado: if the template now has markup displayed to users, we need to reconsider this
[18:38] <salgado> sinzui, oh, right, my question was actually: "why does it use the old stylesheet instead of the new one".
[18:39] <salgado> should it use none?  I'd be more than happy to change that
[18:41] <sinzui> salgado: I do not think it needs css, I see every element uses a style attribute to disable the default. If I am wrong, it must use style-3.0.css.
[18:42] <salgado> ok, I'll remove the launchpad-stylesheet macro from it and see what happens
[19:46] <mwhudson> good morning
[19:58] <thumper> morning
[20:10] <thumper> mwhudson: I changed the url for https://code.edge.launchpad.net/~vcs-imports/analysesi/main, but the update still looks at the old location
[20:10] <thumper> mwhudson: I'm pretty sure it is the same repository, just at a different location
[20:10] <thumper> mwhudson: how do we blow away the existing checkout?
[20:10] <mwhudson> thumper: oh for CVS its completely terrible
[20:11] <mwhudson> thumper: https://wiki.canonical.com/InformationInfrastructure/OSA/LPHowTo/UpdateCodeImportLocation
[20:11] <mwhudson> thumper: needs a LOSA :(
[20:11] <thumper> ok
[20:12] <thumper> mwhudson: ew
[20:13] <mwhudson> thumper: yes
[20:15]  * mwhudson fights with storm
[20:36] <sinzui> bac: what are your plans for Bug 447418
[20:36] <mup> Bug #447418: Timeout with large milestone with lots of private bugs <timeout> <Launchpad Registry:In Progress by bac> <https://launchpad.net/bugs/447418>
[20:47] <bac> sinzui: don't know yet
[20:47] <bac> sinzui: just started looking.
[20:53] <thekorn> intellectronica, hi, thanks to you guidance last evening I managed to fix bug 497108, I attached the branch and a screenshot of the result.
[20:53] <mup> Bug #497108: show changes to the affected product field of a task in the interleaved activity log <Launchpad Bugs:New> <https://launchpad.net/bugs/497108>
[20:53] <thekorn> what's the next step?
[20:53] <intellectronica> thekorn: that's wonderful! thank you so much for taking on this work
[20:55] <intellectronica> thekorn: go ahead and propose the branch for merging. i can review it now. the tree is closed right now (release in 1h) but we can land this as soon as it opens again
[20:56] <thekorn> ok
[21:00] <thekorn> intellectronica, created merge proposal at https://code.edge.launchpad.net/~thekorn/launchpad/affects_in_interleaved_activitylog/+merge/16261
[21:01] <sinzui> bac: sorry, I was called away to get children from the local institution
[21:01] <intellectronica> thekorn: huh, that's a very small diff :)
[21:02] <thekorn> intellectronica, yes, that surprised me too
[21:02] <intellectronica> thekorn: we do need to add a test, though, to demonstrate the new behaviour
[21:02] <sinzui> bac: I was pondering (this weekend) of converting. the bug table to an ajax call like subscribers. I need to see all the bugs when looking at a milestone, so I am not keen to use a batch navigator.
[21:03] <thekorn> intellectronica, that's what I thought, can you point me to a place where I should add them
[21:03] <thekorn> should I add a doctest or a unittest
[21:03] <sinzui> bac: my plan may be total rubbish because the SQL time on the page is very good as I recall. Most of the time was in python, and I think it is in the status counts, the same code we disabled on series because they caused timeout.
[21:03] <intellectronica> thekorn: there should be a story test somewhere, looking for it
[21:04]  * sinzui suspects something with enums, but he really does not know wtf is wrong with the code
[21:04] <thekorn> intellectronica, and most importantly: is there a way to only run relevant test, and not this huge testsuite
[21:05] <intellectronica> thekorn: of course :) `bin/test -vv -t $pattern` where pattern is a regex matching the paths of the tests you'd like to run
[21:07] <thekorn> ok, so stories are doctests, nice
[21:08] <sinzui> thekorn: that is almost nice. most stories are mediocre function tests instead of user integration tests.
[21:09] <intellectronica> thekorn: see lib/lp/bugs/stories/bugs/xx-bug-activity.txt
[21:09] <intellectronica> thekorn: to run it, go `bin/test -vv -t xx-bug-activity.txt`
[21:15] <thekorn> ok, lets try to compile a test
[21:42] <sinzui> I think I just approve the last two mailing lists that will ever need approval
[21:42] <sinzui> I think I just approved the last two mailing lists that will ever need approval
[21:47] <bac> sinzui: yeah, as soon as i started looking at this problem i ran into our friend get_status_counts
[21:49] <sinzui> It looks so simple to loop of a fixed set of object that are cached. yet I suspect something is not cached, or worse, the access of status is very costly
[21:53] <wgrant> When is 3.2.1/3.1.13/whatever it is?
[21:55] <sinzui> wgrant: I think we are going to rename the series 10.05 and the milestone will be named 01 after the month
[21:56] <sinzui> wgrant: We are trying to use series like we tell other projects
[21:56] <al-maisan_> sinzui: the series?
[21:56] <wgrant> sinzui: But that's barely useful, since LP doesn't really release, and has no use for series.
[21:56] <sinzui> al-maisan_: yes rename the series to make sense, and the milestone to be the month
[21:56] <sinzui> or the step
[21:57] <wgrant> Anyway, I don't really care about how it's spelt -- what is the targetted release date?
[21:57] <sinzui> wgrant: it does not make sense to ever create a new series since we do not release, but since a series sets the focus of development, and we mean to be very focused for this series, we would be insane to create another series
[21:58] <sinzui> I wish I knew. I took a guess for the registry
[21:58] <wgrant> Ah. And when is ~launchpad on vacation?
[21:59] <thumper> wgrant: for me, real soon now :)
[21:59] <sinzui> I think we stop getting paid to work on the 25 of December and most of us return on  January 2
[21:59] <thumper> sinzui: 2nd is a Saturday
[21:59] <wgrant> Ah, so just the week. Great.
[22:00] <sinzui> thumper: true.
[22:00] <bac> thumper: you don't get paid for saturdays?
[22:01] <sinzui> I hope not, otherwise management would tell me to stop woring on what I want to work on
[22:03] <sinzui> I started a branch to add karma to registry actions (with the ulterior motive to wire all the events so that I can send notifications and create sparklines). I hope to finish over the holidays