Re: [Monotone-devel] mtn 0.43dev: "failed to convert string from UTF-8 to ANSI_X3.4-1968"

[Derek Scherger]

2009/3/7 Jack Lloyd <address@hidden>

If I run mtn log on my nvm db with mtn 0.43-dev, rev
d24b59732a5b3293592457cba013c8f8b716a875, monotone fails with the
following error. I do not have any LANG/LC_* environmental variables
set. Also perhaps relevant: using glibc 2.9-20081201 snapshot. The
_MTN/debug file is attached. I ran the tests after building the
binary, looked OK.

mtn: fatal: error: failed to convert string from UTF-8 to ANSI_X3.4-1968: '-----------------------------------------------------------------
mtn: error: Revision: 424e1cf5155ae4473250978ae6b7e44e12775741
mtn: error: Ancestor: fc85e75bcd1af555052e4c1d48a11ff37434fec1
mtn: error: Author: address@hidden
mtn: error: Date: 2009-01-14T15:28:20
mtn: error: Branch: net.venge.monotone
mtn: error:
mtn: error: Added files:
mtn: error:         contrib/display_branches.lua
mtn: error:
mtn: error: ChangeLog:
mtn: error:
mtn: error: Added to <E2><80><98>contrib/<E2><80><99> an useful script by Richard Levitte.
mtn: error: Message-ID: <address@hidden>
mtn: error:
mtn: error: '
mtn: this is almost certainly a bug in monotone.
mtn: please send this error message, the output of 'mtn version --full',
mtn: and a description of what you were doing to address@hidden.
mtn: wrote debugging log to /home/lloyd/projects/net.venge.monotone/_MTN/debug
mtn: if reporting a bug, please include this file

I've tracked this problem down to the following change

Revision: 9c0bb9b509e63897e6a52c907988cef2d4a8fe0d
Ancestor: 1c069d8736d169b25eaa747d9a5ceabcb59e79b6
Author: address@hidden
Date: 2009-01-23T22:43:07
Branch: net.venge.monotone.stripped
ChangeLog:

Configuration cleanup part 2.
 

If anyone has time to look into the details it would probably be good to get it fixed before releasing 0.43.

Initially, I tried bisecting revs manually but that got old pretty quickly. So, instead of grinding ahead I decided to write a proper bisect command to do the work for me. What I have so far worked well enough to help find the rev above and I've committed it to net.venge.monotone.bisect for now. It needs more work, docs, tests, etc. before it'll be ready for mainline. At the moment it does not update the workspace its running from, it just spits out a suggested revision to try next as you mark things as good or bad. I ran it in one workspace (as I was developing it) and updated and tested revs in another workspace to find the problem above.

I'm going to be busy the next few days and them I'm going to be away
for a couple of weeks so I won't have a chance to look into this problem myself or finish bisect in time for the next release. I'll be
in the San Diego area though so if anyone from around there wants to get
together for a beer or lunch I'm game for that.

Cheers,
Derek