Hmmm....<br><br>I can't reproduce it anymore it seems. Weird. I rebooted into Windows to try it again, and it doesn't manifest this problem anymore.(crappy windows, i hate it when reboots solve seemingly unknown problems) However, i will paste the error from
bzr.log file in any case. Oh, and it is happening in the add phase not in the commit phase.<br><br>bzr arguments: [u'add', u'*']<br>looking for plugins in C:/Documents and Settings/alaa/Application Data/bazaar/2.0/plugins
<br>looking for plugins in C:\Program Files\Bazaar\lib\library.zip\bzrlib\plugins<br>Looking for plugins in 'C:\\Program Files\\Bazaar\\lib\\library.zip\\bzrlib\\plugins'<br>Names in archive: ['__init__.pyc', 'launchpad/__init__.pyc', 'launchpad/lp_indirect.pyc', 'launchpad/lp_registration.pyc', 'launchpad/test_lp_indirect.pyc', 'launchpad/test_register.pyc']
<br>Load plugin launchpad from zip 'C:\\Program Files\\Bazaar\\lib\\library.zip\\bzrlib\\plugins'<br>encoding stdout as sys.stdout encoding 'cp437'<br>Traceback (most recent call last):<br> File "bzrlib\commands.pyc", line 729, in run_bzr_catch_errors
<br> File "bzrlib\commands.pyc", line 691, in run_bzr<br> File "bzrlib\commands.pyc", line 389, in run_argv_aliases<br> File "bzrlib\builtins.pyc", line 372, in run<br> File "bzrlib\workingtree.pyc", line 337, in open_containing
<br> File "bzrlib\bzrdir.pyc", line 590, in open_containing<br> File "bzrlib\lazy_import.pyc", line 116, in __call__<br> File "bzrlib\transport\__init__.pyc", line 1127, in get_transport<br>
File "bzrlib\transport\__init__.pyc", line 1117, in convert_path_to_url<br> File "bzrlib\urlutils.pyc", line 273, in _win32_local_path_to_url<br> File "bzrlib\osutils.pyc", line 269, in _win32_abspath
<br>UnicodeDecodeError: 'ascii' codec can't decode byte 0xbb in position 24: ordinal not in range(128)<br><br>return code 3<br><br><br>Regards,<br>Alaa Salman<br><br><div><span class="gmail_quote">On 7/20/07,
<b class="gmail_sendername">John Arbash Meinel</b> <<a href="mailto:john@arbash-meinel.com">john@arbash-meinel.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
-----BEGIN PGP SIGNED MESSAGE-----<br>Hash: SHA1<br><br>Alaa Salman wrote:<br>> I can also confirm this bug. However, i encountered it on windows.<br>><br>> The problem was the name of a directory containing some weird
<br>> characters(by weird i mean non-ascii) So i think it was choking on it. I<br>> can provide the directory name if it would help.<br>><br>> Regards,<br>> Alaa Salman<br><br>I would be surprised to see this happen on Windows, since we go through their
<br>Unicode api. (And you shouldn't be able to create files that it cannot<br>represent in UTF-16).<br><br>So I would certainly be interested in hearing about it.<br><br>I could see having problems with terminal encoding being able to display them.
<br>But that means we have a bug in 'bzr add' that it fails if it tries to display<br>a filename it cannot represent. (It should be effectively using<br>path.encode(terminal_encoding, 'replace')). My guess is that it isn't writing
<br>to self.outf like it should.<br><br>If it is happening at commit time, then I'm not sure what is up. I know we<br>changed little bits about commit, so it is possible that the commit reporting<br>code is no longer passing it to the write file descriptor.
<br><br>John<br>=:-><br><br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.7 (Darwin)<br>Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org">http://enigmail.mozdev.org</a><br><br>iD8DBQFGn+NTJdeBCYSNAAMRAsmyAJ4812ZUodHB7XsdEq1Siend/aawqwCgnXZ2
<br>DoIX/7vOxXVN09n0yVhbAX4=<br>=/1Jz<br>-----END PGP SIGNATURE-----<br></blockquote></div><br>