Dear Iantcho Vassilev: Thank you for the bug report. Do you get the same error every time you run it? From the stack trace you posted, it doesn't seem to have to do with the character set of the local filesystem, since the exception occurs when trying to retrieve the directory. Why do you think it has to do with non-UTF8 encoding used on the filenames? Perhaps there is a different bug involving that.
Could you try the same thing with Tahoe-LAFS v1.8.3 instead of v1.9.0? The code shown in the stack trace changed between those two releases. (And the current code in 1.9.0 has a security bug which could allow an attacker to corrupt your directory. Except I guess you are safe since the attempt raises an exception instead of updating the directory. ;-)) Once we figure out more about when this bug happens, then we'll know if it is another manifestation of a known bug or if it is a new bug. If it is a new bug you get a gold star and if it is new information about an existing bug you get a silver star [*]. https://tahoe-lafs.org/trac/tahoe-lafs/wiki/HowToReportABug Regards, Zooko [*] That's just a joke about the way they did things in American elementary school 30 years ago. But I will totally arrange for you to get a shiny star sticker to stick onto your laptop if you want it. http://www.nextag.com/Teacher-Created-Materials-TCM1276-579933379/prices-html _______________________________________________ tahoe-dev mailing list [email protected] http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
