/srv/irclogs.ubuntu.com/2011/01/05/#launchpad-dev.txt

maxbUrgh00:21
maxbbzr-tarmacland breaks 'bzr selftest'00:21
pooliemaxb, as in, it has failing tests, or it breaks it entirely?00:30
lifelesspopping into supermarket back in a bit00:30
maxbas in, it has code in its tests that failed to import, so the entire execution dies00:52
wgrantthumper: Are you looking at the buildbot failure too?01:29
wgrantIt is legit, for once.01:29
thumperI wasn't01:29
* wgrant does.01:29
thumpergah, my landing failed due to the non [testfix] nature01:39
* thumper leaves the devel fix to wgrant01:39
thumperwgrant: is it obvious?01:40
wgrantthumper: Yes.01:42
wgrantthumper: Just running the Bugs tests now.01:42
wgrant(the test suite was clearly not run over the problematic branch :/)01:43
brycehrunning rocketfuel-get just now it fails in mailman:02:05
brycehCompiling /home/bryce/launchpad/lp-branches/devel/lib/mailman/Mailman/i18n.py ...02:05
brycehCompiling /home/bryce/launchpad/lp-branches/devel/lib/mailman/Mailman/versions.py ...02:05
brycehmake[1]: Leaving directory `/home/bryce/launchpad/lp-sourcedeps/sourcecode/mailman'02:05
brycehmake: *** [compile] Error 202:05
brycehmake: Leaving directory `/home/bryce/launchpad/lp-branches/devel'02:05
lifelessyup02:06
lifelessuse lucid02:06
lifelessor fiddle with stuff under the hood as per sinzui's bug about this02:06
bryceh$ grep CODENAME /etc/lsb-release02:06
brycehDISTRIB_CODENAME=lucid02:06
brycehbug #?02:06
lifelessinteresting02:08
lifelesshmm, possibly we've broken mailman on lucid by fixing for natty><02:08
lifelesssinzui: ^02:08
StevenKSo we're aiming for Lucid, Maverick and Natty?02:09
lifelesswe deploy on lucid.02:10
lifelessits mandatory until a new LTS is ready02:11
lifelesseverything else I don't particularly care about :)02:11
=== Ursinha-afk is now known as Ursinha
spmARGH!02:31
spmwho made the change that makes it impossible to suspend a user without forcibly resetting their password?02:31
* spm grumps02:31
thumperspm: not me02:32
wgrantspm: Wha? LP doesn't have passwords.02:33
spmfiik. wouldn't let me suspend them unless I set their password as well.02:34
spm +reviewaccount fwiw. has password fields now02:34
spmclick the 'change' button and get a "No! Password not set! bad Losa!" error message.02:35
lifelessfile a bug02:36
spmnearly completed. I was ranting here so the bug won't be quite so vitrolic.02:37
spm:-)02:37
lifeless=== Top 10 Time Out Counts by Page ID ===02:37
lifeless    Hard / Soft  Page ID02:37
lifeless     150 / 5403  Archive:+index02:37
lifeless      98 /  385  BugTask:+index02:37
lifeless      97 /  126  Archive:EntryResource:getPublishedBinaries02:37
lifeless      37 /  332  Distribution:+bugs02:37
lifeless      29 /  134  ProjectGroupSet:CollectionResource:#project_groups02:38
lifeless      20 /   33  MailingListApplication:MailingListAPIView02:38
lifeless      13 /    8  ProjectGroup:+milestones02:38
lifeless      10 /   13  DistroSeriesLanguage:+index02:38
lifeless       9 /  307  Distribution:+bugtarget-portlet-bugfilters-stats02:38
lifeless       7 /   14  NullBugTask:+index02:38
spmthumper: do we have any juju to remove comments from merge proposals?02:44
thumperspm: no02:44
thumperspm: just sql02:44
thumperspm: just another of the reasons we should have a singular comment interface02:44
thumper(which we don't have)02:45
spmI don't spose you have that handy?02:45
spmheh02:45
thumperspm: sorry, no02:45
thumperspm: the table is codereviewcomment02:45
* spm files another bug ;-)02:45
lifelessthumper: it is pretty much a single thing in the data model; what do you see as needed to propogate it higher?02:49
thumperbugs handle comments differently02:49
spmso do answers fwiw02:49
thumperlifeless: bugs store the initial description as the first comment (which is hidden in the UI)02:49
thumperlifeless: there are also bug specific fields on the message table02:50
thumperlifeless: and the comments pretend to be email messages02:50
wgrantAnd don't even start thinking about attachments...02:50
thumperwhich they aren't always02:50
lifelessthumper: there are? I thought those fields were in BugMessage02:50
thumperI seem to recall some specific bug thing02:50
thumperperhaps it is gone now02:50
thumperbut the underlying model is quite different02:51
thumperand should be normalised02:51
thumperand extracted from the message table02:51
thumperwhich is a pile of poo02:51
thumperwgrant: how are those tests going?02:51
lifelessthumper: what would that leave behind? why isn't it just s/message/comment/ (and thus not very interesting)02:52
thumperlifeless: the incoming email processor stores all emails directly in the message / messagechunk tables02:53
thumperas well as the librarian02:53
thumperit is not a good model for comments02:53
thumperthe message table doesn't store the text02:53
thumperthere are one or more message chunks that do that02:53
thumperit is just overly messy02:53
lifelessyes, thats done to handle ginormous comments02:53
thumperwell, I don't have the original raisins02:54
lifelessit lets us sequence comments without having to deal with a very fat table02:54
lifelessso its faster02:54
wgrantthumper: Sorry, got distracted with payroll stuff. I'm pretty sure they try to make it as awkward and unintuitive as possible.02:57
* wgrant creates an MP.02:57
thumperwgrant: if it is a testfix, rs=me03:02
wgrantthumper: https://code.launchpad.net/~wgrant/launchpad/makeBug-testfix/+merge/4520003:03
thumperwgrant: done03:05
wgrantthumper: Thanks.03:06
lifelesspoolie: around?03:55
poolielifeless, hi04:04
lifelesspoolie: call ?04:04
poolielifeless, hi,  now?04:16
lifelesshttps://dev.launchpad.net/BugTriage04:19
lifelesshttps://bugs.launchpad.net/launchpad-project/+bugs04:23
lifelesswgrant: hey06:03
lifelessstub: hi06:03
stubyo06:04
lifelessarchive:+index is getting worse daily06:04
lifelessany chance you can drill in a bit to get some faster way to answer the questions it needs to ?06:04
wgrantdogfood sort of fails to be terribly useful at analysing this sort of query.06:05
wgrantBecause dogfood is awful.06:05
lifelessit succeeds at being terrible06:05
stubI'm supposed to be dealing with the test suite leaving garbage db's around, which I guess I should bump in favor of the timeouts.06:07
lifelessah06:08
stubDo we have any real slow queries, including the ids in the IN clauses?06:08
lifelessonly the 500ms ones06:08
lifeless(which is pretty slow given the amount of data they are returning)06:08
lifelessstub: well, I can't speak for your priorities right now :) - but to me the test suite stuff is important, but unblocking other developers is more important [for you specifically]06:09
lifelessI don't know if gary would agree06:09
stubI can try to reproduce slow queries using random ids in the IN clause, but genuine data will work better.06:10
wgrantI can try to find some genuine data.06:11
lifelesswgrant: are you able to generate a representative ready-to-run query ?06:11
lifelessjinx!06:11
wgrantNot sure how valid it will be, given that DF is from October.06:11
wgrantBut we'll see.06:11
lifelesswgrant: perhaps a template query and a couple of queries to run on prod to populate data like archive ids etc06:11
lifelessok, I need to run for a while to organise dinner06:12
stubwgrant: I can run a query on production to generate the list of ids if that helps06:15
wgrantstub: Thanks. I'll work one out soonish.06:16
=== almaisan-away is now known as al-maisan
al-maisanGood morning !06:31
wgrantMorning al-maisan.06:32
lifelessbryceh: fwiw bug 69744106:55
_mup_Bug #697441: buildmailman fails under python 2.7 (natty) <python-upgrade> <Launchpad itself:Triaged> < https://launchpad.net/bugs/697441 >06:55
stubwgrant: When we are doing those 400-1000ms queries with the SourcepackagePublishingHistory.id IN (...) clauses, do we already have the SourcepackagePublishingHistory objects available? I suspect we don't need to actually join with that (big) table in most cases.07:24
wgrantstub: We should have them. But that should be fairly cheap regardless, right?07:26
lifelessI'm curious what an explain analyze says is up07:27
stubIts a big table, and unnecessary joins constrain the planner. And I usually consider 100ms 'fairly cheap', so yes :)07:27
stubwgrant: Do you know what the BuildFarmJob.status codes we are selecting for?07:33
wgrantstub: Let me see if I can remember which method it is.07:33
stublifeless: http://paste.ubuntu.com/550516/ with random ids and buildfarmjob.status IN (1,2)   (both statuses are fairly large categories)07:38
lifelessso its having to generate temp datasets07:41
lifelessboth of which are being built and sorted rather than delivered from indices07:42
lifelessit also looks to be highly correlated07:44
lifelessstub: are both halves of the union equally expensive?07:45
stublifeless: roughly07:48
stubUnfortunately I can't easily benchmark the variant that eliminates the two unnecessary ORDER BY and SourcePackagePublishingHistory joins, as I end up with about 6 subqueries that make it go slower.07:50
lifelesshmm07:50
lifelessI see 193 and 749 now that I look closely07:50
lifelessso the >< side is the one to focus on07:50
stubWhere do you see that? I see 1067 and 90807:53
stubOh... actual time. I'm using estimated time. Actual time will be affected because rows will already be in RAM07:54
lifelesswelll. run it twice ;)07:55
lifelesswe've seen mismatches between estimate and actual that matter before, haven't we?07:56
stubInteresting Gnome lockup...08:05
stubAnyway...08:05
stubjust removing the two unnecessary ORDER BY statements in the subqueries seems to half the runtime by itself. Removing the SourcePackagePublishingHistory table from the joins should be a decent win too.08:06
adeuringgood morning08:35
mrevellMorning08:58
mptWould any kindly Launchpad developer be able to give me a list of the top, say, 50 Launchpad projects by number of blueprints they have?11:04
wgrantmpt: https://pastebin.canonical.com/41512/, but it's a couple of months out of date.11:14
mptwgrant, brilliant, thanks.11:14
=== Ursinha-afk is now known as Ursinha
=== matsubara-afk is now known as matsubara
deryckMorning, all.12:02
wgrantmpt: Are we?12:32
mptwgrant, are we what?12:33
wgrantmpt: Starting to contact the projects that most use blueprints.12:33
mptwgrant, ah, yes, I just talked with mrevell about it12:33
wgrantExcellent, excellent news.12:34
leonardrgmb, i seem to be using an ec2test image that doesn't have the python-lxml dependency you added around dec. 2312:40
leonardrdo you know how that could be happening?12:40
wgrantIs the branch you're running utilities/ec2 from reasonably up-to-date?12:41
leonardrwgrant: i think so, but maybe not12:41
leonardri'm updating now12:41
leonardrhopefully that'll fix it12:41
wgrantThe test run will merge devel before it starts, but you need a recent version locally to have the image whitelisted.12:41
leonardrthanks, i'm guessing that was the problem12:45
leonardrtrying again now12:45
leonardr"using machine image version 504"12:46
wgrantLooks good.12:46
=== leonardr is now known as leonardr-afk
=== mrevell is now known as mrevell-lunch
=== yofel_ is now known as yofel
=== matsubara is now known as matsubara-lunch
=== mrevell-lunch is now known as mrevell
bacabentley, adeuring, allenap , bac, benji, danilo, sinzui, deryck, EdwinGrubbs, flacoste, gary, gmb, henninge, jelmer, jcsackett, jtv, bigjools, leonard, mars, mrevell: Reviewer meeting ping14:59
gary_posterthanks14:59
deryckyes, thanks14:59
adeuringbac: thanks for the reminder!14:59
gmbTa15:00
jcsacketthenninge: ping.15:20
henningeHi jcsackett!15:20
jcsacketthi henninge. is recife still undergoing qa?15:21
henningejcsackett: yup15:21
jcsackettdo you know when it might be done? i'd like to be able to be sure it will make release. :-)15:21
henningejcsackett: I plan to finish tomorrow around this time. I don't expect any problems atm.15:22
jcsacketthenninge: that sounds excellent. can you let me know if you run into any hurdles or if there's any way i can help out?15:23
henningejcsackett: sure, I will15:23
henningethanks for offering! ;)15:23
jcsackett:-)15:23
jcsackettthanks, henninge.15:23
=== matsubara-lunch is now known as matsubara
flacosteEdwin-afk, sinzui: how is QA of bug 682727 coming along?15:52
_mup_Bug #682727: obsolete-junk/+series times out when the user is not anonymous <lp-registry> <qa-needstesting> <timeout> <Launchpad itself:Fix Committed by edwin-grubbs> < https://launchpad.net/bugs/682727 >15:52
flacostejcsackett: can you QA bug 589584?15:52
_mup_Bug #589584: merge proposal status is clickable but doesn't show hand cursor <ajax> <bugjam2010> <confusing-ui> <lp-code> <qa-needstesting> <trivial> <Launchpad itself:Fix Committed by jcsackett> < https://launchpad.net/bugs/589584 >15:52
EdwinGrubbs flacoste: it's done, I just marked it now.15:53
flacostethanks EdwinGrubbs!15:53
jcsackettflacoste: qaing it now.15:53
=== deryck is now known as deryck[lunch]
=== salgado is now known as salgado-lunch
jcsackettflacoste: i'm having to hunt down another problem--the branch merge proposal page is OOPSing on qastaging on opening diffs, which isn't something i've modified.15:58
jcsackettat least, i don't believe it is, and don't see the behavior on launchpad.dev with that branch.15:58
flacostejcsackett: you might ask abentley for help with that problem16:00
jcsackettflacoste: thanks.16:00
jcsackettabentley: i can't seem to open any branchmergeproposal page on qastaging--its OOPSing on trying to open the diff. thoughts?16:01
abentleyjcsackett, the librarian is FUBARed with old merge proprosals.  You could create a new one, but if you do, you'll need to manually run the scripts that update diffs.16:01
abentleyjcsackett, I recommend using staging instead.16:02
jcsackettabentley: dig. thanks.16:02
abentleyjcsackett, because the cron scripts are run automatically.16:02
jcsackettabentley: that makes sense.16:02
jcsackettgood to know it's an issue on qastaging, not with the code.16:02
flacosteabentley: what needs to be fixed on qastaging for this to work properly?16:04
abentleyflacoste, the librarian doesn't fall back to the production data correctly.16:05
flacosteabentley: do we have a RT for that?16:05
flacosteare the losa aware of this problem16:05
flacoste?16:05
abentleyflacoste, I don't know, other people discovered this problem.16:06
abentleyflacoste, I just saw it discussed on IRC.16:06
flacosteabentley: do you remember who was discussing it?16:07
abentleyflacoste, Sorry, no.  It was a while ago.16:07
flacosteok, i'll investigate16:07
=== leonardr-afk is now known as leonardr
benjiare LEPs meant to be kept up to date after they're implmented or are they simply historical?16:11
flacostebenji: historical16:18
benjicool, thanks16:18
=== beuno is now known as beuno-lunch
=== Ursinha is now known as Ursinha-lunch
=== salgado-lunch is now known as salgado
=== deryck[lunch] is now known as deryck
=== al-maisan is now known as almaisan-away
=== benji is now known as benji-lunch
rockstargary_poster, ping17:43
gary_posterrockstar, pong, though I was seconds away from announcing lunchtime :-)17:43
rockstargary_poster, just wondering where your Tarmac mp went.17:43
gary_posterrockstar: oh, thanks for following up!  I meant it to go to the lp fork, so I deleted the oe to trunk.  sorry for the noise17:44
gary_posterone17:44
rockstargary_poster, does the bug not affect my upstream?17:44
gary_posterno rockstar17:44
rockstargary_poster, ah, okay.  It looked like a pretty scary bug, so I was concerned.17:45
gary_posteryeah, it was interesting rockstar :-)17:45
rockstargary_poster, thanks.  That's one less thing off my actionable list.17:45
gary_postercool, np17:45
=== gary_poster is now known as gary-lunch
rockstarderyck, are you a good person to talk to about lazr-js stuff in Launchpad right now?18:18
rockstarBasically, when I take an axe to lazr-js, whose life am I making more difficult?18:18
=== Ursinha-lunch is now known as Ursinha
deryckrockstar: I'm probably the best one to do that with, yes.18:25
rockstarderyck, okay.  I don't think start of it will affect you too much, as the combo loader will get pulled out first, and you don't use that anyway.18:27
rockstarderyck, but the build system will have to become part of Launchpad soon.18:27
deryckah, ok18:27
=== benji-lunch is now known as benji
deryckrockstar: sorry, internets are flaky in AL when it storms. ;)18:39
=== beuno-lunch is now known as beuno
=== gary-lunch is now known as gary_poster
lifelessflacoste: what did you think of my triage mail ?19:52
lifelessflacoste: also I've forgotten the thing I was to mail you and jml about for consideration19:53
flacostelifeless: i liked it very much! there are a few things i'd like to clarify, but overall i found it very clear19:55
lifelessawesome19:55
flacostelifeless: i don't remember what the other email should have been19:55
lifelesswhat would you like to clarify ?19:55
flacostein the triaging guidlines, you didn't specify the bucket to use19:56
flacostei think you did that on purpose19:56
flacostemaybe not19:56
lifelessyeah, it was19:56
flacosteyou only say 'in front'19:56
flacostelater than19:56
flacosteetc19:56
flacostei understand the intent, but i think to be practical, we need to be more explicit19:57
lifelessthe problem with saying 'bucket x' is that we then have a scale problem: a large number of bugs matching <that rule> will swell <that bucket> without swelling our engineering resources etc19:57
flacosteright19:57
flacostebut we only have buckets19:57
flacosteso 'in front' doesn't really mean anything19:57
lifelessI can expand on that19:58
lifeless(because it does mean something :))19:58
flacostei know it does :-)19:58
flacostebut what it means operationally isn't clear19:59
lifelessin that document we're saying that what we want is bugs that are less important than 'the least important in the high bucket' are low19:59
lifelessand that queue jumpers only are critical19:59
lifelessflacoste: so, we could do an experiment without an explicit rule->bucket mapping for 'high', and see if its hard for folk, or if the results after a week or two are inconsistent with what you'd like to have seen20:01
flacosteso a bug escalated by a stakeholder would be marked critical?20:01
lifelessflacoste: I think so, when we accept it.20:01
flacosteok20:01
flacostewe will need to change our DefinitionOfCritical20:01
flacostewell, rename it to DefitionOfAnIncident20:02
lifelessflacoste: I think we need to make the definitionofcritical more clearly talk about operational incidents vs code changes20:02
flacostebut i think that would be a good change20:02
flacosteagreed20:02
lifelesshah yes +120:02
lifelesspoolie and I had an interesting discussion about 'how many high bugs should we have'20:03
lifelesswe expect about 1000 bugs closed a year by maintenance team work20:04
lifelesstha suggests the critical backlog (https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=timeout,oops) to be cleared in ~ 3 months20:04
lifelessand after that ~ 500 bugs in high every 6 months20:05
lifelessits possible that having 700 bugs in high (as we do) isn't a problem per se: thats a 9 month queue, yes, but in 9 months most bugs will still sort into the same bucket20:05
lifelessflacoste: what do you think?20:06
flacostelifeless: that's my analysis also20:07
flacosteand we should have a much shorter queue in a couple of months20:07
lifelessflacoste: we'll see some movement, yes.20:07
lifelessflacoste: I'd like to try tightening up the 'front' etc stuff in that section before we try making it more fixed20:07
lifelessflacoste: because by the july epic we'll be needing to promote medium bugs to high - the goal posts should be shifting20:08
lifelessflacoste: at the very least I'd like to do a re-triage of high bugs before writing declarative rules for what should be high20:09
lifeless(so that the rules can reasonably match :))20:09
flacostelifeless: doing it like in your proposal would remove the need for a 'escalated' tag -- which i was toying with to mark out the queue jumper in the High bucket20:09
lifelessflacoste: we may want such a tag for convenience in recall ('where are the escalated stakeholder bugs')20:10
flacosteright20:10
flacostebut we wouldn't need to hunt for it20:10
lifelessbut it wouldn't be needed for 'what do I need to work on next'20:10
flacostethey would sort at the top because of their critical priority20:10
lifelessright20:10
lifelessand the initial critical bucket if we implement my proposal will be ~ 3 months deep20:11
lifelesswhich is good20:11
lifelessnot brilliant20:11
lifelessbut a good starting point to clean up from20:11
flacostelifeless: OOPS, timeout and regression -> Critical ?20:11
lifeless+ escalted20:11
flacoste+ escalated20:11
flacosteworks for me though20:11
lifelesshttps://bugs.launchpad.net/launchpad-project/+bugs?field.tag=regression20:12
lifeless6 bugs20:12
flacoste172 oops20:13
flacosteand 58 timeout20:13
lifelessyeah20:13
lifelessflacoste: ok, so IIUC you're actually ok as-is now with a little tightening around the meaning of front etc - perhaps a use case.20:19
lifelessflacoste: were there other things in it that you'd like to clarify?20:19
flacostelifeless: no, that was it, really20:19
flacostelifeless: i found the whole rationale very clear20:20
lifelessexcellent20:20
=== almaisan-away is now known as al-maisan
=== henninge_ is now known as henninge
henningejcsackett: I subscribed you to a bug on staging where our QA is failing. I am investigating.20:28
henninges/on staging//20:28
jcsacketthenninge: thanks for the heads up.20:28
=== salgado is now known as salgado-afk
thumperarse20:47
* thumper wonders how to fix this20:47
lifelessflacoste: popping into the doctor with Lynne, back soon20:48
flacostelifeless: ttyl20:52
=== matsubara is now known as matsubara-afk
thumperflacoste: I have an issue with recipe builds20:53
flacostethumper: what's the issue?20:53
flacoste(/me is on a call)20:53
thumperflacoste: an early design decision was to have the recipe builds live under the recipe for the canonical url20:53
thumperhowever the recipe for the build is now optional20:53
thumperin order to maintain some traceability20:53
flacostemeaning that the recipe can be deleted?20:53
thumperwhich means we have some recipe builds without recipes20:53
thumperwhich are "dead"20:54
flacosteright20:54
thumperyes, the recipe can be deleted20:54
thumperbut the builds live on20:54
flacostecreate a graveyard parent?20:54
thumperwell...20:54
flacostein canonical_url, pseudo-code:20:54
thumperI wanted to have them hang off the ppa20:54
thumperlike ppa binary builds20:54
thumperhowever both the binary build and the recipe build have exported themselves20:55
thumperso in order to keep the wadl stable, we can't really change them20:55
flacostethumper: the URL isn't in the wadl20:55
thumperI'd ideally like to move both binary builds and recipe builds to live under the same URL20:55
thumperisn't it?20:55
thumperthat's interesting20:55
flacosteit's not20:55
thumper~user/+build/<buildfarmjobid>20:56
flacosteonly the schema is part of the wadl20:56
thumperhmm...20:56
thumperso this may well be fine then20:56
flacostethe url is part of the documentation20:56
thumperok20:56
thumperperhaps I may bug wgrant about this when he is up20:56
thumperjust to make sure I don't fubar anything important20:56
abentleyflacoste, wow, really?  We have a RESTful API that doesn't specify the URLs of anything?20:57
flacosteabentley: we don't because everything is discoverable20:57
flacostethrough introspection20:57
flacoste_link20:57
flacosteyou get a resource and then navigate the object graph20:58
thumperabentley: lucky us I guess :)20:58
flacosteor call methods and get back references20:58
flacosteonly the service root is a well-known name20:58
=== al-maisan is now known as almaisan-away
abentleythumper, kinda.  I'm not sure whether our javascript would handle URL changes gracefully.21:00
thumperabentley: what do you mean?21:00
abentleythumper, it doesn't use launchpadlib, so it may have hand-crafted URLs in places.21:01
thumperI don't think we have many of those...21:02
thumperI could be wrong21:02
abentleythumper, I'm changing merge proposals so that only recently-used proposal targets are suggested.  Where should I test it?  Test the widget?  Extract a vocabulary and test that?  Test the +register view?  The current tests are pagetests.21:04
thumperI think test the widget, or test the code that the widget uses21:05
flacosteabentley: we usually don't generate url directly in the JS21:10
flacostewell we shouldn't21:10
flacostethe LP.client is the launchpadlib analog21:11
flacosteor they are generated properly server-side21:11
elberryhello, I need some help installing launchpad in a VM.21:19
elberryAfter getting rocketfuel-setup, and running it. I'm prompted for my launchpad username. It doesn't seem to work though. Whenever I type in my lp username and password, I continue to get the password prompt.21:20
elberryand I'm unable to get past this point as simply hitting enter after being prompted for my username results in the default username being used.21:21
leonardrflacoste: i believe we do generate lots of urls in the js, because the ajax environment doesn't support navigation the way a custom client does21:21
flacosteleonardr: right, but usually either server-side, isn't?21:52
flacosteby or by using the json dump of the context21:52
gary_posterpoolie, lifeless, we'd like input from one or both of you on https://bugs.launchpad.net/launchpad/+bug/636193 .  Might be quick reply, might not.22:02
_mup_Bug #636193: feature flags need to self document <feature-flags> <lp-foundations> <Launchpad itself:Triaged by benji> < https://launchpad.net/bugs/636193 >22:02
wgrantthumper: It should be fine. Just change the PPA +build traversal to use PackageBuild instead of BinaryPackageBuild.22:12
thumperwgrant: actually we are considering /+build/<build-farm-job-id>22:12
thumperwgrant: for all build farm jobs22:12
thumperwgrant: which includes the translation jobs22:13
wgrantthumper: Translation jobs don't have an archive.22:13
thumperwgrant: so removing the inside part of binary package buids22:13
thumperwgrant: exactly22:13
thumperno archive22:13
wgrantI don't immensely like the sound of that.22:13
wgrantBut perhaps.22:13
thumperwgrant: that way we have a consistent url for all build farm jobs22:13
wgrantPackageBuilds are naturally contained within an archive. It makes sense to have the traversal under an archive.22:14
thumperwgrant: the question becomes "do we want consistency for all jobs" or "do we want the containment"22:15
thumperwgrant: since translation jobs don't have archives22:15
thumperwgrant: they are not currently traversable22:15
wgrantthumper: Jobs are not primarily jobs.22:15
thumperwgrant: but we may well be interested in the state or log files22:15
wgrantJobs exist to serve their assigned tasks.22:15
wgrantThe assigned task should come first, not the jobness.22:16
thumperwgrant: you could argue that the build jobs happened on builders, so that is the natural parent22:17
thumper(I'm not saying that I am arguing that)22:17
thumperabentley brought up the argument of "why treat translations differently?"22:17
wgrantthumper: Jobs don't have builders to start with, so that can't work.22:19
wgrantAnd I think translations jobs probably belong under a branch.22:19
thumpergood point22:19
thumperwgrant: do all binarypackagebuilds now have a buildfarmjob id ?22:22
thumperwgrant: through the packagebuild table?22:22
wgrantthumper: Yes.22:23
thumperwgrant: we could have uniqueness through either the package build id, or the build farm job id22:23
thumperwgrant: since there is already a buildfarmjobset that gets jobs through the id, and the specific job method22:23
thumperwgrant: I'd be inclined to use that22:23
wgrantProbably.22:24
gary_posterhey poolie.  We wanted your and/or lifeless' input on https://bugs.launchpad.net/launchpad/+bug/63619322:57
_mup_Bug #636193: feature flags need to self document <feature-flags> <lp-foundations> <Launchpad itself:Triaged by benji> < https://launchpad.net/bugs/636193 >22:57
gary_posterFor one, benji took that.  If you really want it, just let us know. :-)22:58
poolieyay benji!22:58
gary_posterlol :-)22:58
gary_posterFor another, we have some implementation questions.  benji put them on the bug, so you can see what the story is there22:58
pooliei'm going to the rally tomorrow so i'm not likely to work on it fro the next few weeks22:58
pooliei see22:58
pooliebut perhaps benji and i can pair at the thunderdome? that could be fun22:59
gary_posterthat could be fun, though we've been asked to bring these tasks to completion so feature flags can be declared "done"22:59
gary_posterthunderdome isn't too far away though :-)23:00
gary_posterif you can give us some quick direction, please do; otherwise, you can make that request/suggestion :-)23:00
pooliei will do that on the bug23:00
gary_postermany thanks23:00
poolieright now23:00
gary_postereven better ;-)23:00
pooliehe (or you) are welcome to give me a call any reasonable time to talk about things if you want to23:01
poolieeven if i'm not answering irc23:01
pooliebetween say 08:00 and 19:00 utc+1123:01
poolie(not next week of course)23:01
gary_posterawesome, thank you23:01
gary_posterright :-)23:01
lifelessgary_poster: I've commented on the bug FWIW23:02
gary_posteroh, lifeless, thanks!  sorry, I didn't see.  I still need to set up my mail rules in some new clever way :-/23:02
lifelessgary_poster: oh, I just did now when yo umentioned it23:02
gary_posterlol, oh ok, cool23:03
lifelessI has a -big- mail backlog23:03
gary_poster;-) gotcha23:03
lifeless10K messages over my holiday23:03
lifelessdown to 9K as of this morning23:03
gary_posterheh, congrats23:03
gary_posterneed to run.  night all23:04
=== gary_poster is now known as gary-afk
brycehWhen I run launchpad via 'make run', and then browse around, each page takes several minutes to load.  In the make run output I see it printing a huge number of apache log messages about transferring language files23:39
brycehe.g. GET /+icing/rev9918/yui/datatype/lang/datatype_zh-Hans.js23:39
lifelesstip should be better23:39
lifelessbe sure to do make jsbuild23:39
brycehlifeless, well I can't get tip because rocketfuel-get fails23:39
brycehon mailman23:39
lifelessbryceh: yeah, I linked the bug to you in this channel23:40
brycehlifeless, no, I looked at that bug but is seems to not be relevant.  The files they say are missing, are present, and the versions/names of packages it said to load are already present on the system.23:41
lifelessok23:42
lifelessnot sure then23:42
bacStevenK, thumper, mwhudson, wgrant, lifeless: you all around for a reviewers meeting?23:48
thumperI'm around23:48
bactop o' the hour?23:48
thumperaye23:48

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!