[00:57] <spiv> Good morning.
[00:59] <lifeless> allo allo
[02:33] <poolie> hi spiv
[02:34] <lifeless> hi poolie
[03:24] <lifeless> anyone know, can you do keyword lambdas in python 2.4?
[03:26] <lifeless> by which I mean
[03:26] <lifeless> lambda foo=bar:quux
[03:28] <thumper> lifeless: I've never seen that before
[03:28] <lifeless> thumper: :)
[03:28] <lifeless> thumper: I'd never had cause to do it before today.
[03:28] <thumper> lifeless: what are you trying to do?
[03:28] <lifeless> it Just Worked in python 2.6
[03:29] <lifeless> thumper: theres an interface which is (now) called with keyword parameters, that a test stubbed out with a lambda.
[03:30] <thumper> ah
[03:31] <parthm> lifeless: seems to work on 2.4 http://pastebin.com/k4X1x8pE
[03:31] <lifeless> parthm: thanks!
[03:32] <spiv> You've been able to do that with lambda since approximately forever.
[03:32] <spiv> It was particularly useful back when Python didn't have nested scopes.
[03:32] <lifeless> cool
[03:33] <poolie> hi there spiv
[03:35] <spiv> Hey poolie
[03:36] <poolie> hi spiv
[03:36] <poolie> do you have any particular thoughts on bug 582157?
[03:36] <lifeless> spiv: http://pastebin.com/fqiwpZ7S
[03:39] <spiv> poolie: I like your remarks about the two parts of the problem
[03:40] <poolie> :)
[03:40] <poolie> i was hoping you'd say i was obviously wrong and there was an easy fix :)
[03:41] <lifeless> everyone.move_to(ireland)
[03:42] <spiv> Heh.
[03:42] <lifeless> spiv: I'm not entirely sure why the is None check is needed; pqm failed two calls to stat() with it though
[03:42] <lifeless> bah
[03:42] <lifeless> 'bzr st'
[03:43] <poolie> or the IoM, 10% tax and low ping time :)
[03:44] <lifeless> spiv: or possibly I'm misreading the trace; trace shadowing a top level import is a bit annoying.
[03:44] <lifeless> Hmm, maybe we should fix that
[03:46] <spiv> poolie: so how close are we to finding that SSH is the limiting factor?
[03:47] <poolie> good question
[03:47] <poolie> we know that https from chinstrap is not much faster
[03:47] <poolie> it would be nice to try plain tcp with no encryption
[03:47] <spiv> And SSH with no encryption, perhaps.
[03:48] <poolie> if it is something at the encryption level it might be either encryption cpu overhead or added latency or windowing effect
[03:55] <poolie> mm that could be good
[03:55] <poolie> spiv, what are you up to next?
[03:58] <spiv> Firing off a merge request, then lunch ;)  Then https://bugs.edge.launchpad.net/bzr/+bug/551525, then maybe https://bugs.edge.launchpad.net/bzr/+bug/522637
[03:58] <lifeless> spiv: no comment on my pastebin ?
[03:58] <poolie> that would be nice
[03:59] <poolie> bug oh especially the latter, but both would be great
[04:00] <spiv> lifeless: the test change seems fine, there's an incomplete sentence in the docstring change, and I lack enough context to judge if that's sane and obviously correct, or nonsense ;)
[04:01] <poolie> i'm going to try Maverick on my desktop to give feedback on some kernel bugs i hit on the new mb
[04:01] <spiv> Hmm, SSH with no encryption seems hard with modern versions of SSH.  Oh well.
[04:01] <poolie> i may try ssh without encryption
[04:01] <poolie> istm the next thing is plain tcp
[04:01] <poolie> this might require sysadmin help
[04:02] <lifeless> spiv: yes
[04:02] <spiv> You could try SSH with a supposedly faster cipher at least, like blowfish.
[04:02] <lifeless> spiv: the doctstring is winging its way up, I'll iterate on it sometime this week.
[04:02] <lifeless> spiv: its only missing a single bracket.
[04:03] <spiv> That's ok, the original sentence was arguably missing a comma ;)
[04:04] <lifeless> I'd like --lsprof-file
[04:04] <lifeless> to tell the smart server to lsprof the request (and lock out other threads yada yada)
[04:05] <lifeless> and attach the callgrind format data as another part of the response.
[04:06] <poolie> ! :)
[07:12] <AfC1> Strangest thing just happened. Doing bzr push bzr+ssh:/// to a server where we don't have RSA keys and so have to type the password on console,
[07:12] <AfC1> suddenly a GTK dialog popped up asking for the target user@host's password.
[07:12] <AfC1> WTF?
[07:13] <AfC> Was that Bazaar trying to be helpful, or something else $known trying to be helpful, or a "problem"?
[07:13] <lifeless> something else probably
[07:13] <lifeless> new ubuntu version ?
[07:13] <AfC> lifeless: Lucid
[07:13] <AfC> both sides
[07:15] <AfC> It was reminiscent of the Subversion credential caching behaviour, but I wasn't expecting Bazaar to do that at all, and especially not for an SSH login password.
[07:16] <AfC> And not I can't duplicate it. If I can't figure it out, I may have to judge that the box got owned
[07:16] <lifeless> there is a gtk UI for ssh keychains
[07:16] <lifeless> its part of the gnome stack
[07:17] <AfC> Hm
[07:17] <AfC> It was just really anonymous looking. Didn't look that authoritative.
[07:17] <AfC> lifeless: (anyway, thanks)
[07:18] <lifeless> look in your process list
[07:18] <lifeless> for agent
[07:41] <vila> hi all
[07:51] <spm> hey vila!
[08:35] <poolie> hi there vila
[08:36] <vila> hey poolie
[08:39] <poolie> vila, did i tell you i replaced my broken pc with a 6-core amd?
[08:39] <poolie> it makes selftest --parallel pretty nice
[08:39] <poolie> it gets easily disk bound though
[08:39] <vila> wow, welcome to the club :-)
[08:41] <vila> poolie: python -c 'from bzrlib import osutils ; print osutils.local_concurrency()' ?
[08:41] <lifeless> 6
[08:41] <vila> 6 or 12 ?
[08:41] <vila> ok
[08:41] <poolie> probably 6, no ht
[08:42] <lifeless> AIUI amd have rather different ideas in that space
[08:42] <vila> so running the full test suite is down to what ? 6mins 8 mins ?
[09:06] <poolie> something like that
[09:10] <lifeless> hmm
[09:10] <lifeless> tomorrow
[09:10] <lifeless> remind me to land my 'delete 1/3 of the registered repo formats' patch.
[09:10] <poolie> :)
[09:10] <lifeless> its intermingled with other stuff
[09:10] <poolie> vila, is texinfo blocked, or still on your plate, or ..?
[09:11] <lifeless> but I can pull it out and do it with a prod, and I think it will be quite noticable
[09:11] <vila> still on my plate
[09:14] <lifeless> hi jkakar
[09:15] <jkakar> Hiya lifeless!
[10:06] <lifeless> memo to self, put http://www.webperformancematters.com/journal/2007/7/24/latency-bandwidth-and-response-times.html in the bzr perf bug
[17:56] <jam> vila: what's up with: https://code.edge.launchpad.net/~vila/bzr/cleanup/+merge/28315
[17:56] <jam> ?
[17:56] <jam> though you may already be gone
[17:58] <vila> jam: almost but not quite, I just need to look at it, I'm looking into .conf files needs to be locked and ran into yes-but-lock-info-use-config loop :-)
[17:58] <jam> vila: sure, just trying to drive the queue, and that is a 'tweak' entry
[17:59] <vila> jam: I'll look into them as soon as I submit this one
[18:16] <parthm> jam: hi
[18:28] <jam> hey parth
[18:29] <jam> bbiab
[18:33] <Stavros> hello
[18:33] <Stavros> is there a way for a colocated branch switch to store uncommitted changes?
[18:35] <Stavros> anyone?
[18:37] <parthm> Stavros: i haven't used colocated branches but shelve command stores uncommitted changes. maybe you can check if they work together.
[18:37] <Stavros> i can't find it anything in the docs, but it would be great if colocated branches could store changes a la shelve
[18:37] <Stavros> i could have two branches in the same dir and work on them at the same time
[18:39] <parthm> Stavros: yes. i understand the colocated concept in bzr but just haven't tried it :) ... so i don't know how well it works with shelve.
[18:39] <Stavros> as far as i know, it doesn't work at all
[18:39] <Stavros> i'll add a feature request, thanks
[18:39] <parthm> Stavros: oh. yup. in that case its probably a good idea.
[18:43] <jam> back
[18:44] <jam> Stavros: I'll also note that 'bzr-pipeline' does something similar and stores a related group of 'shelved changes' on a given branch
[18:44] <Stavros> Added: https://answers.launchpad.net/bzr-colo/+question/116044
[18:44] <jam> I don't know the details, though
[18:44] <Stavros> jam: oh, let me check that out, thanks
[18:44] <jam> abentley might be able to give more details (author of bzr-pipeline)
[18:45] <Stavros> pipeline looks great, i should be able to figure it out from the docs, thank you very much
[19:51] <lifeless> jam: I think you perhaps got tricked by the new feed-pqm
[19:51] <lifeless> jam: did you mean 'e' ?
[20:01] <jam> morning lifeless
[20:02] <jam> well, right now it is hard to test as it says "No remaining merge proposals matching status ['Approved']?"
[20:02] <jam> however, if there is a single proposal marked approved ,then running 'n' will repeatedly give you back the same proposal
[20:02] <jam> (go to next)
[20:03] <jam> lifeless: also, I submitted martin's proposal, but pqm doesn't seem to be running, nor did I get an error message about it.
[20:03] <jam> though it did go into the Queued state
[20:03] <jam> and it didn't seem to write a 'sent to pqm message'
[20:04] <lifeless> jam: run with --help
[20:04] <lifeless> theres an option to access queued ones too
[20:04] <lifeless> then use e to send it via email
[20:04] <jam> lifeless: so is 's' useless now?
[20:04] <jam> (until we get pqm reading queued messages again) ?
[20:04] <lifeless> I sent email a while back - thumper asked us to stop using queued
[20:04] <lifeless> yeah
[20:04] <jam> k
[20:05] <jam> it was certainly the obvious step
[20:05] <lifeless> yeah
[20:05] <lifeless> I would love to fix that
[20:05] <jam> and Queued gives:
[20:05] <jam>   File "c:\Python26\lib\site-packages\lazr.restfulclient-0.9.10-py2.6.egg\lazr\restfulclient\resourc
[20:05] <jam> e.py", line 852, in __getitem__
[20:05] <jam>     raise KeyError(key)
[20:05] <jam> KeyError: '--queued'
[20:05] <lifeless> dah wtf
[20:05] <jam> apparently you need to put the project name before the arguments
[20:05] <lifeless> *blink*
[20:05] <jam> nope
[20:05] <jam> that doesn't work either
[20:05] <jam> it tells me that I need to only supply 1 argument
[20:06] <jam> sigh
[20:06] <lifeless> looking
[20:06] <lifeless> the __name__ == __main__ section is borked
[20:06] <lifeless> overlapping merges I think
[20:06] <jam> yeah
[20:06] <jam> checks length and then aborts
[20:06] <jam> vs using OptionParser for it
[20:06] <jam> I'll fix it up
[20:07] <lifeless> overlapping merges
[20:07] <jam> oh, and it still uses argv[1] after parsing into args :)
[20:07] <jam> joy
[20:07] <lifeless> http://pastebin.com/Zc6PrRhy is most of it
[20:07] <lifeless> oh lol
[20:07] <lifeless> that think is going to be me
[20:08] <lifeless> the other bit I dunno what happened
[20:11] <jam> lifeless: it also doesn't work particularly well if you initially gave hydrazine readonly credentials
[20:11] <jam> :)
[20:12] <lifeless> thats surprising
[20:12] <lifeless> surely the queue command would have blown up, then ?
[20:12] <jam> well, it read it ok, but it failed with big tracebacks when I tried to set something
[20:12] <jam> sure
[20:12] <jam> it just failed in hard-to-debug ways
[20:15] <jam> lifeless: anyway, 's' is much more obvious for submit (IMO), but hey, as long as we get something working.
[21:51] <JoshBrown> I've accidentally added my email to my name in all my commits, so I'm seeing something like: 'Josh Brown josh@host.com <josh@host.com>' - is there anything I can do about this this?
[22:00] <rubbs> JoshBrown: you can try to reset your whoami by doing bzr whoami Josh Brown <josh@host.com>
[22:01] <rubbs> alternatively you can edit the "email" line in your bazaar.conf file. On linux that is located at ~/.bazaar/bazaar.conf
[22:01] <JoshBrown> rubbs: I've got it set fine now ('Josh Brown <josh@host.com>'), it's just that it looks messy in the logs.
[22:01] <rubbs> oh, of that I'm not sure.
[22:02] <rubbs> unfortunately I must go, I wish you luck in finding your answer
[22:02] <JoshBrown> rubbs: Bye.
[22:02] <rubbs> bye
[22:02] <JoshBrown> :)
[22:10] <jam> JoshBrown: you might look at using something like 'bzr rebase', but I think that tries to preserve the original author info
[22:12] <JoshBrown> jam: Thanks, I'll look into it.
[22:14] <JoshBrown> Actually it only seems to change the actual content, while preserving author info.
[22:41] <jelmer__> heh, bzr transports ftw
[22:41]  * jelmer__ runs bzr.dev pack sftp://charis.local/~/samba3.git
[22:49] <jam> jelmer__: interesting
[22:49] <jam> now does that end up doing a git pack  on the remote side?
[22:50] <jam> seems like it would be pretty inefficient, but still interesting to have it work
[22:50] <jelmer__> jam: Since it's all local it's not that inefficient
[22:50] <jam> jelmer__: well, other than the sftp protocol overhead :)
[22:50] <jelmer__> local as in LAN I mean
[22:51] <jelmer__> jam: right
[22:59] <lifeless> jelmer__: \o.