/srv/irclogs.ubuntu.com/2011/11/04/#bzr.txt

GRiDhello00:01
JoeJulianWhen an upload pack is being generated, a read is done to the file while it's still open for writing, without attempting to flush the write. Is this a bug? On a networked filesystem, this seems to result in a short read: http://fpaste.org/ziBn/00:07
pooliehi grid00:14
pooliehi JoeJulian00:14
pooliethat's interesting00:14
pooliewow that is very interesting00:15
pooliethe double read is a bit interesting too00:15
pooliei don't know if it's illegal but it's certainly unusual for a unix filesystem to require some special action to read back a file that was just written00:16
GRiDpoolie, is there someone in particular who looks after the btree_index code?00:27
poolieprobably lifeless or jam know it best00:27
GRiDok thanks. i'll talk to lifeless, then. trying to wrap up this bug i was (slowly) looking at. it's regarding the bzr search plugin too, which looks like he also wrote.00:30
poolieoh ok00:32
pooliewhich one?00:32
GRiD72085300:35
pooliebug 72085300:35
ubot5Launchpad bug 720853 in bzr search plugin "bzr crashed with RuntimeError in normpath(): maximum recursion depth exceeded while calling a Python object" [High,Confirmed] https://launchpad.net/bugs/72085300:35
GRiDhad a patch to solve the recursion, but i think it wasn't quite right and a test or two might have been failing. going to look again.00:35
pooliethat would be good to fix00:36
poolieoh i see your comment00:36
GRiDi think it actually comes down to the bzr search plugin trying to index some data it shouldn't, and it's triggering a case in the index that's not caught right now when the key is too big.00:40
poolieright00:41
lifelesso/00:46
GRiDhi lifeless :)00:47
poolieJoeJulian, can you please file a bug?00:58
poolieit seems like a gluster bug but we can possibly work around it00:58
poolieyou could try doing an fsync in there and see if it helps00:59
JoeJulianpoolie, will do. I've also opened a gluster bug.01:41
jelmergood morning Orlando :)12:56
davi_jelmer, hi, is it fine to copy .bzr/repository/git (specially the idmap) between copies of the same repository?13:20
jelmerdavi_: hi13:21
jelmerdavi_: as long as the source repository has only a subset of the revisions of the target repository, that should be fine13:21
davi_jelmer, thanks13:21
jelmerdavi_: it *should* also work if that is not the case, but I don't think that is very well tested. bug reports welcome13:21
davi_ok13:22
jelmerthere is also a bug open about having bzr-git hook into bzr's fetch to automatically copy cache data when it's fetching revisions13:22
jelmerdavi_: how's your attempts to use push going?13:24
davi_jelmer, been working fine lately :)13:27
davi_jelmer, there was one bug with pulling with fetch_tags, but i worked around it by pulling the revisions first and then pulling tags.13:28
jelmerdavi_: is that with actual push or some form of dpush?13:31
davi_jelmer, push, well, bzr pull to be precise.13:33
davi_i guess that's a slightly different code path13:33
jelmerit's indeed slightly different, but the hard bit (mapping between bzr and git) is shared between push and pull13:34
=== beuno is now known as beuno-lunch
=== daveb_ is now known as croepha
=== beuno-lunch is now known as beuno
maxbbleh, bzr-gtk build failure on oneiric beta-ppa20:35
maxbThe wonderful world of GNOME 3 migrations as applied to nautilus extensions20:35
=== yofel_ is now known as yofel

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