=== koke [n=koke@adsl229-164.unizar.es] has joined #launchpad [12:16] night all [12:17] kiko_diskless: Would you mind reviewing this privacy patch so that the Malone front page doesn't prompt for login anymore? (It doesn't do so at this moment either, but it did earlier, and it will again when another private bug gets filed) [12:18] sure [12:19] thanks, just make linting... [12:20] wow /me <3 bradb [12:20] bradb, in exchange two questions: any eta on a mountain bike for me, and how much does it cost to buy a crap car in montreal? [12:22] kiko_diskless: I haven't looked into mountain bikes yet. I'll make a note to look in the next few days. [12:22] okidok [12:22] crap car? hm, not sure. [12:23] maybe $1000-$1500 CAD [12:23] any reason why you want to buy rather than rent? [12:27] well, I was thinking of driving to NYC, but the return fee is $1000CAD [12:27] so buying might be a better option than renting [12:29] kiko_diskless: you wanna be stuck with a *car* in NYC? :) it should be pretty cheap by bus or train. [12:29] like, a few hundred bucks [12:29] yeah, that's an option. I was thinking of taking my time though [12:37] kiko_diskless: you might find something if you keep your eye on http://voir.ca/petitesannonces/annonces.aspx?iIDRubrique=801&iIDZone=1&iNumeroParution=1937 [12:38] thanks [12:42] kiko_diskless: patch sent === camilotelles [n=Camilo@20132139198.user.veloxzone.com.br] has joined #launchpad [12:58] okidok [01:09] downstairs === koke [n=koke@adsl229-164.unizar.es] has left #launchpad ["Konversation] [01:23] SteveA: hows the new lappy ? [01:31] kiko-fud: i'm not here right now, but can I merge that patch? === koke [n=koke@adsl229-164.unizar.es] has joined #launchpad === stub [n=stub@203-214-4-72.dyn.iinet.net.au] has joined #launchpad [01:37] are there any web services planned for launchpad?? === bradb [n=bradb@modemcable033.209-70-69.mc.videotron.ca] has left #launchpad [] === jamesh [n=james@203-59-207-160.dyn.iinet.net.au] has joined #launchpad === rbelem [n=rodrigo@200.246.97.164] has joined #launchpad === Seveas [n=seveas@seveas.demon.nl] has joined #launchpad [02:21] kiko-fud: Carlos seemed happy with the whitespace migration. Should I be running this on production, or do we still have more verification to do? === rbelem [n=rodrigo@200.246.97.164] has joined #launchpad [02:46] stub: There's a heinous bug in gina :-) [02:46] stub: I'm working on a fix now [02:46] itym Gina is a heinous bug [02:47] Well, there is that, but this is related to binary package priorities [02:47] we have an inverted priority map [02:47] bloody thing === Kinnison is preparing a fix now [02:50] ideally I'll need a reviewer to go over it [02:50] basically it's removing a buggered duplication and fixing up references to it [02:50] spiv: fancy an easy-peasy review? [02:53] Kinnison: sure. === Kinnison is just committing now [02:54] It'll be daniel.silverstone@canonical.com--desktop/launchpad--gina-fix--20050920--patch-2 [02:54] I'll say once it's mirrored [02:56] ** adding revision daniel.silverstone@canonical.com--desktop/launchpad--gina-fix--20050920--patch-2 [02:56] 2005-09-21 00:54:14 GMT Daniel Silverstone [02:56] Remove BinaryPackagePriority (a pointless duplication of PackagePublishingPriority) which wasn't even the same values, thusly causing endless issues with published archives. [02:56] done === spiv waits for baz [02:59] You're aware of baz's show changeset stuff yes? [02:59] I am. [02:59] Normally chinstrap is speedier than this... [02:59] Well that change is standalone so you should be able to use it === stub [n=stub@203-214-4-72.dyn.iinet.net.au] has joined #launchpad [03:10] stubby. [03:11] spiv: does that patch look okay to you? [03:17] Kinnison: Yep, looks fine. [03:17] Almost [trivial] :) [03:18] Yeah, I was gonna [trivial] it but figured it deserved a look over [03:18] it's a lot of lines for a trivial y'see [03:18] Right. [03:18] I wish more people would do what you just did :) === Kinnison grins [03:18] nearly-trivial reviews tend to be fast reviews, modulo baz. === Kinnison is gonna sit through at least the start of a gina run on dogfood, then if it looks fine, I'll send pqm a request and retire for the night === th1a [n=hoffman@pool-64-223-62-134.prov.east.verizon.net] has left #launchpad [] [03:19] *cough* because you don't have enough tests *cough* [03:19] ;) [03:20] Heh [03:21] Well, this run appears more sane [03:21] 01:21:12 WARNING Countdown 16857 binary packages [03:21] not convinced I cba. to wait through an entire binary package run [03:25] priorities look good === Kinnison bounces [03:25] merge is in pqm's queue [03:25] see you tomorrow [03:25] ciao === Kinnison -> bed. [03:27] night === Burgundavia [n=corey@S0106000000cc07fc.gv.shawcable.net] has joined #launchpad [04:08] Merge to rocketfuel@canonical.com/launchpad--devel--0: Remove BinaryPackagePriority which caused publisher vs. gina issues. r=spiv (patch-2451: daniel.silverstone@canonical.com) [04:44] Merge to rocketfuel@canonical.com/launchpad--production--1.33: Cherry pick patch-2444 into production 1.33 (patch-5: rocketfuel@canonical.com, christian.reis@canonical.com) [05:10] Merge to rocketfuel@canonical.com/launchpad--production--1.33: Cherry pick patch-2446 into production 1.33 (patch-6: guilherme.salgado@canonical.com, rocketfuel@canonical.com) === robitaille [n=robitail@d154-5-117-228.bchsia.telus.net] has joined #launchpad === hub__ [n=hub@toronto-hs-216-138-231-194.s-ip.magma.ca] has joined #launchpad [06:54] hi [06:56] hi hub__ [06:56] looks like launchpad does not like my GPG key [06:56] or that I don't like his GPG encrypt [06:57] is this a problem registering a GPG key, or signing a code of conduct? [06:57] registering [06:57] GPG reject the encrypted confirmation message [06:58] so you received the encrypted confirmation, but couldn't decrypt it? [06:59] yep [06:59] what error do you get? [06:59] adding a subkey elgmal [06:59] I think that's it [06:59] will know in a bit [07:00] note that Launchpad pulls the keys from the keyserver network, so if it is a new key (or you are making changes to it) it may take time to propagate [07:00] yep [07:00] will upload it again [07:01] so "gpg --decrypt" on the PGP blob you received doesn't give you any error messages? [07:03] bingo [07:03] that's it [07:03] sorry for the noise [07:03] enigmail decrypt without problem now [07:04] okay. Follow the URL, enter your launchpad password and it should all be set up [07:04] it will add any additional uids from the key as unvalidated emails for your account too [07:04] yep [07:04] duplicate account detected [07:04] fun [07:04] :-) [07:04] I love that [07:05] w00t [07:05] kudos to launchpad people [07:07] the merge accounts page is at https://launchpad.net/people/+requestmerge, if it didn't already point you there [07:07] it is all good [07:07] it told me, I followed it worked [07:08] now I should read the documentation [07:08] the last uid on your key looks weird: "Pedro R. Fernandez" [07:08] it is a GPG bug [07:09] I have the same key ID as someone else [07:09] I should have played lottery [07:09] http://bugzilla.mozdev.org/show_bug.cgi?id=11204 [07:10] so you do. [07:10] good thing we get you to enter in the full fingerprint :) [07:10] yep [07:10] keyid is not to be "trusted" [07:10] as there are more individuals on earth than combination [07:11] but 1 / 2^32 is still more luck that the Lotto here [07:11] hub__: Congratulations ;) [07:12] thx === _Rappy_ [n=hunt-pre@dsl-253-122.monet.no] has joined #launchpad [09:42] morning all! [09:43] I wanted to ask something, if I had a launchpad name registered, and I changed it yesterday, what isn't it reflected in my ubuntu.com email alias? [09:43] (a possible bug?) [09:50] sivang: I'm not sure if anyone except elmo can help you. [09:52] stub: ah, but as there are probably two parts to this, how do we know which of them failed? (e.g., launchpad part vs. the host system) [09:55] stub: btw, I'd like to note that the gpg importing system rocks , well, as well as every other part of launchpad [10:10] hi === Treenaks [n=martijn@messy.foodfight.org] has joined #launchpad === carlos [n=carlos@243.Red-83-47-24.pooles.rima-tde.net] has joined #launchpad [10:13] morning [10:13] hi [10:18] I'm getting timeouts and proxy errors using rosetta.. known issue? [10:19] carlos: I'm translating the Ubuntu FAQ Guide [10:19] carlos: my view is set to "untranslated only", and when I click "save and continue" it just stops.. [10:19] and after a few minutes I get: [10:19] The proxy server received an invalid response from an upstream server. [10:19] The proxy server could not handle the request POST /distros/ubuntu/breezy/+sources/ubuntu-docs/+pots/faqguide/nl/+translate. [10:19] Treenaks, could you check if it happens too with other modules? [10:20] main page works [10:20] changing profile too [10:20] Treenaks, I mean, translate another package [10:20] I can browse around [10:20] carlos: oh [10:20] carlos: let me see [10:21] thank you [10:23] same with gstreamer/show all [10:23] (waiting for the timeout/error message now) [10:24] Treenaks, URL? [10:24] https://launchpad.net/distros/ubuntu/hoary/+sources/gstreamer0.8/+pots/gstreamer-0-8/nl/+translate [10:24] (hoary!?) [10:25] hmmm [10:25] Treenaks, what do you do there? [10:25] to get the timeout [10:25] carlos: just change anything and press "Save & Continue" at the bottom [10:26] carlos: remove the "needs review" flag for example (there is only 1 on the initial page) [10:26] aw crap, my merge of last night failed with a merge conflict. [10:26] no need to change anything [10:26] carlos: oh, ok.. then just submitting creates the timeout? [10:27] yeah [10:27] Treenaks, please, could you file a bug report? [10:28] carlos: ok [10:28] I need to profile that code a bit to know what's going on... [10:28] Treenaks, thank you [10:28] carlos: what package/distribution names? === WaterSevenUb [n=WaterSev@azevedo.astro.up.pt] has joined #launchpad [10:29] Treenaks, https://launchpad.net/products/rosetta/+filebug [10:33] carlos: guess what.. [10:33] Treenaks, timeout? [10:33] carlos: I think I'm getting a timeout on bug submit [10:34] then it's not a rosetta specific problem.... [10:34] stub, ? [10:34] is there any problem? [10:34] oh it worked now [10:34] it was just very very slow [10:51] carlos: yo [10:52] stub, is the load of the server too high? [10:53] stub, Treenaks is getting many timeouts [10:56] Nothing unusual - pretty much unloaded. There is a poimport process running chewing up 20% of a CPU, but emperor still has three cpus idle. [10:56] Treenaks: Are they 'launchpad is down for maintenance' pages? [10:57] stub: no [10:57] stub: they are "Proxy error" pages [10:57] If it says 'launchpad is down for maintenance', then it is our load balancer that is giving trouble. [10:57] stub: or "System Error, please retry or file a bug" pages [10:57] ok. So I suspect that the error pages are from another proxy server between you and our data centre. [10:57] But I can't prove that ;) [10:58] stub: I'm not using a proxy on my side [10:58] once we get the request timeout stuff working, hopefully other proxies won't time out requests on us :) [10:59] Treenaks: Your ISP might have a proxy, but it would be odd for them to bother with SSL connections. [10:59] Hmm.. [10:59] stub: "my ISP" is a 100mbit ethernet cable plugged into the BGP router :) [11:00] elmo: ping [11:00] It seems to get slower on higher page numbers [11:01] stub, an HTTPS proxy?? [11:03] carlos: can be done, but doesn't make sense usually. Useful in some network topologies where clients don't have direct internet access or if you have particularly paranoid firewalling. [11:03] I don't think it can be done transparently either... === stub is pleased to discover TCP/IP is all becoming a blur from a past life [11:06] carlos: HTTPS proxies work differently to HTTP ones: you send them a "CONNECT hostname:port" command, and then you do the SSL handshake and request [11:06] still, I don't use a https-proxy.. [11:07] ok - I've found some error messages. The issue is definitely at our end. [11:07] great way to punch any protocol through a firewall if they're not configured properly :) [11:07] Treenaks: Thanks for the heads up [11:08] I'll need elmo or possibly Znarl to check out the Pound logs to determine if the issue is in Launchpad, Apache or Pound. [11:09] who can edit a teams calendar? [11:09] Burgundavia: team admins? [11:09] can it be more granular than that? [11:12] Morning === stub suspects Launchpad is taking too long to render some of the pages, and Apache is giving up waiting for the load balancer. [11:13] morning === mdke [n=matt@unaffiliated/mdke] has joined #launchpad [11:36] stub: yeah, well... [11:36] jamesh's database "takes too darn long" patch landed [11:36] so i can hook it up to the publisher [11:37] and also get that "shut down the socket if there are too many tasks queued" stuff done [11:41] dudes, we need gina run on production.... [11:47] Merge to rocketfuel@canonical.com/launchpad--devel--0: r=kiko + some [trivial] various menus landings. (patch-2452: steve.alexander@canonical.com, mpt@canonical.com) [11:47] hurrah === koke [n=koke@169.Red-217-127-113.staticIP.rima-tde.net] has joined #launchpad === koke [n=koke@169.Red-217-127-113.staticIP.rima-tde.net] has left #launchpad ["Konversation] === jinty [n=jinty@205.134.224.215] has joined #launchpad === Keybuk [n=scott@syndicate.netsplit.com] has joined #launchpad === Kinnison lunches === camilotelles [n=Camilo@20132139198.user.veloxzone.com.br] has joined #launchpad === Keybuk [n=scott@syndicate.netsplit.com] has joined #launchpad [01:52] spiv kiko-fud lifeless salgado BjornT jamesh stub -- reviewers meeting in 8 [01:53] SteveA: I won't be able to be around for this meeting, I'm in the "fix final fuckups" moment of our release [01:53] jordi: that's okay, it's a reviewers meeting === cprov [n=cprov@200-171-140-32.dsl.telesp.net.br] has joined #launchpad [01:54] SteveA: isn't the meeting at 13 UTC usually? [01:55] i thought it was 1200UTC [01:55] like the launchpad meeting [01:56] hmm, was 1600 last week [01:56] according to the logs [01:56] spiv kiko-fud lifeless salgado BjornT jamesh stub -- reviewers meeting in 65 minutes [01:57] SteveA: I mean the meeting in 3 mins? [01:57] jordi: there is no meeting in 3 mins [01:57] jordi: i was mistaken about the time [01:57] great, this is wednesday. [01:57] jordi: but, the meeting is just for the review team [01:57] there's a launchpad developers' meeting tomorrow at 1200 UTC [01:57] and you're invited to that one [01:59] Boo hiss [02:00] sounds like a singer from a redneck punk band === niemeyer [n=niemeyer@200.138.134.63] has joined #launchpad [02:02] Hiho! [02:03] hi gustavo === mpt [n=mpt@200-171-140-32.dsl.telesp.net.br] has joined #launchpad [02:05] Hello Steve [02:06] goooooooooooooooooooooooooooooood morning [02:06] hey mpt [02:07] mpt: What about "launchpadders"? [02:07] mpt: Ok.. nevermind :) [02:07] "Launchpadders" is so last month [02:08] Hehehe [02:08] mpt: what's it now then? [02:08] mpt: Launchpaddites? [02:08] mpt: Launchpaddistas? [02:08] For some reason kiko-fud addresses all his messages to the Launchpad list as "The Soyuz team at Launchpad" [02:08] though most of us aren't working on Soyuz [02:08] it's been lunchpadder for years [02:08] mpt: it's a mind-control ploy [02:09] So I always took care to rewrite that as "The Launchpadding Launchpadders at Launchpad" [02:09] mpt: once you belive you work for kiko, he can launch his evil legions of the undead^w^wlaunchpad hackers === WaterSevenUb [n=WaterSev@azevedo.astro.up.pt] has joined #launchpad === ddaa [n=ddaa@ordo.xlii.org] has joined #launchpad === salgado [n=salgado@200-171-140-32.dsl.telesp.net.br] has joined #launchpad === matsubara [n=matsubar@200-171-140-32.dsl.telesp.net.br] has joined #launchpad [02:18] BjornT, around? [02:22] hi salgado [02:23] yo BjornT. might you have some time today for us to sort out the remaining bits of that basic-voting review? [02:24] salgado: ah, sorry, forgot about that. i'll take a look at it now [02:27] cool. thank you === BjornT -> phone === segfault [i=carlos@prognus.com.br] has joined #launchpad [02:44] lifeless: what do you think of a FewerBazConflicts BOF to diagnose (and hopefully) fix the workflow of our fellow launchpadders? [02:44] could be interesting [02:44] I just have a persistent feeling that a lot of the frustration around is caused by workflow that expect that baz merge does magic. [02:45] Maybe also DemystifyingMeshMerge :) [02:45] Merge to rocketfuel@canonical.com/launchpad--devel--0: [r=spiv] Launchpad Auto Build System Scoring prototype, ordering jobs by sourcepackagerelease urgency/component and time pending in queue. (patch-2453: celso.providelo@canonical.com) [02:46] lifeless: okay, I'll sumbit to JaneW, who do you think should be lead? I think the deliverable should be documentation. [02:47] mh... that calls for jblack... [02:47] jblack: ping [02:51] Anyone fancy a quick review of two trivial, but not quite trivial patches? [02:51] (I.E. functionally they're trivial but they're more than one or two lines) [02:51] less than 400 lines? [02:52] spiv kiko-fud lifeless salgado BjornT jamesh stub -- reviewers meeting in 9 minutes [02:53] k === Treenaks [n=martijn@messy.foodfight.org] has left #launchpad [] [02:55] uhm yes [02:56] Kinnison: send them to me [02:56] Do you want patch numbers, or a diff or what? [02:56] diff + tree-id is most convenient [02:57] okies [02:57] in email? [02:57] sure [02:57] stub, ping [02:58] salgado: pong [02:59] stub, another cherrypick. would be great if you could do it before going to bed. :) [02:59] patch-2446 [02:59] want me to mail you? [02:59] SteveA: sent [02:59] salgado: Done [03:00] great! thanks stub [03:00] salgado: I asumed you forgot to email me since it seemed like a patch that needed rolling out [03:00] stub: what channel ? [03:00] Dunno [03:00] stub, indeed, I forgot. but thankfully you watch the commits list closely. :) [03:00] bah [03:01] SteveA: what channel? [03:01] canonical-meeting [03:01] kiko-fud: ping [03:01] salgado: you've got mail. it mostly the testing to make sure that assert statements are triggered that bothers me. [03:01] that is weird [03:01] the point of assert statements is that they shouldn't get triggered [03:02] exactly my point [03:02] if you're going to test for it, i think it is worth upgrading to a proper exception [03:02] you can't argue "i'm lazy, so i want a single statement" then [03:02] as you're writing a test for it [03:02] well, I'm writing tests to prove that that is not allowed [03:03] and client code should verify the pre-conditions before trying to do that [03:03] spiv: btw, are you aware of that 'python -O test.py -f --test=librarian.txt hangs? not sure if it's important or not [03:03] morning reviewers [03:04] kiko: ECHANNEL [03:04] BjornT: No, I wasn't! [03:04] BjornT: Ouch. [03:04] kiko, #canonical-meeting [03:05] old news === zyga [n=zyga@chello084010027057.chello.pl] has joined #launchpad === Kinnison prepares to upgrade his laptop to breezy using the archive re-published on mawson === Kinnison eeps [03:16] wow [03:18] wow? [03:19] yeah, sounds cool [03:20] Kinnison: be carefull... [03:20] Kinnison: I just did and it hurts :/ [03:20] zyga: what was the state of breezy @ 4am ? [03:20] Kinnison: ?/ [03:21] so, I've been using assertions a lot in database code, to catch client code not checking for pre-conditions [03:22] I also write doctests to prove you are not allowed to do some things you don't met the pre-conditions [03:23] zyga: mawson gets its archive pulse around 4am [03:23] BjornT is concerned about the tests depending on these assertions being raised [03:23] aah, zyga wouldn't know === Kinnison grins [03:23] never mind [03:24] what should I do? kiko, SteveA, BjornT? [03:24] Kinnison: I did the upgrade a minute ago and udev gave me a hard time :/ [03:24] kiko: I don't think the new exception display is as useful as I hoped. I think I need to waste more space and output the str(the_exception) + url instead of just the url [03:24] stub: which new exception display? [03:25] SteveA: Script output. [03:26] salgado: if you're writing a test to test your asserts, i think maybe these asserts are more than just that. you'll want to either put the tests in a special "here are some tests to show that we do something decent when a programmer misbehaves when using our APIs", or make them a part of the contract for those methods, documented in the docstring, and proper exceptions. [03:27] so, you have the choice of either way, but don't let it be ambiguous whether these are part of the API interface, or just you being nice to other programmers who make mistakes. [03:28] ok, so that means we should be using specific exceptions when checking for pre-conditions? [03:28] I'm sitting on the fence. More tests are good, and testing your assertions work as you hope is good. [03:28] But nobody asked me ;) === matsubara [n=matsubar@200-171-140-32.dsl.telesp.net.br] has joined #launchpad [03:29] i still think that assert statements should never be triggered, not even by tests [03:29] salgado: So one clear practical problem is that the correctness of our code, as measured by the test suite, will be wrong if your tests are depending on assert statements and we run with python -O. [03:30] I think it won't make any difference using specific exceptions in these cases, as the pre-conditions are pretty clear in the docstrings. if you don't check for them, it's your fault and you should get an exception that's not meant to be caught (AssertionError) === lamont [n=lamont@dhcp-sn38-07.hrz.uni-oldenburg.de] has joined #launchpad [03:30] I think I'm with Steve: if they're worth testing, explicitly raise rather than assert. [03:30] well, I guess everything in database code is worth testing, no? [03:31] I don't believe in arguments mentioning -O. The only people who use it don't know what it does. [03:31] stub, +1 [03:31] stub: It's a bit of a weak argument I admit. Perhaps "practical" was too strong a word to use :) === Hieronymus [n=jeroen@cp413115-a.tilbu1.nb.home.nl] has joined #launchpad [03:31] SteveA: yeah, sorry. I thought today was Thursday. [03:31] Indeed, having tests fail if you run them could be a good thing since the code isn't designed to work with it ;) [03:32] I'd almost be happier if we had "try: assert False:\nexcept AssertionError: pass\nelse: print 'LP is not python -O safe.'; sys.exit()" ;) [03:32] okay, we're never going to use -O on launchpad, without some serious cleanup work anyway. [03:32] spiv: sure, add that. [03:32] We should have a test for that ;) [03:33] salgado: keep the asserts, keep the tests, but make sure these tests are not in the general flow of documentation, but are classified as "testing asserts to catch faulty preconditions" or suchlike. [03:34] everyone vaguely satisfied with that? [03:34] i'd be happier if the tests were in a special file, to make it even clearer [03:34] It'll do for me. It feels odd, but I don't think it really matters hugely :) [03:34] Kinnison: you have review mail. [03:34] okay, I would do that. but my point here was not that I wanted only to keep the asserts. I wanted to make sure that we can use asserts to check for pre-conditions. [03:35] s/I would/I will/ [03:35] SteveA: ta [03:35] salgado: if you'd write in the docstring "if you do such-and-such it raises an AssertionError" then make sure you're not using an assert. [03:36] if you'd write in the docstring "don't do such-and-such" then use an assert [03:36] SteveA, no, I usually write "you can't use this method if you don't have this and that" [03:36] then that's fine. [03:36] use an assert [03:37] and make sure the tests of these cases are clearly separated. perhaps as doctestname-cornercase.txt or something like that [03:38] we can make the documentation work better as documentation, and put the more involved testing, and the testing of corner cases and misbehaving clients, in another file === SteveA asks for a better name [03:38] that seems pretty fine [03:40] salgado: please improve the AssertionsInLaunchpad docs, and get bjorn to review your improvements [03:40] to reflect what we've decided [03:40] sure. that's why I wanted this discussion [03:40] stub, that would be wonderful! makes me smile! === stub names Steve 'Kenneth' [03:44] i can pretend my name is "Keith" === Kinnison hands SteveA a snot-proof deckchair [03:45] i must now dig my clothes up, and go to get some belated lunch [03:46] Kinnison: are you showing sufficient gravitas? [03:47] I believe so [03:52] SteveA: was my reply convincing? === bradb [n=bradb@modemcable033.209-70-69.mc.videotron.ca] has joined #launchpad [03:54] Kinnison: yes, but it seems slightly tasteless to alter sys.argv [03:54] oh? [03:54] I guess I'm used to C where you futz with argv if you want [03:55] I'll probably end up with optparse or something eventually but since for now there's only one argument I couldn't be bothered with it [03:56] please add a comment saying "lookee here, altering sys.argv" [03:56] erm okay [03:58] Kinnison: You probably should be using canonical.launchpad.scripts.log_options [03:58] stub: whassat then? [04:00] erm... logger options. Gives you --quiet and --verbose, tied up to Pythons logging system so you use log.debug(foo) and log.error(foo) instead of print statements. [04:01] (and if you were using it, it wouldn't have been a bother to add more command line options) [04:03] stub, did you see the odd error checkwatches returns now? [04:03] BugTrackerConnectError: https://bugzilla.ubuntu.com: HTTP Error 501: Not [04:03] +Implemented [04:03] stub, I think our proxy doesn't support https, perhaps? [04:03] kiko: Don't know. [04:04] note that this is returning for bugzilla.ubuntu.com [04:04] stub: okay, so instead of thinking about optparser I'm thinking about the canonical variant. where can I find a spec about it? [04:04] which we used to be able to monitor correctly [04:04] stub, should we ping elmo and find out? [04:05] Yer.... 501 not implemented when I test manually. I guess it isn't implemented ;) [04:05] heh [04:05] bandido [04:07] stub, just turn off the proxy and at least ubuntu.com will work [04:07] o [04:07] k [04:07] kiko: Can I merge that auth problem patch? [04:07] and I'll pester james into opening outgoing https for us (think he will?) [04:07] bradb, did I read it? [04:08] kiko: I dunno. I sent it to you yesterday though. [04:08] You said you were going to review it. [04:09] ah, but saying and doing! [04:10] what's the name of our other sysadmin? [04:10] BjornT, AssertionsInLaunchpad updated. :) [04:11] stub, can I have access to the full access and error logs of the production servers? [04:12] kiko: are you going to be able to review it now, or am I going to [trivial] this merge? :) I've got four patches desparately wanting to be merged atm. [04:13] bradb, I need to eat something first, if you can wait [04:13] I'm dying [04:14] i can't wait! [04:14] salgado: If you don't mind a time delay, yes. I can copy them across to a machine you have access to. Giving out more accounts on the production servers though could be problematic as they are supposed to be secure (and more accounts == more attack vectors) [04:16]