[01:33] <mgrandi> so, for some reason the 'git' git repo won't fast-import into bzr, but other smaller ones will
[01:36] <poolie> mgrandi, there have been bugs in the past where git wouldn't import because it has strange historical artifacts
[01:36] <poolie> due to buggy versions of git being used on it
[01:36] <poolie> bzr has similar things
[01:36] <poolie> i thought it was fixed
[01:36] <poolie> so you could file a bug
[01:36] <mgrandi> yeah
[01:36] <poolie> if there's not already one
[01:36] <mgrandi> i'll look, its pretty vague
[01:36] <mgrandi> just a 'keyerror'
[01:46] <mgrandi> gonna see if i can trace it out~
[03:30] <mgrandi> so it seems that the reason the fastimport is failing is because the commit a certain tag is referencing is not there...
[03:38] <mgrandi> so, not sure what bzr is supposed to do in that circumstance
[07:56] <vila> hi all
[07:58] <poolie> hi there vila
[07:59] <vila> poolie: hey !
[07:59] <jelmer_> hello
[08:00] <mgz> morning all!
[08:01] <poolie> hi there
[08:01] <poolie> let's hang out
[08:17] <jelmer_> :-(
[11:00]  * mgrandi is awake
[11:06] <mgrandi> fastimport is hard.
[11:06] <mgz> let's go shopping?
[11:07] <jelmer> heh
[11:08] <jelmer> mgrandi: what about it, specifically?
[11:08] <mgrandi> one sec , let me play the 'which tab is playing music' game
[11:10] <mgrandi> well, i tried importing the 'git' git repo again, and it failed at the end because of a key error
[11:10] <mgrandi> http://bpaste.net/show/25513/
[11:10] <mgrandi> i made it drop into pdb, it seems that there is no 'mark' for '2', so im guessing that means a tag is referring to a commit that no longer exists?
[11:11] <mgz> ...I was just going to suggest BZR_PDB
[11:12] <mgrandi> well it happened at a specific spot so i just made it drop into pdb when it caught a keyerror exception
[11:12] <mgz> and you already did it. you're almost and expert now :)
[11:12] <mgrandi> the "command" its on, is this: http://bpaste.net/show/25520/
[11:13] <mgrandi> yay!
[11:13] <mgz> okay, running my cache summary script on your dump from last night
[11:14] <mgz> ...MemoryError
[11:14] <mgrandi> wat
[11:14] <mgrandi> you ran into a memory error running the script?
[11:14] <mgz> I probably just ran out of memory :)
[11:15] <mgrandi> you should post that script, it sounds useful :o
[11:16] <mgz> it's a bit of a hack from before I had a neater way of doing it, but will put up for you to have a go
[11:18] <wgz> http://float.endofinternet.org/temp/cache_summary.py
[11:19] <wgz> will try it on this box too... after building meliae
[11:21] <wgz> ...keyerror
[11:22] <mgrandi> fun never ends!
[11:22] <mgrandi> although key error was what i was getting hwen i let it finish, maybe related?
[11:23] <mgrandi> also do you have a link to my dump? i cant login to my ftp server for some reason
[11:23] <wgz> no, just an error in how the script pokes around with the objects
[11:23] <wgz> I had a better way of doing some of this...
[11:24] <wgz> mgrandi: http://float.endofinternet.org/temp/dump.json.gz
[11:36] <wgz> okay, three bugs in short succession, should just fix meliae first
[11:37] <mgrandi> 3 bugs you just found in meliae?
[11:37] <wgz> well, I probably already filed them
[11:42] <mgrandi> hmm
[11:43] <wgz> bug 871450 is particularly annoying but probably easy to work around, every attribute has '"' stuck on the end
[11:48] <mgrandi> hmm
[11:49] <mgrandi> any easy fix we can do right now?
[11:50] <wgz> yeah, fiddle with the json import which there's also a bug for
[11:53] <mgrandi> so it just not doing it right because simplejson is not there and therefore its not using anything to encode json?
[11:57] <wgz> right.
[11:57] <wgz> okay, let's try this update...
[12:02] <mgrandi> doesn't python have a json api?
[12:02] <mgrandi> built in?
[12:03] <wgz> indeed it does these days, and based on the module that meliae is using
[12:03] <wgz> so a little import dance is enough
[12:03] <wgz> bug 871451
[12:04] <mgrandi> they both use the same api, so i can just say simplejson=json ?
[12:04] <mgrandi> import json as simplejson?
[12:11] <wgz> well, the reverse makes more sense, but that's what I did, yeah
[12:12] <wgz> now just working out some other changes
[12:12] <mgrandi> ok
[12:12] <wgz> IndexError: _LRUNode(4423523216 80B 5refs 2par) has only 5 (not 5) references
[12:12] <wgz> funny.
[12:12] <mgrandi> o.o
[12:14] <wgz> it's just the error forgetting to compensate for 0-based indexing :)
[12:16] <mgrandi> hehe
[12:18] <mgrandi> how are you supposed to run the unit tests? i can never remember the one liner to do that
[12:18] <mgrandi> for meliae (and most other python projects)
[12:19] <wgz> okay, this looks like it mostly works now, just the id type issue left...
[12:20] <jelmer> mgrandi: usually something like 'make check' or 'trial meliae'
[12:20] <wgz> mgrandi: there's a script called run_tests.py in the root dir :)
[12:21] <mgrandi> yeah, but those don't get copied to the site-packages dir =P
[12:21] <mgrandi> or don't get built, so i was wondering if i just had to copy them and then run them or something easier
[12:30] <jelmer> wgz: you're still having weekend ? :-P
[12:30] <jelmer> vila, wgz: I wonder if I could tempt one of you into doing some reviews some time this week
[12:31] <jelmer> I was about to say I would code for reviews, but that seems kindof pointless...
[12:31] <vila> jelmer: :)
[12:31] <vila> jelmer: will do my best
[12:35] <wgz> mgrandi: http://paste.ubuntu.com/892105/
[12:35] <wgz> and the script in my temp folder is updated to produce that
[12:36] <wgz> so, there's 100mb just in decompressed string caches
[12:36] <mgrandi> did you fix up meliae in the process?
[12:36] <wgz> some of it, I worked around a few things too
[12:36] <mgrandi> and i remember python using around 500 mb total when i stopped it
[12:36] <mgrandi> so 1/5th isn't good
[12:41] <mgrandi> and what you told me about the meliae test suite, this is what i was looking for =P Oct 02 04:57:14 <wgz>	can do that with... `cd meliae` `Python27\python setup.py build_ext -i` `Python27\python -m unittest meliae.tests.test_suite`
[12:43] <mgrandi> but now i sleep for another hour
[15:12] <mgz> vila vila
[15:12] <vila> something is burning ?
[15:12] <mgz> when you froze at the end of the hang out this morning
[15:13] <mgz> I was about to ask if you would help me write some test case things
[15:13] <vila> oh, hopefully ;)
[15:13] <mgz> if I commit what I have, can you look over it and make suggestions on how to solve my problems?
[15:13] <vila> sure
[15:13] <mgz> okay, will split this file up into several bits
[15:36] <Pikkachu> hey, I have a few patches for pidgin I need to maintain, and I wonder what's a good way to manage them
[15:37] <Pikkachu> people from #ubuntu-motu said it's hard
[15:37] <Pikkachu> I'm slightly thinking of something with Bazaar branches though, anyone has some experience?
[15:47] <vila> Pikkachu: the best way is to submit them upstream ;)
[15:47] <vila> Failing that, you should probably do it the debian/ubuntu way and even better the udd way
[15:48] <vila> googling for udd should give you the pointers to the existing docs
[16:01] <Pikkachu> thanks for trying
[17:30] <mgrandi> hello
[17:33] <mgz> wello
[17:34] <mgrandi> so
[17:35] <mgrandi> there are like 5 bugs related to fast import that are preventing us from actually solving said memory problem
[17:35] <mgz> well, it doesn't help, but it's not a complete stop
[17:35] <mgz> have you filed all of 'em yet?
[17:35] <mgrandi> well
[17:35] <mgrandi> one was the json thing which i think you said was filed
[17:35] <mgrandi> and might of fixed when i was in class/sleeping haha
[17:36] <mgrandi> the timezone one is filed, the memory one is filed, and im not 100% sure what is wrong with the one i ran into yesterday
[17:37] <mgrandi> from what i can tell from the git fast-import man page and the fast-import code, this bug: http://bpaste.net/show/25508/ is caused by a tag referring to a "mark", ( a commit i think) not existing anymore
[17:38] <mgrandi> i want to make sure thats right before i go reporting it
[17:39] <wgz> seems possible
[17:39] <wgz> ideally you'd just make a minimal repo that had the problem
[17:39] <wgz> but what you've got is enough for a reasonable
[17:39] <wgz> ...bug report
[17:39] <wgz> right, just going into the garden briefly
[17:40] <mgrandi> thing is i dunno how to create a repo with that problem
[17:40] <mgrandi> or rather, know enough about git
[17:41] <wgz> that was easier than it could have been
[17:41] <wgz> had not buried himself anywhere obscure
[17:41] <mgrandi> like, how do you just delete a commit? ovo
[17:42] <mgrandi> without deleting the tag that references it
[17:44] <mgrandi> or, this could like the case with the invalid timezone, that this is a git bug and fastimport just needs to be tolerant of it
[18:00] <mgrandi> so i have no idea if you know much about the fast import format, i think jelmer does though
[18:01] <jelmer> I'm reasonably familiar with it
[18:01] <jelmer> it's all relative
[18:04] <mgrandi> what is?
[18:04] <jelmer> how much somebody knows about fastimport
[18:04] <mgrandi> ah
[18:04] <mgrandi> well i just meant
[18:05] <mgrandi> i dunno if you saw the stack trace i pasted above, but basically its just saying that a mark (2) is not found in the dict of marks
[18:05] <mgrandi> marks -> bzr revision ids
[18:05] <mgrandi> im assuming that means that bzr did not find a revision with mark 2, and thats why its not there -> why it throws a key error
[18:06] <jelmer> I haven't looked at the traceback, but that sounds plausible..
[18:06] <mgrandi> http://bpaste.net/show/25508/ if you didnt see it
[18:08] <mgrandi> my question is before i look silly on the bug report, is can you do this in git? just remove commits? or is this just another possible bug with git that fastimport needs to be tolerant of
[22:29] <poolie> hi all
[22:29] <jelmer> 'mÃ¸rning poolie
[22:35] <wgz> UnicodeDecodeError
[22:37] <jelmer> wgz.decode('wgz')
[22:52] <poolie> hi jelmer, wgz
[22:52] <poolie> :)
[22:56] <wgz> poolie, am I understanding google plus correctly in that it's actually impossible to do any fixed-width/code formatting?
[22:57] <wgz> so, it's not really possible to do a post with snippets or diffs or console output such like?
[22:57] <poolie> i think that's correct