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

wgrantStevenK: rvb has two pending items on https://devpad.canonical.com/~lpqateam/qa_reports/deployment-db-stable.html -- could you please try to QA those?04:00
=== wgrant changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: - | Critical bugs:208 - 0:[######=_]:256
wallyworldwgrant: the work you are doing on product picker - have you made any changes to ProductVocabulary in vocabularies.py?04:03
LPCIBotProject windmill-db-devel build #364: STILL FAILING in 1 hr 7 min: https://lpci.wedontsleep.org/job/windmill-db-devel/364/04:03
wgrantwallyworld: Just http://paste.ubuntu.com/619573/04:04
wallyworldwgrant: thanks. i'm looking at altering the json so that exact matches (or matches above a certain ranking) are returned in a separate attribute so that if there are "too many" we can stil display the exact ones04:06
wallyworldbug 25528204:07
_mup_Bug #255282: project name picker search / vocabulary is hard/impossible to use (too many results on exact searches) <disclosure> <lp-registry> <project-picker> <projects> <Launchpad itself:Triaged by wallyworld> < https://launchpad.net/bugs/255282 >04:07
wgrantwallyworld: Probably better to limit?04:07
wgrantwallyworld: That's what that diff does.04:07
wgrantwallyworld: It ranks exact matches first, then by FTI, and limits as well.04:07
wallyworldwgrant: ah yes, i didn't see the limit04:08
wgrantLimiting in the current implementation is bad, because it ranks by displayname.04:08
wallyworldin that case, that bug is moot04:08
wgrantBut ordering by rank makes limiting sensible.04:08
wallyworldyes agreed04:08
wallyworldi spent some time cleaning up a fix previously landed which didn't work properly :-(04:09
wgrantOh?04:09
wallyworldthere was one recently to deal with the picker handling too many matches but it was all wrong (i didn't do the fix, just cleaned it up :-)04:10
wgrantAh, right, I remember that one.04:10
wallyworldwgrant: so i should assign that bug to you since your change deals with the problem04:11
wgrantwallyworld: Probably, yeah. I think this two line change solves most of the product picker problems.04:11
wallyworldok. you can link a few bugs to your branch :-)04:11
wgrantYup.04:12
wgrantThe prettification is a separate, more complicated beast.04:12
wgrantwallyworld: The link doesn't seem to do anything.04:13
wgrantThe one you just landed.04:13
wgrantAnd the spacing is off.04:13
wallyworldworks for me?04:13
wallyworldyour sure your browser is not blocking popups?04:14
wgrantWhich browser?04:14
wallyworldi use ff404:14
wgrantEw, popups?04:14
wallyworldwell the browser says its a popup but it's a window.open(...) call04:14
wallyworldand i have mine set up to open in a new tab04:15
wgrantHm, then it shouldn't be green.04:15
wgrantGreen means an inline thing.04:15
wallyworldwell, i was told to make it green04:15
wgranthref is not defined04:15
wgrantWhen I try it in Firefox 4.04:15
wallyworldgreen meaning "this link doesn't kill the current page"04:15
wallyworld?04:15
wallyworldi'll have another look, but it worked when I tested before ec2'ing04:16
wgrantHmm. Where is href defined?04:16
wgrantI think you might have meant data.alt_title_link04:16
wallyworldi need a bit more context. let me open the branch04:16
wgrantwindow.open(href) is failing, since href is not defined. In the 'if (data.alt_title)' branch.04:17
wgrantAnyway, it's all behind flags, so it doesn't really matter much right now.04:18
wallyworldthat sucks. yes, it is broken. not sure how i let that happen.04:18
wallyworldi'll fix04:18
wgrantThanks.04:18
wgrantWe should also huwshimi about the link style, I think.04:18
wgrantIt looks a bit odd being in the parenthesised section.04:19
wallyworldsure. i'll do what i am told :-) i wanted to make it something different but was told the styles are fixed and not easily changed04:19
wgrantWell, it's easier to change now it's there.04:20
wgrantThe hard bit is doen :)04:20
wallyworldyep04:20
wgrantwallyworld: Did you intend to reuse the commit message?04:31
wgrantI see you did that on lazr-js a few times too.04:31
wgrantIt's rather confusing.04:31
wallyworldprobably should have changed it04:31
wallyworlddidn't think you would be looking so closely at it04:32
wgrantI read most diffs, so I can keep track of what's going on and hit people when they introduce security holes :)04:33
wallyworldfair enough :-)04:36
LPCIBotProject windmill-devel build #171: STILL FAILING in 1 hr 10 min: https://lpci.wedontsleep.org/job/windmill-devel/171/04:36
LPCIBotProject windmill-devel build #172: STILL FAILING in 45 min: https://lpci.wedontsleep.org/job/windmill-devel/172/05:22
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
jtvWho's up for a pre-imp chat?07:47
LPCIBotProject windmill-db-devel build #365: STILL FAILING in 1 hr 9 min: https://lpci.wedontsleep.org/job/windmill-db-devel/365/07:52
jtvlifeless: got another fun problem that I'd love to discuss with you — creating multiple Jobs in one query.07:59
wgrantjtv: lifeless isn't here today.07:59
jtvAh blast07:59
wgrantjtv: But that's always fun.07:59
jtvYes07:59
wgrantI think you have to use strings.07:59
wgrantThat's what I do, at least.07:59
wgranteg. in PublishingSet.publishBinaries07:59
jtvYou mean, SQL strings?08:00
wgrantJa.08:00
jtvThat's not really the problem I'm pondering though.08:00
jtvI never really assumed that Storm would support what I wanted directly.  The real questions is how to make this work well API-wise.08:00
jtvIt seems easy: extend IJobSource with a createMultiple() that returns an iterable of job ids.08:01
jtvThen feed those into job-type-specific equivalents of createMultiple().08:01
jtvThe part I dislike is how some IJobSource-derivatives operate on Job, and classes implemented purely in that table; and others like to refer to other tables that in turn refer to Job.08:02
jtvSo IJobSource.createMultiple() would end up in job utilities that are expected to return something else than Job.08:03
lifelessI would like to delete 'Job'08:03
jtvYou're not here.08:03
jtvShoo.08:03
lifelessits a generally poor pattern for sql to do inheritance like that08:04
lifelessI pass through08:04
jtvNot using direct inheritance support in the DB does make things feel very awkward and old-fashioned,08:04
jtvalmost like inheritance in JavaScript.08:05
jtvMaybe we should've just used db-native table inheritance.  :)08:05
lifelesswell08:06
lifeless I would have done code inheritance but not db inheritance08:06
lifelessfor most jobs there isn't anything in common, but we've created a bottleneck as it stands08:07
wgrant:(08:13
lifelessby analogy, why don't we have a base *table* with the id column :>08:14
wgrantIndeed.08:14
wgrantAlso, why does the test suite and staging update take so long :(08:14
wgrantAnd why does something conflicting with db-devel have to have just landed :(08:15
jtvThe answer, my friend, is blowing in the wind.08:15
jtvlifeless: you're right though — design of our jobs is driven by commonality of contents, not commonality of purpose.08:16
jtvIt'd be nice if we could at least have a pattern along the lines of "put everything in the json metadata, but we can also duplicate data that needs to be searchable in proper columns."08:17
jtvI think I need to keep multi-job creation out of IJobSource because it isn't even a utility interface; it's an interface definition pur sang.08:19
adeuringgood morning08:22
jtvhi adeuring08:24
adeuringhi jtv!08:24
=== henninge changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: henninge | Critical bugs:208 - 0:[######=_]:256
rvbawgrant: Hi, I'm in the progress of QAing r10636.08:53
wgrantrvba: And r10641?08:54
rvbawgrant: yes, that too08:55
wgrantThanks.08:55
wgrantrvba: Have you talked to Stevenk?08:55
StevenKAt length.08:55
rvbawgrant: Yes I have ...08:55
mrevellHappy Monday08:56
wgrantHeh08:56
rvbaHello mrevell!08:56
LPCIBotProject windmill-devel build #173: STILL FAILING in 1 hr 10 min: https://lpci.wedontsleep.org/job/windmill-devel/173/09:11
=== jtv1 is now known as jtv
LPCIBotProject windmill-db-devel build #366: STILL FAILING in 1 hr 14 min: https://lpci.wedontsleep.org/job/windmill-db-devel/366/09:30
jelmerwgrant: hi10:04
wgrantjelmer: Hello.10:06
jelmerwgrant: you mentioned in #bzr you were QA'ing some of the bugs in my newer-bzr branch; are you still working on that and/or is there something I can help with?10:08
wgrantjelmer: I tried a few things on qastaging, but I'll probably need to do importds on staging tomorrow, since qastaging doesn't have any.10:09
wgrant(and it's not on staging yet)10:09
* wgrant -> food10:10
jelmerah, ok10:10
jelmerwgrant: if you need any help, you know where to find me :)10:15
=== almaisan-away is now known as al-maisan
wgrantjelmer: Yup, thanks.10:27
wgrantrvba: How's it going?10:54
rvbawgrant: good so far, I've found a bug.10:55
rvbawgrant: is this blocking you in any way?10:55
wgrantrvba: This is potentially disastrous.10:56
wgrantrvba: We need to merge db-stable into devel today.10:56
wgrantWhat's the bug?10:56
rvbawgrant: a simple UI bug.10:56
wgrantIn +initseries?10:56
rvbayes10:56
wgrantAh, OK, fine then.10:56
rvbaNothing disastrous :)10:56
wgrantI'd like to do the merge in the next 30 minutes.10:57
wgrantTo catch the next devel run.10:57
wgrantSo it'd be great if you could have the QA done by then.10:57
rvbaSince the changes in question are (like always) derivation related ... I suppose we could mark these bug QAok.10:58
rvbas/bug/bugs/10:58
wgrantWell, they also have the potential to break Ubuntu initialisation, but yeah, that's a while off.10:58
wgrantSo if you can't get them done soon, qa-ok it is.10:58
rvbawgrant: that's right, they have potential to break ubuntu init ... I think StevenK is checking these changes very seriously.10:59
rvbaStevenK: I suppose +initseries won't be used "for real" right now, the only dangerous thing is the initialisation of ubuntu. what is the conclusion of your conversation with Julian this morning about this? Will you check the ubuntu initialisation?11:02
rvbawgrant: We found another bug in initialisedistroseriesjob ... if you pass packagesets=None the job will fail because of the way parameters are passed inside a metadata attribute.11:12
rvbaIt will be very easy to fix but it's a stupid bug.11:13
rvbahttps://bugs.launchpad.net/launchpad/+bug/79343411:13
_mup_Bug #793434: Passing packagesets=None triggers an error when initializing a series. <derivation> <Launchpad itself:In Progress by rvb> < https://launchpad.net/bugs/793434 >11:13
rvbawgrant: I suppose I should wait for you to merge db-stable into devel and then fix this in devel ...?11:15
=== al-maisan is now known as almaisan-away
wgrantrvba: Probably, yes. We'll merge shortly, then be frozen until QA'd past the merge.11:18
wgrantWhich will be tomorrow some time.11:18
rvbaOk, I'll get the fix ready then.11:19
wgrantThanks.11:20
wgrantrvba: So, can we qa-ok them?11:31
rvbawgrant: I *just* did.11:31
rvbaRight in time I suppose ;)11:31
wgrantHeh.11:31
wgrantThanks.11:31
=== almaisan-away is now known as al-maisan
bigjoolsI wish make schema would do just exactly that, not a million other things12:25
stubbigjools: I use 'make -C database/schema'12:25
bigjoolsstub: do you know why the top-level Makefile's schema target depends on build then?12:27
* henninge lunches12:27
stubbigjools: Don't know. Technically that is correct I guess, since we need /bin/py built and stuff, so the problem is that 'make build' is too busy12:28
maxbAlso that 'make build && make schema' re-does bits of the build12:28
bigjoolsah, that Makefile uses bin/py ... :/12:30
stubprobably something to do with wadl depending on *.py... perhaps that should only rebuild if explicitly asked or if it is non-existent12:30
bigjoolsjeebus, the test failure attachments are huge now12:30
stubYer... all those librarian logs...12:31
bigjoolsand SQL now it seems12:31
stubthat I suspect are not reset between tests...12:31
wgrantHmm.12:32
wgrantschema doesn't need build.12:32
wgrantJust compile.12:32
wgrantWhich is much smaller, and runs OK with -j3.12:32
=== wgrant changed the topic of #launchpad-dev to: devel is release-critical until r13163 deployable | https://dev.launchpad.net/ | On call reviewer: henninge | Critical bugs:208 - 0:[######=_]:256
bigjoolsthat was slower than -j2 last time I checked12:34
wgrant... bah.12:34
stubWhat does 'orphaned' mean on the qa'd patch deployment report12:35
stub?12:35
wgrantstub: You used [testfix] when you shouldn't have.12:36
wgrantI decided it was safe to deploy, since it passed buildbot and seems harmless.12:36
wgrantSo it is in devel now.12:36
wgrantstaging seems happy enough, so if it's not OK please yell really really soon.12:39
stubThat branch lifelesslanded would be qa-untestable anyway. Nothing is using the new table yet, so the fallout would be in related areas that don't cope with the triggers.12:44
wgrantstub: Yep.12:51
bigjoolshave we got a run_jobs.py cronned in on staging?12:56
jtvhi henninge!  Can I trouble you for a review?  https://code.launchpad.net/~jtv/launchpad/db-bug-793382/+merge/6354513:05
* henninge tries not to let anything trouble him ...13:05
jtvIs that good or bad?  :)13:06
henningejtv: sure, I am happy to look at your review. ;-)13:06
jtv\o/13:06
henningegood for me, saves me the troubling.13:06
henninges/at your review/at your proposal/13:07
gmbflacoste: Can I get an RC for https://code.launchpad.net/~gmb/launchpad/bug-772609-hopefully-without-breaking-anything-this-time/+merge/63432? It should have landed Friday night but bounced due to a [testfix].13:10
wgrantgary_poster: Morning.13:16
gary_postermorning wgrant13:17
wgrantgary_poster: You're still planning to release the new subscriptions stuff during the downtime deploy this week?13:17
gary_posteror evening, sorry13:17
wgrant(the bugmail footer change is in devel now, so will be deployed unless it's reverted)13:17
wgrant(but we still have the strucsub listing regression, so I'm not sure)13:18
gary_posterwgrant, yes13:18
wgrantGreat.13:18
gary_poster(the structsub listing thing has branches to be addressed--that also rip out the feature flags--after at least a day or two of making sure that the subscriptions stuff is ok when exposed to everyone)13:19
wgrantOK. We've only had a few complaints about its absence, so I guess it's not too bad.13:20
gary_postercool13:20
wgrantDespite the mild security implications.13:20
gary_posterwgrant, security?  Do "other subscribers" affect visibility of private bugs?13:21
wgrantgary_poster: No. But people inevitably mistakenly put private info in public bugs, and want to know who it was emailed out to.13:22
wgrantHopefully that's less common now.13:22
gary_posterah, k.13:22
wgrantgmb: Hmm, I'm not sure who can grant r-c these days. Since there's no RM...13:23
gmbHmm.13:23
gmbTraditionally it was flacoste, lifeless or <RM>. So I guess we have to wait on one of the other two. Or maybe gary_poster can sign off on it.13:24
wgrantThis seems pretty clearly necessary and really wants to land in the next 3 hours, or I will be sad tomorrow.13:24
gmbYes.13:24
* gary_poster has vague memories of team leads having privs like this?13:24
wgrantIt hasn't been used since the RM position was abolished,13:25
gmbgary_poster: Let's say that your memories are right :)13:25
wgrantHeh.13:25
gary_poster:-)13:25
stubBecause we are minimizing the stuff that *has* to rollout during downtime deployment. Does this come with a db patch?13:25
gary_postergmb, ok, I'll go fiddle with the MP then13:25
gmbstub: No.13:25
* gary_poster waits...13:25
wgrantstub: Yeah, this is the issue with deploying features at the same time.13:25
wgrantWhich lifeless is vehemently against.13:26
gmbstub: But if stuff is rolled out without this, we will have breakages.13:26
gmbAnd that will make both wgrant and I go <sadface>13:26
wgrantThis release prep is chaotic enough already, let's not make it worse by delaying this.13:27
gary_posterstub, barring your quick strong objection, I'll approve13:27
stubSure. Might want to make that clear to Francis and/or robert then13:27
stubI don't object, not that it would matter if I did :)13:27
gary_posterheh, I dunno13:28
stubI would wonder if not landing it could be worked around by just disabling the feature using a flag, which also isn't clear from the MP13:28
gary_postergmb, rc approved with all the authority of my title behind it ;-)13:29
gmbCool, thanks.13:29
stubIts actually pretty awesome the last few releases haven't needed RC's...13:30
stubUsed to be a truck load of 'OMG its broken' fixes picked up by last minute QA13:30
wgrantWell, given that we deploy stuff every couple of days, there's less space for stuff to explode. It's been working pretty well!13:30
lifelessstub: wgrant: gary_poster: FWIW I think 'rc-approval' is fine from squad leads13:40
lifelessI'm not sure we -need- an rc-approval bit other than 'this has to be landed to make the downtime safe'13:41
gary_postercool, thanks lifeless13:41
gary_posterand agreed13:41
gary_postera team review approval seems pretty good to me13:41
lifelessthis is fixing the anonymous viewing of bug pages right ?13:41
lifelessgary_poster: re: releasing the new subscription stuff - thats slated for Monday right ?13:42
wgrantIt has to be Thursday, I think :/13:42
wgrantThe bugmail footer change is not flagged.13:42
lifelesswhy ?13:42
wgrantSo it will be deployed on Thursday.13:42
wgrantUnless that page works for everyone?13:42
gary_posterlifeless, correct.  we had the flag discussion on the bug tracker, I think13:42
lifelessI think we should wait for an hour or two after the deploy before setting the flag13:43
lifelessor monday per gary_poster's comment just now ;) \o/13:43
gary_posterno no13:43
gary_posterI was agreeing with wgrant13:43
lifelessok13:43
gary_posterwe can wait, but then there will be a couple of hours in which the links will point to a page without valuable info13:43
gary_posterpage will appear13:44
lifelesssure13:44
gary_posterbut no info13:44
lifelesslets just wait ~1 hour - enough time to see that nothing else is truely messed up13:44
gary_posterI'm fine with that13:44
lifelessif something is, we can open the flag wide and know its not the flags fault13:44
lifelessvice versa, if it looks good and we open the flag wide and it falls over, we know it probably is the flag.13:45
lifelessanyhoo... its now late, so gnight all :)13:45
gary_postersounds good lifeless.  'night13:45
=== wgrant changed the topic of #launchpad-dev to: devel is release-critical until r13164 deployable | https://dev.launchpad.net/ | On call reviewer: henninge | Critical bugs:208 - 0:[######=_]:256
wgrantNight lifeless.13:47
LPCIBotProject windmill-db-devel build #367: STILL FAILING in 1 hr 7 min: https://lpci.wedontsleep.org/job/windmill-db-devel/367/13:49
deryckadeuring, henninge -- ping for standup.14:00
LPCIBotProject windmill-devel build #174: STILL FAILING in 1 hr 7 min: https://lpci.wedontsleep.org/job/windmill-devel/174/14:01
henningederyck: yup14:01
henningeX crash. Unity?14:02
deryckreboot, brb14:08
gary_postermrevell, hi.  are you going to be around to give some UI opinions in the next half hour or so if I send you some screen shots?14:22
mrevellgary_poster, Yes, certainly.14:22
gary_postermrevell, thank you14:22
mrevellnp :)14:22
henningejtv: reviewed14:22
jtvThanks!14:22
jtvhenninge: apologizing for not finding anything wrong may be going a bit far :)14:23
henninge....14:23
henningeyeah, let me see if I can find something wrong, then14:24
jtvuh-oh14:24
henningejtv: the indentation of the parenthesis on line 319 and 332 looks strange ... but I may be wrong.14:27
henningesame on line 35014:27
henningejtv:  there you go! ;)14:27
jtvThank you, that's better.  :)14:27
jtvThe indentation looks a bit weird there because we rarely open a parenthesis on a line of its own.14:28
jtvIn this case though I do think it makes sense.14:28
henningeyeah, I guess I was wrong, then ...14:28
henningewell, actually I wasn't as we agree about the strangeness.14:29
jtvI'm not sure there's any perfect answer.14:29
jtvI generally like what I think is GNU style, with opening and closing braces identically indented.14:29
=== flacoste changed the topic of #launchpad-dev to: devel is release-critical until r13163 deployable | https://dev.launchpad.net/ | On call reviewer: henninge | Critical bugs:208 - 0:[######=_]:256
flacostegary_poster: you probably want to land your bug 792493 branch on devel once PQM gets out of RC-mode14:38
_mup_Bug #792493: Creating a structural subscription for a team with a preferredemail makes a mute link that oopses <oops> <Launchpad itself:Triaged by gary> < https://launchpad.net/bugs/792493 >14:38
flacostegary_poster: also, i downgraded the revision to deploy to 13163 since that's the one that include the merge, your other RC can be deploy nodowntime afterward14:39
flacosteso it's not a blocker per se i think14:39
wgrantIt is unless we want to delay the unflagging for hours and have bugmail links broken.14:39
wgrantWe cannot turn the flag on by default without 13164.14:40
gary_posterflacoste, what wgrant said.  My branch is not that important, but his is14:40
=== flacoste changed the topic of #launchpad-dev to: devel is release-critical until r13164 deployable | https://dev.launchpad.net/ | On call reviewer: henninge | Critical bugs:208 - 0:[######=_]:256
flacosteok, makes sense14:41
flacosteshouldn't be a big problem14:41
gary_postercool14:41
flacosteanybody took care of the conflicts yet?14:41
wgrantI can prepare a branch if you want, but it's pretty trivial.14:42
wgrantSince you can just take the files from devel.14:43
flacosteyeah, no problem14:43
wgrantThere's only three.14:43
wgrantflacoste: We'll be remerging db-stable tomorrow once devel reopens anyway.14:44
wgrantSo no need to reland it on devel.14:44
flacosteyep14:45
gary_postermrevell, mail sent (with two screenshots inline; hope that's not too annoying)14:45
mrevellThanks gary_poster, looking now. Not at all annoying :)14:46
gary_postercool :-)14:46
nigelbDoes running launchpad impair the ability for my apache to server php?15:00
wgrantnigelb: rocketfuel-setup installs apache2-mpm-worker, and PHP isn't threadsafe so it must be removed. But LP works fine with apache2-mpm-prefork instead of -worker, so you should be able to install libapache2-mod-php5 again.15:03
wgrant(it will remove -worker and install -prefork)15:03
nigelbwgrant: I tried that and it ended with an unsucessfull install, but its fine.  I'll just use nginx :)15:03
wgrantnigelb: What went wrong?15:05
wgrantI've done it in the past.15:05
LPCIBotProject windmill-devel build #175: STILL FAILING in 1 hr 9 min: https://lpci.wedontsleep.org/job/windmill-devel/175/15:10
nigelbwgrant: dpkg failures15:14
wgrantnigelb: Huh.15:24
flacostejelmer: were you able to QA the bzr upgrade?15:41
deryckhenninge, I see you saw I marked bug 410864 as related.  I agree it looked like a dupe too...15:47
_mup_Bug #410864: 'choose a source package' suggests undefined when search has too many results <qa-ok> <Launchpad itself:Fix Committed by henninge> < https://launchpad.net/bugs/410864 >15:47
deryckhenninge, but I thought I'd be cautious and leave it separate since the widget was used differently.15:48
henningederyck: argh!15:48
henningederyck: I just read the bug properly. It is not the same bug and it is not fixed.15:49
henningeActually, I had wondered about what is described there while fixing the bug.15:49
deryckhenninge, I walked through the steps in the bug on qastaging and had a nice list of packages to choose from.  over 35 steps, IIRC.15:50
deryck35 steps in the results picker, I mean15:51
* henninge has to try this now15:51
=== salgado is now known as salgado-lunch
henningederyck: :(16:01
deryckWhy the frown?16:01
henningederyck: qa-bad16:01
deryckah sadness indeed.  How is it bad?16:01
henningederyck: It broke the check for picker with search boxes.16:02
deryckI don't get meaning of "the check for picker with search boxes"16:02
henningehm16:02
deryckhenninge, how is it broken?  Sorry to be dumb.16:02
henningeI just got a result box with 220 batches.16:03
henningederyck: https://bugs.qastaging.launchpad.net/ubuntu/+source/linux/+bug/68739216:03
_mup_Bug #687392: Kernel panic with 2.6.32-26 security upgrade <Linux:Confirmed> <linux (Ubuntu):Incomplete> < https://launchpad.net/bugs/687392 >16:03
deryckheh a ha!16:03
henningederyck: edit "Linux" and enter "linux" into the search box.16:04
deryckI see it now.16:04
deryckonly 220 pages! :)16:04
henningederyck: Unfortunately I have to leave really soon and have no time to fix or rollback.16:05
deryckhenninge, so depending on where we are in the qa process, i.e. if qa-ok revisions ahead of you, which is likely.  I'd still leave it qa ok and do a follow on fix....16:05
deryckhenninge, it's a corner case that this many results will turn up normally.  and ugly, big corner case.  but at least the inital bug is fixed and the picker is usable...16:06
deryckif ugly.16:06
henningeoookaaay16:06
deryckhenninge, so either constrain the widget width, or limit the number of pages we show.  is anything beyond 40-50 pages useful?16:07
henningederyck: the limit is 2016:07
henningederyck: I removed it for Robert's special case but unfortunately it leaked into other cases it seems.16:07
deryckhenninge, right, but you could only display 20 and not limit on 20.16:08
henningederyck: I filed two other bugs for a proper fix.16:08
henningeI think they are linked from my mp?16:08
henningederyck: I will fix this tomorrow and maybe include a fix for bug 410864.16:09
_mup_Bug #410864: 'choose a source package' suggests undefined when search has too many results <Launchpad itself:In Progress by henninge> < https://launchpad.net/bugs/410864 >16:09
deryckhenninge, great, thanks.16:10
deryckthough I'm still not clear why 410864 isn't fix since we just looked at 220 results on that page. ;)16:10
deryckbut we can talk about it tomorrow.16:10
sinzuiI am 2 hours into my day. I am already burned. No doubt because I worked 3 days to see progress.16:15
sinzui1. We do not need a special JS for linting/evaluating. I can make seed do it16:15
sinzui2. I can run YUI tests without firefox, or any browser, I do not require a database or the web server. The test runner still needs  xvfb,16:15
sinzuijcsackett: do you have time to talk?16:17
jcsackettsinzui: sure, but one moment. i need to reboot.16:18
jelmerflacoste: wgrant said we'd have to wait until staging gets updated as it has a importd we can use for testing16:20
jcsackettsinzui: back, calling you now.16:21
flacostejelmer: don't we have a bazaar.qastaging ? i'm sure we can test at least basic bzr functionality there16:22
jelmerflacoste: the basic bzr functionality we can test there - and that works, but all the bugs associated with my branch require running of a importd with the new code16:23
flacostejelmer: staging is running 10647 and you require 10649 right?16:24
jelmerflacoste: what branch are those revno's for?16:27
flacostejelmer: db-stable, that's what staging runs, i see that your stable landing was merged on db-stable at 1064916:28
jelmer(on another note, why are there 5 people with recipes that build lp:~launchpad-pqm/launchpad/stable)16:28
jelmerflacoste: ah, yep16:29
flacostejelmer: recipe: i hav eno idea16:30
flacostepeople trying to autobuild launchpad .deb?16:30
maxbOh dear. That's an impressive lack of clue16:31
bigjoolsyet hilarious at the same time16:31
jelmerI guess.. none of them merge in any packaging branches though, so that's doomed to fail16:31
maxbIt's about as ridiculous as requesting subversion code imports from bazaar.launchpad.net, which people also seem to do from time to time16:32
jelmermaxb: we should fix that by just letting them enter a URL and Doing The Right Thing16:33
maxbBut, what is The Right Thing?16:33
maxbIt's not even clear what they are hoping to achieve16:34
jelmermaxb: In some cases I guess a mirror (if it's a bzr branch elsewhere), if they're trying to import from bazaar.launchpad.ent we should tell them to "bzr branch && hack && bzr push"16:34
jelmermaxb: I think they're looking for the fork button16:34
maxbCould be16:35
maxbOn a related note, we could use a "Do you really want to be doing this?" banner for people entering questions on Launchpad itself16:36
maxbBack on the code import issue, I think https://code.launchpad.net/+code-imports/+new is wrong to default to Subversion16:37
maxbIt should default to nothing and force you to pick one16:37
jelmermaxb: we should not require you to specify the VCS at all, just let you enter a URL16:37
maxbHm. I am of the opinion that there is no point writing the code to do that, because if a user can't even figure out what VCS they are importing from, they don't deserve an import :-)16:38
flacostemaxb: that's a little harsh :-)16:39
flacostemaybe they onbly care about bzr16:39
flacostewhatever, just give me a bzr repo16:39
flacoste!16:39
jelmermaxb: *I* would appreciate having to click one radio button less for each import16:40
jelmerif we have the data we shouldn't bother to ask our users for it16:40
=== al-maisan is now known as almaisan-away
flacostejelmer: staging is updating now, should be available in ~90 minutes16:49
jelmerflacoste: great - thanks :)16:52
rvbabac: Hi ... I'm not sure I should have done it this way, but I created another branch ("a rebased" version of the branch you've been reviewing) so that it targets devel.17:02
rvbabac: sorry to bother you with that, but perhaps you could review/approve it ...?17:02
rvbahttps://code.launchpad.net/~rvb/launchpad/init-multiple-parents-bug-777120-devel/+merge/6357217:02
=== deryck is now known as deryck[lunch]
=== matsubara is now known as matsubara-lunch
=== salgado-lunch is now known as salgado
=== deryck[lunch] is now known as deryck
=== matsubara-lunch is now known as matsubara
LPCIBotProject windmill-devel build #176: STILL FAILING in 1 hr 17 min: https://lpci.wedontsleep.org/job/windmill-devel/176/18:33
=== henninge changed the topic of #launchpad-dev to: devel is release-critical until r13164 deployable | https://dev.launchpad.net/ | On call reviewer: - | Critical bugs:208 - 0:[######=_]:256
timrcwgrant, I might  be seeing a regression of https://bugs.launchpad.net/launchpad/+bug/75064019:29
_mup_Bug #750640: If the source version differs from the binary version, it is not specified in the Package index for that binary <oem-services> <qa-ok> <soyuz-publish> <Launchpad itself:Fix Released by wgrant> < https://launchpad.net/bugs/750640 >19:29
maxbtimrc: It's 4:30am in Melbourne...19:30
timrcmaxb, $1 USD says he has logging enabled and will see it when he wakes up19:31
timrcwgrant, nm, I think I misread comment #219:51
lifelessmorning y'all20:30
=== bigjools-afk is now known as bigjools
lifelessflacoste: yo21:12
flacostehi lifeless21:13
mwhudsonjelmer: does launchpad no longer depend on pysvn?21:16
mwhudson(i guess cscvs still does)21:16
=== lifeless changed the topic of #launchpad-dev to: Performance Tuesday! | devel is release-critical until r13164 deployable | https://dev.launchpad.net/ | On call reviewer: - | Critical bugs:208 - 0:[######=_]:256
mwhudsonhm, it seems the update of sourcedeps.cache depends on dictionary order21:28
abentleymwhudson: yes, that's likely.21:28
mwhudsonshall i file a bug?21:29
abentleymwhudson: But I thought it would only perform the update if the data had changed.21:29
mwhudsonah21:29
abentleymwhudson: I experienced a bug this morning where it said the cache had been updated, so I'm now no longer sure that's right.21:30
mwhudsoni think that's what it just did to me21:30
abentleymwhudson: Okay, what did it do?  Are the cache files the same data in different orders?21:31
mwhudsonabentley: it looks at a quick glance as if it will update the cache if any branches were updated, not if any branch ended up with a different tip than that in the cache21:32
mwhudsonso i think if i revert and run update-sourcecode again, it will not be changed21:32
mwhudsonabentley: yeah21:32
abentleymwhudson: okay, that's useful.21:33
jelmermwhudson: hi21:33
jelmermwhudson: cscvs indeed still does, and there codehosting code also still uses oo_svn21:33
mwhudsonjelmer: ah well21:33
mwhudsoni guess hypothetically we could kill off the remaining cscvs-svn imports and then delete all the svn code from cscvs21:34
mwhudsonbut well, fails to beat the effort/reward test i guess21:35
jelmermwhudson: yeah, probably21:35
jelmermwhudson: I was going to ask the other day - the codeimport workers don't have direct/API access to the database, right?21:35
mwhudsonjelmer: no21:36
mwhudsonthe machines still do, for sodding oops-prune21:36
jelmermwhudson: I was looking at bug 432217, I guess that's a fair bit harder in that case21:37
_mup_Bug #432217: Import branches have auto-format upgrade disabled <code-import> <lp-code> <tech-debt> <Launchpad itself:In Progress by jelmer> < https://launchpad.net/bugs/432217 >21:37
jelmermwhudson: it seems though, that at least for bzr-{git,svn,hg} branches we could just nuke the branch if it's in an old format rather than bothering with upgrading?21:38
mwhudsonjelmer: yes, for deterministic imports that's totally the way to go21:38
mwhudsonfor the others, ugh, i guess there's no good answer really21:38
mwhudsonjelmer: we can give the machines access to the db again if we want, but i've always regarded them as a bit more likely to get compromised than the average machine21:39
jelmerthe code has a FIXME saying a upgrade job should be created, though I wonder how that would have to happen (XML-RPC request??)21:39
mwhudson(i seem to be more paranoid than most people about this)21:39
mwhudsonuhh21:39
mwhudsona branchupgradejob wouldn't help21:39
mwhudsonbecause of the storage of the import branches on escudero21:39
mwhudsonso if you upgraded the branch on crowberry, it would just get downgraded again the next time the import puller ran21:40
jelmerah, urgh21:40
mwhudson(the real answer to this side of things is to have the code import worker have some kind of token-mediated access to crowberry that allows write access to exactly one branch)21:40
mwhudsoni think on staging the code import worker can write to any branch on the codehost in effect21:41
mwhudsonthis doesn't seem like a good idea for prod :)21:41
jelmer:)21:43
jelmerI'll have a look at nuking the bzr-{hg,svn,git} branches; we can nuke and recreate cscvs-based svn import branches21:44
jelmerthat just leaves CVS imports21:44
jcsackettsinzui: did you ping me earlier?21:45
sinzuijcsackett: no, but a kitten may have. She slept on my keyboard during lunch21:46
jcsackettsinzui: dig. the cats are after your computer again.21:46
sinzuijcsackett: I just approved your yui test branch21:50
mwhudsonjelmer: wow the ratio of failed to running says something here: https://lpstats.canonical.com/graphs/CodeImportsCVSBreakdown/21:50
jcsackettsinzui: cool, thanks.21:53
jelmergarr, I thought my internet connection was just bad today22:07
jelmermwhudson: oh, wow (those colors are.. unusual)22:08
mwhudsonjelmer: sysadmins are not visual designers, usually :p22:08
jelmermwhudson: while you're here.. am I correct in thinking that the code import workers don't have any access to e.g. information on what the development focus for a project is?22:12
mwhudsonjelmer: yes, that's true too22:12
mwhudsonit's not hard to arrange to pass more information along though22:12
mwhudson(are you thinking about stacking?)22:12
jelmermwhudson: yes, exactly22:12
cr3if I add a new method to the restful api, do I need to add @operation_for_version("beta")?22:16
* timrc would think "devel" would be a more appropriate version *duck*22:18
lifelessdevel22:19
cr3timrc: I'm thinking "not backward compatible == beta", "backward compatible == devel"22:20
lifelessbeta *was* a beta22:20
lifelessit is not now22:20
lifelessignore it22:20
lifelessyou want for devel22:20
lifelessmwhudson: jelmer: those machines are not getting db access.22:21
timrccan the suggestion that gets spit at you if you do not include @operation_for_version be changed to suggest 'devel' rather than 'beta'? I stumbled upon this recently as well and some head scratching ensued22:21
mwhudsonah, now we have someone who is as paranoid as me apparently22:21
lifelesstimrc: patches gratefully...22:21
timrclifeless, =)22:22
jelmerlifeless: fair enough22:22
mwhudsonlifeless: has the access they have for oops-prune been removed then?22:23
timrclifeless, hey while you're here... I did not really have a reviewer for https://code.launchpad.net/~timrchavez/launchpad/set_ppa_private_from_api_724740-2 -- I discussed some w/ bigjools, though... should I just add the next on call reviewer to the merge proposal ?22:23
jelmercan it be that launchpad is firewalled by sourceforge?22:24
mwhudsonjelmer: in the past they've been happy with us doing what we do, but it's possible for sure22:25
lifelessmwhudson: I thought that went *out* to them / was a different DB22:26
lifelesstimrc: ping them here if you can22:26
lifelessjelmer: mwhudson: so its not for security I don't want the importds talking to the DB22:27
lifelessrather its that long running processes with DB access have a history of terrible transaction handling.22:27
lifelessthese things have no call to know about our DB schema.22:27
lifelessand if they did, downtime deploys would get that much harder.22:27
flacosteafter merging devel i have an error with sprite generation:22:33
flacosteKeyError: u'../images/mute.png'22:33
flacosteany ideas?22:33
flacosteok, make clean solved the issue22:35
LPCIBotProject windmill-db-devel build #368: STILL FAILING in 1 hr 7 min: https://lpci.wedontsleep.org/job/windmill-db-devel/368/22:46
=== matsubara is now known as matsubara-afk
lifelessback23:02
thumperwhat's with all the failing import emails?23:39
thumperthere seems to be an uncharacteristically large number of them23:40
mwhudsonthumper: maybe this is related? <jelmer> can it be that launchpad is firewalled by sourceforge?23:40
thumperhaha23:40
thumpermaybe23:40

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