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

=== StevenK changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: StevenK | Critical bugtasks: 277
* wallyworld types s/launchpad.See/launchpad.LimitedView/g00:02
StevenK /g is probably not necessary00:02
wallyworldbut harmless none the less00:03
wallyworldit was figurative anyway - my ide is doing it :-P00:03
StevenKwallyworld: :%s/\(launchpad.\)See/\1LimitedView/00:03
wallyworldnow you're just showing off00:04
lifelessdon't you use an IDE ?00:04
lifeless;)00:04
wallyworldyes, but i don't do regex search and replace very often00:05
mwhudsonbzr ls -0VRk file | xargs -o sed -i -e 's/00:07
mwhudsonthe fact that i can type that without thinking much is a little scary00:07
mwhudson(should be -0)00:08
wgrantbzr sed!00:08
mwhudsonyes... i think00:09
wallyworldi like my IDE because for non-trivial search and replace you can preview the changes and veto any matches which should not be included00:11
wgrantsed, diff...00:12
wgrantdone00:12
wallyworldsure, but text based (harder to read the output) and not nearly as user friendly00:13
wallyworldie can you click through from a match to the source code00:14
poolielifeless, fwiw i think you should just capture all traceback00:33
wgrantlifeless: 20 frames isn't many00:34
wgrant(thanks to TAL)00:34
lifelesswhats a better number ?00:35
poolie60?00:35
poolie50?00:35
StevenKlifeless: So what about ++profile++sqltrace ?00:37
lifelesswhat about it ?00:38
StevenKlifeless: Oh, you want to do it all the time?00:39
lifelessin the query log in OOPSes, yes00:39
StevenKOh, and do the work in the OOPS handler?00:41
lifelessthe timeline, yes.00:41
lifelessoops handler is too late00:41
lifelessI found a methodology error too00:44
lifelesstimeit python API00:44
lifeless!= timeit CLI behaviour00:44
lifelessStevenK: this doesn't stop the sqltrace profiler beind useful, it just means we have equivalent data whenever we get an OOPS00:46
lifelessit does point the way at possibly simplifying the profiler implementation00:46
huwshimiI assume I can ignore these errors and do a lp-land? http://paste.ubuntu.com/739827/00:55
StevenKhuwshimi: That's odd. That's local, or via ec2?00:56
huwshimiStevenK: ec2. from yesterday afternoon00:56
StevenKWow.00:56
huwshimiStevenK: Did I break the world?00:58
StevenKhuwshimi: I just find it surprising that something else is listening on 2121 on an ec2 instance while the test is running00:59
wgrantStevenK: Some things listen on random ports.01:01
wgranteg. the librarian01:01
huwshimiStevenK: So I can ignore it then?01:03
hloeungpoolie, jelmer: ok, packages are there now. Where would you like me to install / update?01:12
wgranthloeung: clementine01:13
wgrant(the guest on concordia)01:13
hloeunghmm, it seems I don't have SSH access into clementine01:14
hloeungnevermind, found another way around that01:14
wgrantCorrect.01:14
wgrantIt's a guest that is torn down every build.01:14
wgrantYou need to update its image.01:15
hloeungah right01:15
lifelessStevenK: oh hai ;) https://code.launchpad.net/~lifeless/python-oops-tools/bug-890001/+merge/8233401:29
lifelessStevenK: (diff coming)01:29
benjihi lifeless; if I put a fastdowntime deployment on the deployment page would you (or stub) have time to do it in the next few hours?01:31
lifelessbenji: no; we only have one window a day for fdt01:32
lifelessbenji: (because they are downtime)01:32
StevenKlifeless: r=me01:33
benjilifeless: darn, well that's understandable, I'll put it up during my day tomorrow to get in line for the next one; thanks01:33
lifelessbenji: they are also done by losa FWIW. Perhaps you mean a live schema patch ?01:33
lifelessbenji: next one is in ~ 6 hours01:33
StevenKWhich patches are unapplied?01:33
benjilifeless: oh right, I think stub said that this (adding a table) was doable live01:34
lifelessbenji: does the table have FK references ?01:34
* benji tries to remember01:34
lifelessif it does, it requires downtime.01:34
wallyworldsinzui: if you are still around - do you have any objection to me adding isBugSupervisor(obj) and isSecurityContact(obj) to IPersonRoles? to compliment isOwner(obj) and isDriver(obj)01:35
benjilifeless: yep it does; fastdowntime it is01:36
wallyworldsinzui:  or do we want to avoid referencing bug model artifacts from registry01:36
wallyworldi can see why we would not want to do that01:36
wgrantbenji: So, request it for today's window.01:40
wgrantbenji: Since we can't do it tomorrow.01:41
sinzuiwallyworld, go ahead. They are consistent. <- StevenK wallyworld may be doing some of the role checking you are working on01:41
wgrant(there is an extended outage for a slony upgrade)01:41
StevenKI wonder if my db-devel patch has hit prod01:41
wgrantStevenK: No01:41
wgrantStevenK: is that before benji's?01:41
wallyworldsinzui: thanks. i thought they were consistent but wasn't sure if we considered registry a lower layer than bugs, hence the question about referencing01:42
StevenKwgrant: Let me check01:42
wgrantbenji: I also added your patch number to the allocation listing this morning, since it seems you missed that.01:42
* wgrant lunches.01:43
StevenKwgrant: db-stable r1114001:43
sinzuiwallyworld, registry is considered the lowest and only required app.01:43
wgrantStevenK: That's unfortunate.01:43
StevenKwgrant: Oh? Why?01:43
wgrantBecause we can't do benji's tonight.01:43
wgrantAnd I have two landing now.01:44
wgrantAnd tomorrow's window is used.01:44
wgrantWell, only one of my two is landing now.01:44
StevenKLean on lifeless for more than one patch a day?01:44
wgrantBut the other is ready, blocked on the first being deployed.01:44
wgrantWhich probably can't happen until Wed.01:44
wallyworldsinzui: yes. so the fact that registry (PersonRoles) would now reference interfaces declared in the bugs layer may be considered "dirty"01:44
StevenKFDT is not ... fast01:44
wgrantwallyworld: Dirty but sometimes unavoidable.01:45
wgrantwallyworld: And bugsupervisor is registry anyway.01:45
StevenKwallyworld: That's a layering violation01:45
sinzuiwallyworld, yes it is, but it will not be. forever. at least not for security...it will go to registry because many artefacts could be labeled security01:45
wallyworldwgrant: IHasBugSupervisor is bugs01:45
StevenKMove it down, I'd suggest01:46
StevenKIn a seperate branch01:46
StevenKsinzui: When were you thinking of chatting? I'll be lunching soon01:46
wallyworldStevenK: yes, that was the basis of my question. i didn't like the layering violation01:46
wallyworldi think the consensus is just do it now and fix the layering later01:47
StevenKFixing the layering should be very quick01:47
StevenKAnd I don't like leaving tech debt around if it can be helped.01:48
StevenKWe already have too much!01:48
wallyworldyes, possibly touch many files though01:48
wallyworldi won't leave it hanging around01:48
StevenKIt can be done via regex ... :-P01:49
lifelessits questionable to say its bugs, given the upcoming issuetracker concept :)01:52
StevenKForbiddenAttribute: ('bug_supervisor', <lp.registry.model.distributionsourcepackage.DistributionSourcePackage object at 0xcbf0290>)01:55
StevenK:-(01:55
sinzuiStevenK, wallyworld. we want the DSP to have a bug supervisor. It is not in scope (yet) for disclosure01:58
sinzuisee bug 191809 and bug 61921801:59
_mup_Bug #191809: A DistributionSourcePackage needs a bug supervisor role to control permissions <lp-bugs> <search> <ubuntu-qa> <Launchpad itself:Triaged> < https://launchpad.net/bugs/191809 >01:59
_mup_Bug #619218: It isn't possible to set the bug supervisor for a source package <lp-bugs> <Launchpad itself:Triaged> < https://launchpad.net/bugs/619218 >01:59
huwshimilifeless: If you get the chance at some stage I would like to get another review of this: https://code.launchpad.net/~huwshimi/launchpad/avatars-everywhere-712894/+merge/8143002:00
sinzuiwell I say the later is a dupe of the former bug02:00
wallyworldnot a recent problem then02:01
sinzuino. dsp could have a field that returns the distro bug supervisor so that that the interface is met02:02
lifelesswgrant: remember that oops that was breaking staging amqp oops loading02:05
wallyworldyes it could02:05
lifelesswgrant: anyhow, its hilarious02:22
lifelessStevenK: hi. Diff coming soon - https://code.launchpad.net/~lifeless/python-oops-tools/bug-889982/+merge/8233702:23
lifelesswgrant: this was the cause - https://bugs.launchpad.net/launchpad/+bug/89095102:25
_mup_Bug #890951: bad oops prefix in staging translations-export-to-branch <oops> <Launchpad itself:Triaged> < https://launchpad.net/bugs/890951 >02:25
lifelesssinzui: what was the subject of the mail that kicked off the thread about arbitrarty cocs for teams ?02:42
lifelesssinzui: I had some thoughts but have lost the thread02:42
StevenKsinzui: I'm just confused that IHasBugSupervisor.providedBy(self.pillar) is returning True for DSPs02:43
sinzuilifeless, Proposed team agreements feature02:43
lifelesscool02:43
lifelessI'm aware this is a community driven thing02:43
lifelessI thing there is a good inflection point in LP to push most of it out of LP entirely - so they can do whatever they want as a django app or similar.02:44
lifelesss/thing/think/02:44
StevenKNow I'm being mocked.02:44
lifelessI will mail my thoughts in in a bit.02:44
StevenKIn [3]: IHasBugSupervisor.providedBy(dsp)02:44
StevenKOut[3]: False02:44
lifelessStevenK: by me asking for reviews?02:44
StevenKlifeless: Certainly not!02:44
lifeless:)02:44
StevenKlifeless: I've approved your last one02:45
StevenKOH, it's the bloody view change02:49
lifelesspoolie: bug 885972 might be up your alley02:54
_mup_Bug #885972: raw_sendmail creates TimedActions with invalid detail <regression> <Launchpad itself:Triaged> < https://launchpad.net/bugs/885972 >02:54
sinzuitrying to see all of the disclosure feature is like looking into the face to Cthulhu; madness02:56
wgrantlifeless: Haha, handy.02:57
wgrantsinzui: Rather.03:00
wgrantIntertwined and partially invisible madness :(03:00
StevenK% uptime03:19
StevenK 14:19:32 up 14:07,  3 users,  load average: 31.39, 24.86, 12.6503:19
StevenKDear RabbitMQLayer, DIE03:19
lifelesswgrant: oh, you just read scrollback ?03:20
wgrantlifeless: Yes.03:21
* StevenK is slowly getting happier with this branch03:25
StevenK4 files changed, 53 insertions(+), 54 deletions(-)03:26
jtv1StevenK, wgrant: no joy from dogfood buildmaster.  :(03:40
wgrantWell, it's not running at the moment... that could be relevant.03:41
wgrantI wonder why not.03:41
* wgrant starts.03:41
wgrantIt is building stuff now.03:43
lifelesshmm03:45
lifelesswhat, if any, js library do we use in oops-tools, I wonder03:45
lifeless(I want expandable sections on the timeline)03:45
lifelessalso, I want a tool to report on out of date deps03:47
lifelessdoes setuptools/buildout perhaps know already ?03:47
lifelessStevenK: oh hai :) https://code.launchpad.net/~lifeless/python-oops-datedir-repo/timeline/+merge/8234403:48
StevenKsinzui: Can haz chat, if you're still around?03:49
StevenKlifeless: r=me03:51
jtv1StevenK, wgrant: builds are failing on dogfood, but I don't see anything explaining the failures.  Am I missing something, or did I simply break the build farm?03:53
=== jtv1 is now known as jtv
wgrantWhere are the failures?03:53
jtvhttps://dogfood.launchpad.net/~jtv/+archive/ppa/+packages?batch=15003:55
pooliehttps://dev.launchpad.net/EC2Test/Image we use an EBS instance too, right?03:56
StevenKWe do not.03:56
poolieno, sorry, instance storage?03:56
StevenKRight03:56
StevenKIt is not EBS-based.03:56
StevenKEr, backed03:56
poolieand 'large'03:57
StevenKI think it's xlarge03:57
StevenKIt's in the code anyway03:57
mwhudsonec2 test predates ebs backed images03:57
mwhudsoni think instance store makes more sense for ec2 test-ish ephemeral vms anyway03:58
poolieyeah04:00
pooliei may try actually changing it to put more on a ramdisk04:00
mwhudsonah yeah, that may be a win04:00
StevenKI'd like EBS-backed instances for Jenkins, only for the reason that we can start testing quicker if we have a seeded download-cache and such04:00
pooliewee04:00
mwhudsonthere are much more powerful instances now too, may be worth trying them out04:00
poolie23MB/s apt update04:00
mwhudson(partly the power is in multi-cores, which doesn't help so much of course)04:01
mwhudson"High-Memory Quadruple Extra Large" instances are really quite something04:01
poolieso apparently the local store is kinda slow04:02
pooliedon't have data04:02
pooliemay try it now while this is running04:02
mwhudsonebs is even slower :-)04:02
mwhudsonbut yes ramdisks do help afaik04:02
mwhudson"High-Memory Extra Large Instance" would almost certainly be better for us than basic extra large (fewer cores, but more 'compute units' per core)04:03
mwhudsoncheaper too04:03
mwhudsonmaybe "High-Memory Double Extra Large Instance" with everything stuffed onto a ramdisk would be fast enough that the extra cost is mediated?04:06
StevenKThat's c1.2xlarge?04:06
StevenKWe currently use c1.xlarge instances04:06
mwhudsonno, m2.xlarge or m2.2xlarge04:07
mwhudsondon't think c1.2xlarge is actually a thing?04:08
StevenKI was guessing04:08
mwhudsonheh :)04:08
mwhudsonthe names are hard to remember, there's almost a pattern04:08
jtvStevenK, wgrant: no logs of my build failures whatsoever afaict.  I think it's all broken.04:08
StevenKYes, almost.04:08
wgrantjtv: Indeed, it looks that way.04:09
jtv:-(04:09
wgrantDid you try it locally?04:09
jtvNo.04:09
StevenKstoreBuildInfo is now utterly fucked?04:09
StevenKOr is failure counting screwing us over?04:09
jtvOr log retrieval… who knows.04:09
wgrantThe builds dispatch fine.04:09
wgrantI saw logs.04:10
jtvFailure accounting will have seen some changes, I think.04:10
StevenKI saw logtails04:10
jtvYes, there were logs previously.04:10
StevenK*COUNTING*04:10
jtvAh.04:10
jtvFailure counting will have seen some changes, I think.04:10
jtvWith retries in particular, IIRC.04:11
jtvSome information or other from a previous failure now survives into a next dispatch, that previously didn't.04:11
pooliemwhudson, trying a tmpfs hack now04:12
mwhudsonpoolie: woo04:13
lifelesspoolie: will you look at that sendmail issue? [I d/c'd before apologies if you replied already]04:13
mwhudsonpoolie: i think i'll email launchpad-dev about trying m2.xlarge, do you want to follow up about tmpfss?04:13
StevenKlifeless: You need better internets04:13
lifelessStevenK: I know :(04:13
lifelessStevenK: https://code.launchpad.net/~lifeless/python-timeline/backtrace/+merge/8234804:14
pooliecat is sleeping on my mouse cord04:14
StevenKNo diff, no review.04:14
pooliemakes it hard04:14
StevenK:-P04:14
StevenKpoolie: Your mouse has a cord? :-P04:14
pooliethat may be my problem04:14
poolielifeless, are you talking about bug 88597204:15
_mup_Bug #885972: raw_sendmail creates TimedActions with invalid detail <oops-infrastructure> <regression> <Launchpad itself:Triaged> < https://launchpad.net/bugs/885972 >04:15
StevenKMy keyboard and mouse are cordless. It's quite nice.04:15
lifelesspoolie: yes04:15
lifelessStevenK: there is a diff04:15
lifeless:P04:15
jtvStevenK: don't rub it in—my wrists have been aching ever since bluetooth stopped working04:15
StevenKHaha04:16
jtv(*mostly* stopped working… it still works for some things)04:16
StevenKMine are abusing 2.4GHz04:16
lifelessStevenK: I'm sorry for muddling the LGPL change in there, I should have self-reviewed it separately; I claim tiredness.04:17
lifelessStevenK: it is a separate commit, you may be better clicking on the commits04:17
poolielifeless, i'll see what I can do04:18
* jtv goes for a little cry or food or something04:18
=== jtv is now known as jtv-afk
StevenKlifeless: I'm already trying to keep track of my own branch, there is six other branches you've tossed me over the course of the day, and sinzui has sent me a novel that I need to reply to. My brain, it is leaking out my ears.04:19
* StevenK stabs lifeless for the 1,400 lines.04:21
StevenK# The fifth element defaults to None:04:24
StevenKBruce Willis would not approve.04:24
lifelesspoolie: thanks04:25
lifelessStevenK: yeah, I know. Gotta love small reusable components!04:25
lifelessStevenK: don't worry, my next branch is on LP itself.04:27
StevenKlifeless: You don't specify 'v3' for LGPL in setup.py04:27
lifelessStevenK: you can't04:27
StevenKYou did for AGPL04:27
lifelessyes04:27
lifelesshttp://mail.python.org/pipermail/catalog-sig/2011-November/004028.html04:27
StevenKAnd you seem to repeat LGPL once too many in README04:27
lifelesshmm, let me see04:28
lifelessthats a nuisance, cause I've got that copied all over the place now.04:29
lifelessNice catch04:29
lifelessits in every darn little header too04:29
lifelessfuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu04:29
lifelessI'll just delete that last line.04:30
pooliemwhudson, really a one line patch? that's cool04:42
mwhudsonpoolie: it's two, it turns out04:42
mwhudsonbut yes04:42
mwhudsonvery easy04:42
pooliei get the chance to add better handling of instance creation errors04:42
poolieby printing the reason code04:42
poolieapparently they have sold out of computers04:43
mwhudsonheh04:45
lifelessyes we have no banaanas ?04:45
StevenKNo bananas today!04:45
pooliehttp://support.rightscale.com/06-FAQs/FAQ_0112_-_How_come_I_get_an_insufficient_capacity_error_when_launching_an_EC2_instance%3F04:46
mwhudsoni saw a fun fact a while ago: amazon adds more capacity to ec2 every day than they had running the entire amazon organization for the first five years of its existence04:46
lifelessyeah04:46
lifelessscary shit04:46
StevenKmwhudson: *!!!*04:47
poolieyep, i heard that too04:47
* mwhudson fails to google up the source for that04:47
lifelessit was in their newsletter04:48
pooliethe other one is that google is the largest pc manufacturer in the world04:48
poolieperhaps fsvo pc04:48
mwhudson"launch an instance in the -Any- availability zone" -- _surely_ we do that already04:48
StevenKStep 5 of that answer makes me eyeroll.04:48
poolieand fsvo manufacturer04:48
lifelessmwhudson: no, you get to choose a zone04:48
lifelessmwhudson: this is 'are you feeling lucky punk' zoning04:48
mwhudsoni know you can specify a zone, but you can also say "i don't care which zone" can't you?04:50
mwhudsoni can't see anything in devscripts/ec2test that would specify a zone04:51
mwhudson(or a region, come to that)04:51
mwhudsonanyway, time to go04:51
pooliehm maybe i can also fix this '400 bad request' in shutdown04:51
lifelessthe endpoint you connect to04:51
lifelessisn't it04:51
mwhudsonlifeless: no, zone is a parameter to runinstances04:54
mwhudson(he says confidently, after reading the api docs)04:54
mwhudsonregion, i think you're right04:54
lifelessmeh, I'll need to page in then04:54
mwhudsonPlacement.AvailabilityZone | The Availability Zone you want to launch the instance into Type: xsd:string Default: EC2 chooses a zone for you04:55
mwhudsonanyway, time to wander around in the sun for a bit04:55
* mwhudson eods04:55
lifelessnow for the joy of updating LP04:57
pooliethat error  might have meant there were none anywhere in east1"04:57
pooliethat error  might have meant there were none anywhere in east1"04:58
* StevenK seriously ponders a patch to bin/test that makes --subunit the default if output isn't a TTY.05:03
poolieok so this does seem a _lot_ faster05:17
pooliebecause the job i started later has finished ahead of the original version of the code i started half an hour earlier05:17
poolieit may be measurement error, i can't really believe it05:17
wgrantWhich job?05:17
poolieupdate-image with fs performance tweaks vs without05:19
wgrantHmm, what does update-image do that can be temporary?05:19
pooliebranching and setting up lp seems massively faster05:19
wgrantAssuming you mean a tmpfs.05:19
pooliethis is with data=writeback etc05:19
pooliealso05:19
wgrantAhh05:19
wgrantpoolie: https://launchpad.net/builders/actinium05:20
wgrantBuilding now05:20
poolieec2instance discards stdout when it runs commands on the slave05:20
poolieno05:20
poolieok, stdout is out of order with stderr05:26
wgrantpoolie: Huh05:28
poolieis possibly hard to avoid05:28
wgrantpoolie: maverick and oneiric built successfully 5 hours ago05:28
pooliethere are two pipes; they have an ordering05:28
pooliewe are not as smart about reading from them as a regular ssh would be05:29
poolieconceptual pipes05:29
pooliefor some reason we have our own select/recv loop05:29
StevenKlifeless: https://code.launchpad.net/~stevenk/launchpad/subunit-default-not-a-tty/+merge/8235205:35
lifelessdoes that work?05:38
lifelessI thought optparse options didn't like being written to05:38
lifelessalso where are you needing this?05:38
StevenKNowhere, I'm scratching an itch05:39
stuboverwriting optparse options works05:39
lifelessStevenK: I'm just worried it may mess something up for other people05:39
lifelessStevenK: is there a --non-subunit option if they want non-subunit there ?05:40
stubAlthough you are usually better off using parser.set_defaults() *before* parsing the command line05:40
StevenKI don't think so.05:40
StevenKlifeless: It has seriously taken me 5 minutes, I don't mind tossing it if need be.05:40
lifelessStevenK: it would be nice to have an opt-out, I think.05:40
lifelessStevenK: i've been known to run non-subunit through less, for some nitty debugging situations05:41
stub(branch_nick, revno) doesn't really identify the revision of a tree that was used because branch_nick is not unique. Is there a better key available? I need to record what branch+revno was used for the latest database update05:46
pooliewgrant, mwhudson, something like https://code.launchpad.net/~mbp/launchpad/ec2-tmpfs/+merge/8235505:54
pooliestill testing it05:54
* wallyworld off to the vet again. poor dog :-(05:56
lifelessstub: revid is a globally unique identifier06:03
lifelessstub: can look that up in the history of a given branch to identify the local revno for it06:03
stublifeless: For a revision, or for the branch at that revision?06:03
lifelessstub: revision06:03
stubSo I could, say, keep a table with every revid in the branch that has been applied to production.06:05
stubOr just the lastest revid, hopefully 'good enough' (although someone cowboying the wrong way could send automation crazy)06:05
lifelessso the branch has many more revids than db schema patches06:06
lifelesswhats the big picture here06:06
stubthere are more to db updates than schema patches (trusted.sql, update.py, its dependencies...)06:07
stubhttps://bugs.launchpad.net/launchpad/+bug/84546406:07
_mup_Bug #845464: deployment report should fail revisions in stable containing undeployed db changes <fastdowntime-later> <Launchpad itself:Triaged> <qa-tagger:Triaged> < https://launchpad.net/bugs/845464 >06:07
lifelessstub: can we make trusted.sql into patches, and ignore update.py ?06:07
stubWe need to know what has been deployed. That is what is safe to merge from db-stable -> devel.06:08
lifelessyes, I agree06:08
lifelessuhm, yes, if you record a single 'latest rev deployed' in the prod DB, and we only deploy forwards, then you can just do a merge graph check to see what revs are safe to merge from db-stable to devel06:09
stubKnowing the db patch numbers that have been applied isn't perfect, as patch numbers could conflict if people mess up, and we want the version-applied rather than a potentially modified one.06:09
stubKnowing the revision number isn't perfect, as there is a chance we didn't deploy from db-stable06:10
lifelesswell, lets not overthink it - because the things that can go wrong are infinite :)06:10
stubBut we probably won't get perfect, so looking for a balance of correct and good enough06:10
lifelessand we'll get cascading failures in both of those cases.06:10
lifelessin the former case we'll have developers going zomg wtf, not to mention failures on staging, failures on pqm06:11
lifeless(More reliably too if we drop the redundant patch info from the file - less ways for devs to mess up)06:11
lifelessfor the latter case, hmmm, no guarantee of cascade failures, OTOH can we automate it so we can't messs up ?06:12
stubAt the moment I'm thinking of lastest revid and assuming that the branch is lp:launchpad/db-stable06:12
lifelessI think that would work fine06:13
lifelesss/stest/test/06:13
pooliehm i guess we could fold together stdout and stderr on the server and that would avoid the issue06:14
nigelbmwhudson: Oooh. nice idea with using the ec2 with higher memory!06:23
nigelbThe shaping launchpad's next 18 months thread is full of win :)06:25
poolieit sure is06:28
lifelesswallyworld: wgrant: Picking two random js fluent folk; what js should we (or do we?) use in python-oops-tools? Whats the easiest way to tell? If none is in use, whats the easiest way to get up and running with YUI, (given that unlike LP the user base is captive, and having it greased-lightning fast isn't critical)06:40
wgrantlifeless: It doesn't have any JS at the moment, except for the jQuery that's built into Django's admin UI.06:41
lifelessso, what I want to do is take the text traceback06:44
lifelessStevenK: https://code.launchpad.net/~lifeless/launchpad/oops-polish/+merge/82359 if you are still reviewing06:45
StevenKI'm not, sorry.06:45
=== StevenK changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: - | Critical bugtasks: 277
* micahg hugs LP devs for the cancel build option06:47
wgrantmicahg: Watch out, it's permanent and non-retriable.06:47
micahgunderstood (does it mention that on the cancel page)?06:48
wgrantI don't know. I didn't realise it was publicly available until a couple of days ago.06:48
micahgI've usually only wanted it in cases where I know it's going to fail and will be uploading a new version06:48
lifelesswgrant: anyhow, that MP above06:48
lifelesswgrant: will get us backtraces from actions in the LP timeline06:49
lifelesswgrant: I want to put them in the linear query section of the oops viewing template in python-oops06:49
lifelesswgrant: hidden by default06:49
lifelesswgrant: with a clicky clicky thing to show it06:49
lifelesswgrant: I'm not bothered about automated correlation or anything at this point06:50
lifelesswgrant: I'm seeking opinionated 'do it this way its easiest' answers.06:51
wgrantlifeless: I've never started a fresh YUI project before.06:52
wgrantjQuery is trivial.06:52
micahgah, but the cancel button only seems to be on pending builds, but that's progress :)06:52
wgrantmicahg: It works on building virtual builds.06:53
micahgah, ok, I just checked a native one06:53
wgrantIt doesn't work on non-virtual builds, because we can't really cancel them.06:53
lifelesswgrant: so, opinionated recommendation ?06:54
wgrantlifeless: Work out how to use YUI, I guess.06:54
wgrantI don't have a good solution.06:54
lifelesshmm, but jquery is bundled06:56
wgrantWith Django, yes.06:56
lifelesswouldn't it make sense to use one library within the one site ?06:56
wgrantBecause Django is hideous.06:56
nigelbwgrant: So much hate for Django :(06:56
pooliethe ec2 ubuntu archive seems to be unreachable06:56
poolie:/06:56
pooliefwiw the default az is that aws chooses an az for you07:01
nigelbThat's probably for the best.07:04
nigelbI've seen cases where aws says some zone doesn't have the machine you want.07:04
nigelb*doesn't have any more of07:04
nigelbThat's when I realized there exists such a limit per AZ.07:04
pooliei wonder if we should mirror that image in to singapore07:06
wgrantIsn't Singapore significantly more expensive?07:07
poolieonly slightly more expensive07:09
pooliei think 57c/hr vs 5007:09
wgrantAh, not so bad.07:09
pooliealso it may not be on fire at the moment07:10
wallyworldlifeless: i've not used jQuery, but if it's bundled with Django and python-oops-tools uses that, it makes sens to me to just use jQuery07:11
nigelbpoolie: wait, what's on fire?07:12
* wallyworld now has 2 launchers running after unity crashed :-/07:18
pooliei'm having a lot of trouble launching anything in us-east-1, and lots of things are failing with network glitches after they are launched07:19
StevenKHeh, so effectively AWS is.07:36
nigelbpoolie: Now you're scaring me.07:38
* nigelb has workplace depending on us-east-1.07:38
StevenKThere is now us-east-207:39
StevenKBut migrating AZs is horrid07:39
nigelbpoolie: AWS status says there was some DNS issues in us-east-107:40
nigelbUgh, but that was at least 4 hours ago. and that's marked as resolved already.07:40
jtv-afkStevenK, wgrant: successful package build on dogfood!  Now it says "uploading build."07:41
=== jtv-afk is now known as jtv
jtvIt's been "uploading build" for a long time though—6 minutes!07:43
wgrantjtv: Is the build upload cronjob enabled?07:43
jtvOh, that's a separate cron job?07:43
wgrantYes07:43
jtvI looked at the “crontab -l” output for the launchpad user, but the only thing mentioning “upload” there is process-upload.07:45
wgrant#*/5 * * * * LPCONFIG=dogfood /srv/launchpad.net/codelines/current/scripts/process-upload.py -C buildd --builds -v /srv/launchpad.net/builddmaster -a jelmer@canonical.com >> /srv/launchpad.net/dogfood-logs/upload-builds.log 2>&107:46
wgrantIt's disabled.07:46
poolienigelb, ok, image building in singapore!07:53
nigelbpoolie: *whee*07:53
pooliemaybe07:53
nigelbheh07:53
lifelesspop quiz07:53
pooliefor me that is ~165ms away07:54
lifelesshow bad would it be to just add the tb as another table column07:54
nigelbhow far is us-east-1?07:54
poolie275ms07:54
nigelbthat's significantly faster!07:54
poolieyeah07:54
poolieat least if you're going to do anything interactive07:54
poolieus still seems to be having network problems though07:55
nigelbah, right. I can't ping our machines from outside.07:55
poolieus still seems to be having network problems though07:56
poolieand so am i :)07:56
nigelbDid you raise a ticket?07:56
pooliei thought it was me07:56
lifelessjtv: I believe you are OCR today?07:56
jtvlifeless: I believe you are right.07:56
lifelessI have a midsize branch https://code.launchpad.net/~lifeless/launchpad/oops-polish/+merge/82359 if you have the time07:57
lifelessits just updating to newer dependencies and dealing with the fallout07:57
jtvlifeless: I'll take it07:59
pooliewow actually despite the smaller mean ping time that is noticeably more responsive08:00
lifelessjtv: thank you08:00
lifelesspoolie: despite or because of ?08:00
jtvwgrant: would it be okay to reproduce the command line from that cron job?08:00
lifelessjtv: if there are no passwords or production paths in it, it should be fine.08:01
lifelessjtv: if you're in doubt, you can paste it to me and I can venture an opinion08:01
jtvThat's dogfood, and I'm copying it off public IRC.  :)08:01
lifelesshah :P08:03
wgrantjtv: Huh?08:03
wgrantjtv: Oh, you mean run it manually?08:03
jtvYes08:03
wgrantSure, or just reenable the cron job...08:03
jtvNote the bit about being smacked on the head.08:03
jtv\o/ successfully built08:04
wgrantHe's away for ages, he won't notice.08:04
wgrantAnd there's no auditing.08:04
wgrantSo we just have to delete IRC logs and you're safe :)08:04
jtvThe secret to a happy life: impunity!08:04
nigelbpoolie: I just did an apt-get update on a machine and it seems to hit the mirror fine.08:07
poolielifeless, "despite the measured difference being small the subjective difference is large"08:08
lifelessah :)08:08
lifelesslog senses :)08:09
poolieyeah08:09
poolieor perhaps there is less jitter or variability or something08:09
poolienup, there's very little08:10
pooliei don't know then08:10
poolieerror: lp.code.model.tests.test_codeimportjob.TestCodeImportJobWorkflowNewJob.test_dateDueOldPreviousResult [ multipart08:10
poolieis this spurious? i did'nt break it i think08:10
poolies//i don't think i broke it08:10
wgrant/date/i -> spurious08:10
jtvlifeless: question about ll.132—133 of the diff… was it meant as a feature for "name1" to be able to occur twice with different values?08:11
jtv(req_vars008:11
jtv*(req_vars)08:11
jtvIt doesn't make much sense to me, but I wonder why the test seems to want to exercise that.08:11
lifelessjtv: it was a bogus concept08:11
lifelessjtv: all our producers and consumers dictified it.08:11
jtvAmusing.08:12
lifelessjtv: the change here eliminates it08:12
jtvWell, this does look a lot better.08:12
poolieyou have got to be ... kidding me08:12
lifelessyou'll see a lot of s/dict(// in the diff :)08:12
poolie            counter = count(randint(0, 1000000))08:12
lifelesspoolie: thats in your TCP stack ?08:12
pooliethat's in the test factory08:13
poolieeventually the same number will turn up twice08:13
jtvYowza—the tests even depended on ordering of req_vars.08:14
pooliehttp://irclogs.ubuntu.com/2011/04/13/%23launchpad-yellow.html#t18:3608:14
nigelbInteresting.08:15
lifelessjtv: this is a long running source of low grade pain08:15
lifelessjtv: I'm very very happy to finally have hit the point in this oops yak shaving exercise that addressing it was reasonable.08:15
wgrantpoolie: Was that your failure?08:16
pooliethat is giving me a very wgrant moment08:16
wgrantOh?08:16
pooliewho on earth counts on random integers being unique in a test08:16
StevenKWe do.08:16
wgrantIt's probably not random.08:16
lifelessjtv: after this, there is https://code.launchpad.net/~lifeless/python-oops-tools/polish/+merge/82365 which shows backtraces on each SQL query in lp-oops, something that I think will help folk tracking down sources of thousand-query-death.08:16
wgrantOh, it uses getUniqueString08:17
wgrantI see08:17
lifelessjtv: its also pretty small and self contained.08:17
nigelb"a wgrant moment" heh.08:17
pooliewgrant, there may be some other explanation08:18
lifelessjtv: I will be back soon - getting dinner for the family08:18
wgrantWe see similar sorts of things when a test runs a script but doesn't mark the DB dirty. Sequences don't get reset, so extremely confusing errors crop up a few tests later.08:18
pooliebut that randint call looks like a pretty big red flag08:18
wgrantBut in this case you're right, I think.08:18
pooliei wonder why it is trying to make them unique per-thread?08:19
pooliewhy would you want that08:19
wgrantpoolie: No idea.08:23
poolie'wgrant moment' meaning swearing at people08:29
poolieanyhow, https://bugs.launchpad.net/launchpad/+bug/89102808:29
_mup_Bug #891028: TestFactory getUniqueInteger isn't <spurious-test-failure> <Launchpad itself:Triaged> < https://launchpad.net/bugs/891028 >08:30
lifelessjtv: I am back, if that matters :)08:42
jtvlifeless: I am sure you are happy to be back.  And that is a good thing, right?08:43
lifeless:P08:43
jtvNice error page we have now…08:43
jtv(Which is what I get instead of your other MP)08:43
lifelesshmm, works fir me08:44
lifelessI think you hit fdt08:44
jtvYes.  It was a nice frowney.08:45
mrevellHello09:03
adeuringgood monring09:03
jtvmorning mrevell, morning adeuring09:16
mrevellHowdy howdy howdy09:17
pooliehi mrevell09:21
lifelessjtv: so did you have any thoughts on https://code.launchpad.net/~lifeless/python-oops-tools/polish/+merge/82365 ?09:26
jtvNot yet.09:26
lifelessk09:26
jtvI think I'll have my standup first.09:26
lifelessfair enough09:26
lifelessI'm going to halt() - tl meeting in the early am09:26
lifelessjtv: so if you don't get to it, its not a problem, I can nab first-up OCR tomorrow09:26
jtvI should get to it anyway.  Good night!09:27
lifelessnn09:27
pooliemrevell, i liked curtis's karma rant09:29
pooliei was going to speculate but i won't09:29
mrevellpoolie, Let's speculate; it's fun :) I have a reply in mind, but I want to stick to Curtis' request of "doing something" rather than just bikeshedding. Dashboards and walls are on the roadmap for next year. Karma ... let's kill it and, if we replace it with anything, let's replace it with human-awarded recognitions. "poolie thanked mrevell for xxxxx", or similar.09:35
pooliei would possibly, if it gets to the top of my queue09:36
poolieput up a patch that hides all mention of karma as a number09:36
poolieso you just see Person has been active in Project09:37
poolieor maybe "N most active people"09:37
mrevellRight, so long as the people in that list are there because of the number of useful actions rather than their karma score.09:37
pooliewell09:37
pooliei think this is complementary to, but decoupled from, having a better sense of what is useful action09:38
pooliemaybe if we had a really well calibrated measure of useful we'd be ok to show it as a number, but maybe not even then09:38
pooliemrevell, oh the other thing as far as 'thankyou'09:41
pooliewould be to add some social network buttons09:41
pooliei realize this will be controversial and might be a bad idea09:41
pooliealso might not actually be useful09:41
pooliemight be interesting09:41
wgrant"wgrant liked this bug"?09:43
wgrantThat doesn't sound very useful...09:43
poolieyeah one drawback is that a lot of lp is bugs09:44
pooliemm09:44
pooliei can imagine voting up your merge proposals, or thanking you for fixing things09:44
mrevellKarma, as anything other than a list of actions, is a false representation of the value of someone's contributions. I think we can make useful judgements about what is a useful action but when we start weighting actions and so on, it leads to discontent. THere are some people who like karma and I know that turning other types of software into pseudo-games is a thing right now, but I'd rather see human recognition o09:45
mrevellf good work done than a calculation that is basically broken.09:45
poolieyeah09:45
mrevellpoolie, As for +1s and Likes, it fits in with what some people have asked for. Like you say, you'd limit it to certain actions.09:45
mrevellSo09:45
pooliei think if i saw a person's timeline, or a project's timeline, that would give me a much better calibrated sense of their contribution09:46
poolieamhnews's timeline :)09:46
mrevellpoolie, Right yeah09:46
mrevellSo, you wouldn't like a bug, you'd like that someone had reported a bug.09:46
mrevellOr rather, thank them09:46
mrevellin some way09:46
pooliemaybe thank them for fixing it09:47
pooliemaybe +1 a project09:47
mrevellpoolie, or reporting a bug, I think that's fine.09:47
mrevellYeah, +1/Like a project09:47
mrevellor a patch09:47
mrevellor a branch09:47
poolieso09:47
mrevellHmm, interesting.09:47
mrevellI can feel some LEPping coming on.09:48
poolieso it seems at least interesting if not totally justifiable09:48
mrevell:)09:48
pooliemm09:48
pooliedownsides:09:48
poolie - may break things09:48
poolie- people will bitch about it09:48
poolie- gives personal data to $company09:48
poolie- need to choose which ones to do09:48
poolie- opportunity cost09:48
mrevell1. Everyone we do breaks things09:49
mrevell2. Depends who and whether they have a point.09:49
mrevell3. We should have very clear and effective opt-outs or even make it opt-in.09:49
mrevell5. Dashboards and walls are important, IMO; this is just a bit of icing that we might be able to get on top.09:50
mrevells/Everyone/Everything09:50
mrevellpoolie, Do you think this will break things more than usual?09:50
poolieprobably less09:50
poolieless than changing the buildds :)09:51
wgrantHow will it work with our ever-expanding volume of confidential data?09:52
poolieit's a really good question09:52
poolieone answer is that i think we run urchin.js on all pages at the moment09:52
poolie(?)09:52
mrevellwgrant, I think that's the part where I get to say, "Ha, mere implementation detail" :)09:52
poolieso google already know all the urls and get to run js on them09:52
wgrantpoolie: I believe so, yes, which is pretty awful.09:52
wgrantBut being open to Google Analytics compromises is one thing.09:53
wgrantMost of the web is open to that.09:53
poolie:)09:53
mrevellI have a call shortly. I'm spending to day preparing the LP roadmap for the stakeholder meeting tomorrow. We have a skeleton Activity Walls LEP: contributions welcome: https://dev.launchpad.net/LEP/ActivityWalls09:53
wgrantWhat do the social network buttons do?09:53
wgrantI've never used one.09:54
poolieso this would potentially encourage people to click "+1 woo hoo" on the Ubuntu Electric Car project09:54
pooliedespite it being private09:54
adeuringstub: could you have a look at this MP: https://code.launchpad.net/~adeuring/launchpad/bug-sorting-by-attachment-age/+merge/82315 ?09:54
wgrantpoolie: That's sort of what I'm worried about.09:54
stubadeuring: yup. saw that earlier - will go over it now09:54
pooliei was wondering about that too09:54
adeuringstub: thanks!09:54
poolieperhaps a Must is that they only appear on public pages09:54
wgrantI don't think it's really useful for something like LP.09:54
wgrantBut maybe.09:54
poolieif that can be easily cheaply computed09:54
pooliewgrant, they typically act as a counter of how many people clicked it, they may post it to a feed you create on the web09:55
wgrantBut then we're further restricting functionality by privacy, which seems sort of bad.09:55
pooliethey can skew google's search results09:55
pooliewhich is i think one of the more interesting outcomes09:55
pooliehttps://plus.google.com/105614526446850346960/posts/VZYQR5rsKUA09:56
pooliethe first step would be to give less stupid search snippets09:59
pooliei think i'm tired09:59
nigelbpoolie: any luck with singapore?10:24
stubadeuring: done.10:35
adeuringstub: thanks!10:35
stubadeuring: I can throw together the populate script after the patch is deployed if you want (for i in range(1,1000000): cur.execute(...); con.commit())10:36
adeuringstub: that would be great!10:36
stubCan I get the revision id of the last committed revision in my branch with the bzr command line?10:48
* stub finds log --show-ids10:50
wgrantstub: bzr version-info --custom --template="{revision_id}"11:14
stubta - that is nicer11:14
poolienigelb, it's still building there11:18
pooliei think it will be ok unless there's another glitch or bug11:18
pooliemrevell, https://www.google.com/support/webmasters/bin/topic.py?hl=en&topic=114019111:19
mrevellAh thanks poolie11:20
mrevellWhich Google account? martin.pool@canonical.com?11:22
mrevellarg11:22
poolie:)11:22
stubslow but :-/11:22
stub10 seconds more to fastdowntime. Hopefully faster on real disks.11:23
stuboh... don't test on a remote checkout idiot11:25
pooliewoo, ok, a spicy singaporean AMI!11:35
rick_h_morning party people11:40
wgrantMorning rick_h_11:43
nigelbpoolie: Yay! :)11:47
nigelb(sorry, meetings suck. I was stuck in one for an hnour)11:47
nigelb~>11:48
wgrantpoolie: HMMMM12:01
wgranthttps://lpbuildbot.canonical.com/builders/lucid_lp/builds/1559/steps/shell_6/logs/summary12:01
wgrantThere are a few potential suspicious revisions :(12:02
rick_h_hey, I've been fighting that for the last 2 days12:03
rick_h_the random generated "person-name" is always the same id number12:03
wgrantHave you ever managed to reproduce it locally?12:03
rick_h_no, not once12:03
rick_h_always works locally12:03
rick_h_tried 4 times, my bugfix branches 3 times and ran devel last night to see if maybe it was me12:04
rick_h_always get the same 92359412:04
rick_h_but the getUniqueInteger method should be 'random' starting point12:04
poolierick_h_, i filed a bug12:06
poolierick_h_, where are you btw?12:06
rick_h_Michigan USA12:06
pooliethis is like the things i was fighting a few weeks ago where12:06
poolieamazon seemed to have great aptitude for finding timing dependent failures12:06
rick_h_I thought maybe as well, but I've done 4 runs over 2 days (3 runs yesterday) and it's always the same12:07
pooliealways the same test?12:07
wgrantrick_h_: What's the earliest devel revno that showed the problem?12:07
rick_h_I just want to land my pretty "add a css class" bugfix :)12:07
pooliei wonder if it is not coincidental12:07
rick_h_poolie: yes, same test, same invalid person name12:07
pooliewhoa12:07
wgrantIt may be the DB dirtiness issue that I alluded to earlier.12:08
rick_h_sec, let me see if i can find my original failed test branch12:08
wgrantSomeone should try running the previous 100 tests or so12:08
wgrantSee if it's reproducible.12:08
wgrantLocally, I mean.12:09
rick_h_https://code.launchpad.net/~rharding/launchpad/bugfix_814696 is my branch I first got it12:10
rick_h_so 14294 was where I started out at?12:11
wgrantThe ec2 email should say which version of devel was used.12:11
rick_h_sorry, still getting back into bzr12:11
rick_h_yea, I'm still searching for that original email12:11
poolieadd a -r option to ec2 test12:11
wgrantIt automatically merges devel before it starts running tests.12:11
rick_h_ah, nice12:11
pooliethere isa  --trunk otpion12:14
poolieadd a -r and see if trunk sucked in the past12:14
wgrantIt's easy enough to bisect, but I'm hoping to find out how far back we might have to look.12:15
wgrantWithout running too many ec2 instances...12:15
pooliervba, does your patch seriously cut that page from 1000+ to 7 queries?12:17
pooliewgrant, there's only say 200 per month12:18
poolieless than 8 runs should be enough12:18
wgrantThat's true.12:18
wgrantBut anyway, hopefully gary or someone can sort this out before I get a chance to.12:20
rick_h_ok, found that first test email. Source: bzr+ssh://bazaar.launchpad.net/~rharding/launchpad/bugfix_814696 r1429612:25
rick_h_Target: bzr+ssh://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/ r1430112:26
wgrantHmmm12:26
wgrantSo it wasn't the testfix.12:26
poolie+sed -ie 's![ \t]\/[ \t]*ext3[ \t]*defaults[ \t]!/ ext3 data=writeback,commit=3600,async,relatime!' /etc/fstab12:33
poolieisn't that just such a good idea12:33
pooliedon't tell elmo12:33
rick_h_poolie: ooh pretty12:34
nigelbpoolie: elmo will probably shoot you or shoot himself.12:40
pooliei hope it's actually faster after all these round trips12:41
nigelbheh12:44
rvbapoolie: I was lunching… what patch?13:25
rvbaGosh, I've been bitten by this too: "NameAlreadyTaken: The name 'person-name-923594' is already taken."13:27
rick_h_do you always get it? or is it temp?13:29
rvbaI just got it in an ec2 run.13:29
rick_h_ah ok13:29
rick_h_rvba: ping13:40
rvbarick_h_: pong13:41
rick_h_I'm finishing up getting that bugfix for the close button we talked about yesterday13:41
rvbaGreat13:41
rick_h_I'm wondering if you know the what for on the green "steps" bar that shows up on the edit sub link?13:41
rick_h_I thought it was mostly decorative/header showing kind of thing13:41
rick_h_but the docs seem to imply some sort of multi-step process or something in overlay.js?13:42
rvbalet me have a look.13:42
rick_h_Hmm, I guess some links do have it only half across, some all the way,13:44
rvbahum, this step 'thing' is new to me… let's see where it's used.13:46
rick_h_https://bugs.launchpad.net/launchpad/+bug/74146313:47
_mup_Bug #741463: popup diff close button misplaced <trivial> <ui> <Launchpad itself:In Progress by rharding> < https://launchpad.net/bugs/741463 >13:47
rick_h_most of the ajax links on the right have it in some fashion13:47
rick_h_"link to related branch" is half across13:47
rick_h_subscribe someone else as well13:47
rick_h_https://bugs.launchpad.net/launchpad "subscribe to bug mail" is all the way across13:48
rvbaweird13:49
rvbarick_h_: oh I see13:51
rvbarick_h_: it's a kind of weird looking progress bar for multi step stuff.13:52
rick_h_right, that's what the code seemed to say, but things like that "subscribe to bug mail" didn't seem to describe 100% done of some process13:52
rvbarick_h_: like when you "subscribe someone else", first you search for a name (step1) and then you pick up someone from the list you get (step2).13:53
rick_h_ok, so that overlay itself has another step after submitting the form then13:53
rick_h_so if I'm loading this diff, should I include it as just 100% done then? Or leave it out since there's not really a process to go through13:53
rick_h_you're just loading the content13:53
rvbarick_h_: I suppose it should be 100% because because there is no next step ;)13:54
rick_h_ok, will go that route then13:54
rick_h_thanks13:54
rvbarick_h_: thank you, you made me discover something I simply never spotted before ;)13:55
rvbarick_h_: did you see other pickups where the green bar is simply absent?13:59
rick_h_rvba: yea, like the "this bug affects me"14:00
rick_h_but that's a slightly different overlya14:00
rick_h_overlay14:00
rvbaI suppose it's still based on the very same js code.14:00
rvbarick_h_: in fact, maybe it's best to leave it out then.14:02
rick_h_rvba: yea, there's a flag in the JS to show progress bar14:07
rick_h_in the pretty overlay ATTRS14:07
rvbarick_h_: the presence or not of the green bar does not seem to be very consistent across lp.  But it seems to be associated with "performing an action" within an overlay.  In your instance, you don't *do* anything with the overlay, it's simply showing information.14:08
rvbaSo yeah, on second though, I think you can leave it out.14:08
rick_h_yep, I kind of wanted it since i thought it looked good, but seems to have a reason/madness if a bit inconsistant14:08
rick_h_ok, I can agree with that then14:09
rvbaCool.14:09
jcsackettmorning, all.14:13
rvbaHey jcsackett.14:13
jcsacketthi, rvba. :-)14:14
rick_h_morning14:14
rick_h_rvba: ok, branch up, put you in as requested reviewer14:16
rvbarick_h_: sure, I'm in the middle of something right now but I'll get to it later.14:18
rick_h_np, thanks for the help getting things figured out14:18
rvbawelcome.14:18
rick_h_adeuring: we were talking about that ec2 test failures this morning. That's the error I was dealing with yesterday on the call14:27
adeuringrick_h_: ah, thanks for the hint!14:27
nigelbhah, adeuring mailed about the same failure that everyone's talking about.14:27
=== Ursinha is now known as Ursinha-lunch
deryckgary_poster, we have a persistent build failure affecting ec2 and buildbot runs, which seems like a timing issue in factory generated stuff....14:49
deryckgary_poster, I'd ping bigjools, too, but he isn't here. :)  it seems like the kind of thing a maintenance squad should look at...14:50
deryckgary_poster, given no one can pin down a change that introduced it.14:50
deryckgary_poster, what do you think? :)14:50
gary_posterderyck, sorry, my IRC ping failed me somehow, sorry.14:55
derycknp14:55
deryckI see you are aware from mail.14:56
gary_posteryeah14:56
gary_posteryeah, deryck, I'll dig into it or get someone else to14:56
gary_posterderyck, do you know when this started?14:56
gary_posterthe most recent buildbot failure was the first one I've seen14:56
deryckgary_poster, I know that rick_h_ was having the issue in ec2 early yesterday.14:57
gary_posterderyck, ah ok, so another intermittent issue. :-/  ok, thanks14:57
deryckgary_poster, well, it's not intermittent, I don't think.  Not entirely.  rick_h_ gets it consistently in every run as does adeuring.14:58
rick_h_yes, I've completed 4 runs over the last 48 hours, each with the same failure and everyone has the same person id as the same failure id14:58
gary_posterah ok14:59
=== matsubara is now known as matsubara-lunch
nigelbgary_poster: If it helps, poolie ran into it all day as well I think.15:01
=== matsubara-lunch is now known as matsubara
abentleyrick_h_, adeuring, deryck: Here are my current aliases, with comments about what they do: https://pastebin.canonical.com/55863/15:42
rick_h_thanks abentley15:43
adeuringabentley: cool, thanks15:43
deryckabentley, yes, thanks!15:43
deryckrick_h_, let's mumble top of the hour.  cool?15:44
rick_h_sounds good15:44
abentleyrick_h_: Here's a snippit that can't be expressed as an alias:  bzr lp-find-proposal -r mainline:annotate:lib/lp/bugs/javascript/buglisting.js:2015:47
abentleyrick_h_: It means "find me the merge proposal in which landing this line was discussed".15:48
rick_h_cool, going through the app auth process15:49
abentleyrick_h_: it needs to run in the branch the proposal was targeted against.15:51
=== abentley changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: abentley | Critical bugtasks: 277
bacrick_h_: so are you seeing all fail with person-name-923594 ?16:03
rvbabac: I've had the problem in ec2 a few hours ago too.16:07
bacrvba: can you confirm it was with exactly the person name i listed?16:08
rvbabac: yep (NameAlreadyTaken: The name 'person-name-923594' is already taken.)16:08
jelmerhi bac, rvba16:13
jelmerI've just had an ec2 failure with that error as well16:13
bacthanks jelmer16:13
rvbahi jelmer.16:13
jelmerI had a quick look, but I didn't see any recent changes in that area. Has either of you looked into it further?16:14
rvbanot me, bac is on the case ;)16:15
rick_h_bac: yes16:25
bacthanks rick_h_16:26
rvbarick_h_: btw I've reviewed your mp (you should have received an email about that).  I think you need to add a test for the change and then you're good to go!16:27
rick_h_rvba: yep, thanks. Great feedback, appreciate it16:28
rick_h_working on it now16:28
rvbaGreat.16:28
allenapabentley: Could you sanity check a script for me? https://code.launchpad.net/~allenap/launchpad/wipe-precise-translations/+merge/8242216:34
abentleyallenap: looking.16:35
allenapThanks.16:35
abentleyallenap: It looks okay, but I'm no expert on this domain.16:37
allenapabentley: Thanks, awesome.16:37
=== salgado is now known as salgado-lunch
=== beuno is now known as beuno-lunch
mtaylorit's posssible to do a bug import into a project that already has bugs, yeah?17:36
gary_posteradeuring, when did you first see the person-name-923594 problem?  rick_h, are you the only one who saw the problem 48 hours ago to your knowledge?  Is there reason to suspect that it might be in a diff that you made?17:42
gary_posterIt's odd that everyone can reproduce it now17:42
gary_posterand buildbot only just failed with it now17:43
gary_posterbut people report it earlier17:43
rick_h_gary_poster: I was the first to see it because I was trying to run my first ec2 test Tues morning.17:43
rick_h_but no change of mine has landed17:43
gary_posterrick_h_ ok cool thanks17:43
rick_h_and that first run was just to add a css class to an item17:43
gary_posterrick_h_, that was it! ;-)17:44
adeuringgary_poster: recieved a failure messsage  yesterday, 22:39UTC17:44
rick_h_I just think I got lucky to start running ec2 tests at the right moment17:44
gary_posterok thanks adeuring17:44
gary_posterrick_h_ you said before that you had seen the error 48 hours earlier, which would have been Monday morning.  Was it Monday or Tuesday that you first saw it?17:46
rick_h_sorry, guess I started trying to run tests monday afternoon17:46
rick_h_and we had the ec2 issues that you helped me through17:46
rick_h_so the actual run didn't go until Tues17:46
adeuringgary_poster: first line from the log of the test run: Tests started at approximately Tue, 15 Nov 2011 18:04:11 UTC17:46
adeuringbzr+ssh://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/, revision 1430117:46
rick_h_I got the failure email about 2pm EST on tues17:46
gary_posterrick_h_, adeuring, ok thanks, that's a big help.17:47
adeuringrick_h_: the revision number from your failure could help Gray too17:47
adeurings/Gray/Gary/17:47
rick_h_adeuring: yea, it was the same, 1430117:47
gary_posterok thanks17:48
=== Ronnie1 is now known as Ronnie
rick_h_Source: bzr+ssh://bazaar.launchpad.net/~rharding/launchpad/bugfix_814696 r1429617:48
rick_h_Target: bzr+ssh://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/ r1430117:48
gary_posteryeah, 14301 then17:48
deryckabentley, I filed bug 891239 after doing qa on my integration work.  Is that what your branch fix from yesterday addressed?17:48
_mup_Bug #891239: CustomBugListings js error: Cannot read property 'mustache_model' <bug-columns> <Launchpad itself:Triaged> < https://launchpad.net/bugs/891239 >17:49
mtaylorsinzui: how do I add a file to a question so that a losa can get at my bug import xml file again?17:50
sinzuimtaylor, launchpad does not support attachments to questions17:51
sinzuisee bug 7712317:51
_mup_Bug #77123: Attachments in answer tracker <feature> <lp-answers> <Launchpad itself:Triaged> < https://launchpad.net/bugs/77123 >17:51
mtaylorsinzui: so how do I send the bug xml file?17:52
mtaylorsinzui: upload and add a link?17:52
sinzuimtaylor, yes17:52
mtaylorsinzui: ok. cool17:52
mtaylorsinzui: sweet. https://answers.launchpad.net/launchpad/+question/179006 if you get bored18:00
=== salgado-lunch is now known as salgado
=== Ursinha-lunch is now known as Ursinha
abentleyderyck: no.18:13
deryckabentley, ok, thanks.  And we timed out the same.  I just confirmed running your branch it's not fixed by it.18:13
deryckabentley, I'm happy to keep poking and fix it.18:14
abentleyIt was https://bugs.launchpad.net/launchpad/+bug/89074518:14
_mup_Bug #890745: dynamic bug listings don't handle next and prev correctly on first and last batch <Launchpad itself:In Progress by abentley> < https://launchpad.net/bugs/890745 >18:14
=== beuno-lunch is now known as beuno
abentleyderyck: My nets went down again.18:37
deryckabentley, np.  wb.18:37
deryckabentley, I've got some serious storms brewing here, so could lose power or nets, too.18:37
deryckrick_h_, adeuring ^^18:37
abentleyderyck: Surfing on 3G currently.18:37
deryckbummer18:38
rick_h_ouch18:43
bachi allenap, you still here?19:08
bacwallyworld: ping19:20
=== matsubara is now known as matsubara-afk
deryckabentley, interestingly chromium fires a history change event on load that ff does not.20:24
abentleyderyck: Oh well, I guess we want that to support HistoryHash stuffs, too.20:25
rick_h_deryck: yea, that's a pita20:26
rick_h_you basically have to catch the event and check if you've got anything on the stack20:26
rick_h_and edge case it20:26
rick_h_there's a big discussion on trying to decide one way or another, but different browsers choose to fire that on load or not to20:26
deryckrick_h_, yeah, such is the pain of browsers.20:27
deryckrick_h_, I think I like FF's approach on this one.  Load really isn't a history change.20:27
rick_h_yea, same here20:27
rick_h_but I think the idea is that you might be able to (on a pure client side app) determine a page when loaded20:28
rick_h_where normally the server takes care of handling the initial url params20:28
rick_h_so you need to trigger "I'm here, and here's my first page of data load info"20:28
abentleyrick_h_: YUI indicates what caused the event, so it should be pretty clean.20:29
deryckyeah, it just seems "load" represents that already. ;)  and "history" represents everything there after.20:29
rick_h_cool, I've not used that yet, only history.js20:30
adeuringderyck: my daily request to run SQL queries: https://pastebin.canonical.com/55909/20:52
deryckadeuring, ok, np20:53
adeuringderyck: thanks!20:54
derycknp!20:54
adeuringderyck: sorry, I forgot a LIMIT clause...20:58
adeuringderyck: these queires please: https://pastebin.canonical.com/55910/20:59
adeuringderyck: my first paste mised a LIMIT clause. please use this one:  https://pastebin.canonical.com/55910/21:05
deryckadeuring, ok.  sorry I got my system locked up somehow.21:05
adeuringnp21:05
=== abentley_ is now known as abentley
abentleyderyck: we were going to chat?21:06
deryckabentley, ah, forgot.21:06
deryckabentley, let's do it first thing tomorrow.  still got plenty going here.  and need to switch locations for work here shortly.21:06
abentleyderyck: might as well make it part of our regular Thursday call, eh?21:07
deryckabentley, yeah, that works.21:08
deryckadeuring, the first query is taking forever.... still going.21:09
deryckoh just finished21:09
adeuringderyck: ouch...21:09
deryckadeuring, they're done now.21:10
deryckadeuring, https://pastebin.canonical.com/55913/21:10
adeuringderyck: thanks!21:10
deryckadeuring, I need to switch locations and drop girls off at gym.  if you need anything else, email.  I'll hit it when I return.21:10
adeuringderyck: ok21:10
derycklater on, all.21:12
pooliehi21:24
poolieso, this time my singapore ami build completed21:24
poolielet's see how it goes21:24
deryckadeuring, did you need anymore queries?21:34
deryckthe gym has wifi :)21:34
adeuringderyck: no, thanks. I'll ignore the quite slow distibution related query fow now; the others wer fast enough, I think.21:35
deryckadeuring, awesome21:35
poolieStevenK, thanks for name-to-service21:37
poolieo/ deryck21:37
poolieadeuring, thanks for the beta banner, it looks really nice21:37
adeuringpoolie: thanks :)21:38
deryckhi poolie21:41
pooliehi, how are you?21:42
deryckpoolie, I'm good, thanks.  How's things with you?22:09
deryckabentley, here's how I decided to fix this:  http://pastebin.ubuntu.com/740645/22:09
deryckoops, time to go.  later on everyone.22:18
flacostewhen a branch scanning job fails22:34
flacostehow do we get the scanner to scan the branch again22:34
flacostefor example: https://code.launchpad.net/~stub/launchpad/replication22:34
lifelesspush to the branch22:38
lifelesseven a no-op will create a new job22:38
abentleyflacoste: We used to lock the branch and unlock it, but now that Bazaar Experts has been disbanded, you'll need to get a losa to do that.22:38
flacosteabentley: what command would they run?22:39
flacostelifeless: i can't push to the branch22:39
abentleyflacoste: push is probably the simplest.22:39
flacosteanything that can be done without downloading the branch first?22:39
lifelessflacoste: any sftp session that writes, or any bzr session that takes a write lock22:40
flacostelifeless: sorry, i'm thick, do you have any specific command suggestion :-)22:40
flacostebzr break-lock?22:41
lifelessbranch.lock_write(); branch.unlock()22:41
abentleyflacoste: Sure, 'bzr init; bzr push ~stub/launchpad/replication".  It doesn't have to work, it just has to lock.22:42
flacosteabentley: ah thanks22:42
lifelessabentley: still on OCR? if so - https://code.launchpad.net/~lifeless/python-oops-tools/hostname/+merge/8246623:11
abentleylifeless: sorry.23:11
=== abentley changed the topic of #launchpad-dev to: https://dev.launchpad.net/ | On call reviewer: - | Critical bugtasks: 277
lifelessabentley: no worries23:12
lifelessuhm, who can I nab, my tz... wgrant ^23:12
lifelesswgrant: 1 liner23:12
wgrantlifeless: Looking23:14
wgrantYou ask too much.23:14
wgrantlifeless: Want to add reporter while you're there?23:14
lifelesswgrant: sure23:15
lifelesswll23:15
lifelesswell23:16
lifelessappinstance.name I think is the model here23:16
lifelesswgrant: pushed23:21
wgrantlifeless: Done23:27
wgrantThanks23:27
pooliehi23:42
pooliere https://bugs.launchpad.net/launchpad/+bug/891373 where is the bzr-builder people are supposed to use to test against launchpad?23:42
_mup_Bug #891373: recipe help page has the wrong ppa name for bzr-builder <Launchpad itself:Triaged> < https://launchpad.net/bugs/891373 >23:42
pooliein ppa:launchpda?23:42
poolienot a good idea for people to add that though, since it has so much stuff23:43
wgrantpoolie: We've never had anything to do with that.23:50
wgrantpoolie: james_w/bzr handed a bzr-builder to us/IS.23:50

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