/srv/irclogs.ubuntu.com/2010/07/05/#launchpad-dev.txt

=== Ursinha-afk is now known as Ursinha
=== Ursinha is now known as Ursinha-afk
adeuringgood morning08:01
mrevellGuten morgen developertrons08:04
lifelessit is I, quasimodo08:14
=== almaisan-away is now known as al-maisan
lifelessquestion about the lp test runner10:30
lifelessif I have a test that fails in ec210:31
lifelessgiven the test name10:31
lifelesswhats the best way to run it locally10:31
StevenKlifeless: bin/test -vvt <name>10:35
lifelessStevenK: thanks10:44
lifelessStevenK: and common causes for it passing locally failing in ec2land ?10:44
mwhudsonlifeless: ec2 land is hardy running python 2.510:47
lifelesshmmm10:48
mwhudsonat a guess anyway10:49
StevenKlifeless: I'd need to see the traceback10:50
lifelesseasy done10:51
StevenKlifeless: There isn't really a bunch of common causes for stuff like this10:51
lifelesshttp://pastebin.org/38364310:52
lifelessI've merged devel to my branch locally, made no diff10:52
lifelessrunning: ./bin/test --subunit  -t test_runJobHandleErrors_oops_generated| testr load10:53
lifelessid: 46 tests: 19 skips: 210:53
mwhudsonoh10:54
mwhudsonwell, at least partly what's going on here is a glorious lack of test isolation10:54
lifelessaroo ?10:55
lifelessI'd like to make oops' generated by tests not hit disk at all10:55
lifelessbut I don't want to make the patch bigger still10:55
lifelessas my focus is profiling, not oopses10:55
mwhudsonotherwise it looks like a parenthesising bug?10:56
mwhudsonif logid.isdigit() and (lastid is None or int(logid)  > lastid):10:56
lifelesshmm, worth trying for11:00
lifelessI guess different fs characteristics in ec211:00
lifelessthanks!11:00
lifelessdoes ec2land land tip or 'approved revision'11:01
=== henninge_ is now known as henninge
mwhudsontip i think11:07
mwhudson(sadly)11:07
lifeless\o/ I don't need to play silly-things11:07
lifelessmwhudson: oh, I got ec2land running outside11:07
lifelessmwhudson: nuked the paramiko check, apt-get installed boto; set pythonpath and manually made an ec2 file because its now glued into buildout and that blew up outside the vm.,11:08
mwhudsonlifeless: congrats :)11:09
lifelesshow much of that is mergable, do you think?11:09
jmlhello everyone11:16
wgrantjml: Rabble rabble not open enough rabble rabble.11:18
wgrant*ahem*. Morning.11:18
lifelesswgrant: ?11:18
wgrantlifeless: Referencing a recent Facebook update.11:19
lifelessoh right11:19
lifelessclearly true11:19
StevenKlifeless: No fair complaining about a WIP MP11:30
lifelessStevenK: sorry - saw it come in, replied.11:33
lifelessbigjools: btw, not stalking, just subscribed :)12:06
bigjoolslifeless: heh - prepare for email deluge12:07
lifelessbigjools: I have been for 6 years12:07
lifelessbigjools: I doubt you'll shock me today12:07
bigjoolsok, continue delige12:07
bigjoolsdeluge, even12:07
wgrantSpeaking of being subscribed to merge proposals...12:10
wgrantWhy do I get a rejection email from some lists.c.c address for every piece of merge proposal email I send?12:11
lifelessbecause we're muppets12:11
wgrantFor LP, that is.12:11
lifelessyes12:11
bigjoolsmatsubara is fixing that I thought - it's an artefect of the various ownerships12:11
lifelessthere is a list representing reviewers12:11
bigjoolsartefact, evem12:11
bigjoolsoh fuck I can't type today12:11
lifelessthat list has a contact address - the internal lp reviews list from when lp reviews started to get too much for the dev discussion list.12:11
wgrantAh.12:12
lifelessand that list, has a not-c.c policy on it12:12
lifelessso it goes barf12:12
lifelessjust deleting the contact address on the list should fix it.12:12
wgrantBut won't that then spam all the members?12:13
wgrantActually, I guess it would fix it.12:13
wgrantSince the people affected by the spam would be the people most empowered to fix it :P12:13
lifelessthey can manage their influx by setting a personal subscription12:13
lifelessdo no-mail, AIUI12:13
=== Ursinha-afk is now known as Ursinha
lifelesssee you guys tomorrow12:53
=== Ursinha-afk is now known as Ursinha
jtvgary_poster: I think bug 534399 has fallen into a bit of a hole.13:46
_mup_Bug #534399: Windmill breaks branch-rewrite on dev systems <Launchpad Foundations:Triaged> <https://launchpad.net/bugs/534399>13:46
gary_posterjtv: indeed, thanks for bringing it to my attention.  I'll get that back on track.13:48
jtvgary_poster: thanks for that!  Anything related to windmill or the build farm is probably a good candidate for smoothing out because the little complications there can be so devastating to our productivity.13:49
gary_posterjtv, agreed.13:49
jkakarFYI, just got this: bzr: ERROR: Invalid http response for https://xmlrpc.edge.launchpad.net/bazaar/: Unable to handle http code 502: Bad Gateway13:58
jkakarA service might need to be kicked.13:58
bigjoolsedge seems to be fairly borked14:01
wgrantjml: Regarding that email, is there not a work item missing for adding a new security level?15:05
wgrantSimply sending an email post-hoc is surely insufficient.15:05
jmlwgrant, if you think so, please say so on the thread, since others seem to disagree with you.15:06
lifelesswgrant: why?15:06
lifeless(lets talk briefly now, and either save a round trip, or generate a more targeted mail)15:06
wgrantlifeless: Because I don't want most of my applications to be able to change my authentication tokens.15:07
wgrantEven if it tells me about it later.15:07
wgrantAllowing most apps to do that is *utterly stupid*.15:07
wgrantEven if I immediately revert it, there is a window there.15:08
wgrantA significant risk that can be avoided by simply adding a new privilege level.15:08
lifelesswgrant: ok, so you mean 'when allocating an oauth key, privileged things *also* require an explicit ACK from the user when allocating permissions'15:09
lifelesslike15:09
lifelessread[/write] public15:09
lifelessread[/write] public+private15:09
lifelessread[/write] public+private+security-details15:09
wgrantread[/write] public15:09
wgrantread[/write] public+private15:09
wgrantallowed to steal my identity15:09
wgrantYes, it's pretty bad even if a read/write token gets compromised. But it's not permanent-account-hijackingly bad.15:10
wgrantThat level of risk should be minimised, surely.15:11
lifelessso I think you have a valid concern15:12
lifelessthere are usability tradeoffs here.15:12
wgrantThere is no question of this, surely.15:12
wgrantYes, there are tradeoffs.15:12
lifelessftr I don't think we *must* or *must not* do this.15:13
wgrantBut I might point out what lots of Launchpad accounts have access to.15:13
lifelessI'd like to explain why15:13
lifelesslets say we add this new privilege level for oauth.15:13
lifelessquickly will *ask for it always*15:13
lifeless(because quickly wants to be able to do this if the user selects a menu item)15:14
wgrantI was hoping it would obtain a privileged token at the start and then drop privileges later. But even if not, it's better than my scripts everywhere being privileged.15:15
lifelesssure, no question of that.15:15
lifelesswhat might be ideal is a trusted dialog saying 'you sure?'15:15
lifelessthe email is a way to ensure that no matter what, the user is told.15:16
lifelessfrankly script privilege is pretty useless in oauth today; noone knows what level to grant, apps can't request a specific level, and its not got any granularity.15:16
lifelessPersonally, given the choices of:15:17
lifeless - quickly screen scraping in the users web context15:17
lifeless - quickly using an API with an email audit notification15:17
lifeless - quickly... with extra privilege level15:17
lifelessI really want to avoid the first at all costs.15:18
lifelessI'm not sure that the third is really all that nice a way to tackle credential-and-contact management access control for scripts; *my* inclination would be to do something where silent takeover is impossible as a starting point.15:19
lifelesswgrant: but your concerns are valid; raise them. I'm too tired to be creative right now :) - but others may not be, and there is always tomorrow. I'm glad that you only see this as 'add a small extra item', it means its mostly right.15:21
lifelesswgrant: I think what I'm getting at is that privilege escalation shouldn't be unrestricted nor indefinite, but [as currently implemented] this would, and users would invariably grant the wrong access to quickly.15:26
lifelessso I'd really like to see a creative solution15:26
lifelessthat gave just enough access for just long enough and didn't add room for user error from users that *have never used LP before*15:26
lifelesssleep, take #2.15:34
=== Ursinha is now known as Ursinha-fud
jtvDoes anyone know how I fix these problems starting the Librarian layer?  http://paste.ubuntu.com/459509/  I got them after an unexpected shutdown.17:05
=== abentley is now known as abentley-lunch
=== matsubara is now known as matsubara-lunch
jtvhenninge: I just pushed the fix for test_helpers.17:26
henningejtv: cool, thanks17:26
=== salgado is now known as salgado-lunch
=== Ursinha-fud is now known as Ursinha
jmljtv, make sure all the librarian processes are dead and pid files are deleted.18:23
jtvjml: again?18:23
jtvAfter all the reboots, shutdowns, kills, make schema runs etc?18:23
jmljtv, well, that's what I'd do to try to fix the problem.18:23
jtvWell past that, I'm afraid.  :-(18:23
jmlok.18:24
jmljtv, what happens when you try to start the librarian manually?18:24
jtvIt depends.  With the twistd commandline mars gave me, it ran without complaints.18:24
mwhudsonjtv: what happens if you run ./bin/start_librarian ?18:25
jtvI tried "make start_librarian" which exits with:18:25
jtvDaemons cannot log to stdout, exiting!18:25
jtvNow trying bin/start_librarian18:25
jtvGives me the same line.18:25
jtvEither way, it takes pretty long to reach that stage for some reason.18:26
=== salgado-lunch is now known as salgado
=== matsubara-lunch is now known as matsubara
jtvjml: remarkably, none of all this shows up in /var/tmp/librarian.log18:27
jtvThat just stops where my system shut down unexpectedly Friday.18:28
mwhudsonhm18:28
jmljtv, maybe that's a config=TESTRUNNER vs config=DEVELOPMENT confusion18:28
jml(except I think I got the case inverted)18:28
jtv:)18:28
mwhudsonso basically start_librarian runs the same thing as the twistd line i gave you18:29
mwhudsonoh well18:29
mwhudsonit daemonizes i guess18:29
jtvBut the twistd line worked.18:30
jmlisn't the daemonizing thing important wrt tacrunner interactions?18:30
mwhudsonjtv: ./bin/twistd --python daemons/librarian.tac --pidfile /var/tmp/librarian.pid --prefix Librarian --logfile /var/tmp/librarian.log18:31
mwhudsonjml: but i think the librarian started by the test runner doesn't daemonize18:31
mwhudsonmay be wrong there18:31
jtvmwhudson: that returns quietly18:31
jmlmwhudson, I don't know.18:32
jmlI'm guessing that maybe there's something amiss with the way the tac runner is detecting that the librarian has indeed started.18:32
jtvmwhudson: yay!  that starts up the daemon.18:32
jtvThis time, output appears in the log.18:32
mwhudsonjtv: then you can have fun exploring the difference between what that does and what start_librarian did because i can't see that there should be any18:32
jtvmwhudson: and what's more, tests still break18:35
mwhudsonjtv: maybe it is a development/testrunner thing like jml said18:36
jtvjml, any idea how I would test that?  On "make run" things seem to start normally but references to librarian files still give me an error in the browser.18:37
jmljtv, take a working command and do LPCONFIG=testrunner working-command18:37
jmljtv, alternatively, if it's make, then "make working-command LPCONFIG=testrunner"18:37
jmlfor reasons that elude my poor little mind.18:38
jtvTrying the same tests18:38
jtvjml: I think the former should also work, but make has a feature of allowing the setting of variables in its command line like this.18:38
jtvHmm... the tests still break with LPCONFIG=testrunner18:38
jmloh, that's why I said "working command"18:39
jmlif it's "breaking command", then do LPCONFIG=development :)18:39
jtvThe absence of a "working command" was thwarting me :)18:40
jtv"make run" and tests both break.18:40
jmlI thought you had two things to compare18:40
jml<jtv> mwhudson: yay!  that starts up the daemon.18:40
jmloh now I see18:40
jmlnever mind18:40
jmlanyway, if the tests break with both configs in the same way, then it's not a config issue :)18:40
jtvWell frankly I don't...  I thought the daemon might keep running.18:40
jmlor not a config selection issue, rather.18:41
jmljtv, you've probably been through this already, but you are doing all of this testing against one of the stable branches, right?18:41
jtvThey fail in _exactly_ the same way, far as I can see.  Shouldn't the tests fail from all other sorts of horrible problems with the wrong config?18:41
jtvjml: no, though the same problems occur in both.18:42
jmljtv, which subset of the tests are you running?18:46
jtvjml: I've been running various subsets of Translations tests.18:46
jmljtv, the least I can do is try running the same subset locally against db-stable to guarantee that it is indeed a problem with your local configuration18:47
jtvFrom trunk, and now from db-stable.18:47
jtvI'm fairly sure it is, given that it started happening across an unexpected system shutdown.18:47
=== abentley-lunch is now known as abentley-
=== abentley- is now known as abentley
jtvI'm currently setting up a test branch based on db-stable.18:48
jtvjml: this produces it on a devel-based branch: ./bin/test -vv -m lp.registry -t test_milestone18:50
jtvnow trying db-stable as well18:50
jtvOh blast, that wants another "make schema"18:50
jtvjml: same result on db-stable.18:54
jtvjml: what's really strange is that now my librarian seems to be running, but I'm still getting the same error.19:09
jtvAnd still nothing from lsof -i TCP:111...  is it on the wrong port perhaps?19:09
jtvAh... the librarian I have running now listens on the ports set up in the development config, not the ones in the testrunner config.19:12
=== jtv is now known as jtv-afk
=== al-maisan is now known as almaisan-away
=== flacoste_afk is now known as flacoste
maxbHrm :-/20:15
maxbsinzui's pocket-lint throws errors on apt-installation20:15
maxbWe didn't officially de-support hardy as a LP dev platform yet, did we?20:19
=== matsubara is now known as matsubara-afk
lifelessmaxb: we're still deployed on hardy, so I sure hope not.20:29
lifelessmaxb: OTOH All the canonical staff should be on Lucid anyhow; so they'd need hardy vms...20:30
maxbsinzui's new linter only runs on python 2.620:30
lifelessheh20:30
lifelessI hope thats not in the deployment code path.20:30
maxbOnly in lp-dev-deps on lucid for now, but it breaks the ability to sync lp-deps versions across all distroseries20:33
lifelessyeah20:33
lifelessis it an external package20:33
lifeless(you imply that, I'm checking for clarity)20:34
maxbBuilt in sinzui's personal PPA, copied into the launchpad PPA20:34
lifelessis it a new custom package or a maverick backport? [I'm wondering where to file a bug on it]20:35
maxbFully custom so far20:36
rockstarmaxb, the lp-dev-deps don't get deployed to production. IS has their own packaging (AFAIK)20:45
rockstarmaxb, I was running a hardy chroot for a long time, until those packages brokedededed20:46
maxbIndeed, but lp-deps and lp-database-deps and lp-soyuz-deps build from the same source ... and AFAIK the LP PPA is still supposed to be workable on hardy20:46
=== lifeless changed the topic of #launchpad-dev to: Launchpad Development Channel | Week 4 of 10.06 | PQM is RC; devel is open | https://dev.launchpad.net/ | Get the code: https://dev.launchpad.net/Getting | On-call review in irc://irc.freenode.net/#launchpad-reviews | Use http://paste.ubuntu.com/ for pastes
=== mars changed the topic of #launchpad-dev to: Launchpad Development Channel | Week 4 of 10.06 | PQM is RC; devel is open | | Release Manager and R-C wrangler: mars | https://dev.launchpad.net/ | Get the code: https://dev.launchpad.net/Getting | On-call review in irc://irc.freenode.net/#launchpad-reviews | Use http://paste.ubuntu.com/ for pastes
abentleyrockstar, thumper: There's a power outage in my area, which means I'm tethering, which means I can't use irc.canonical.com's unorthodox port number.22:03
thumperabentley: ok22:03
rockstarabentley, does that also mean no mumbling?22:03
thumperabentley: can you mumble?22:03
abentleyrockstar, thumper: Haven't tried yet.  I do have fring on my phone if that doesn't work.22:04
thumperabentley: I'm in mumble now if you want to try22:04
=== salgado is now known as salgado-afk
=== Ursinha is now known as Ursinha-dinner

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