Crash on saving results because of null bytes
-
Virgil Dupras
- Assigned user set to Virgil Dupras
- State changed from new to accepted
- Milestone order changed from 0 to 0
Ok, what happens is that lxml raises that error not only on null bytes, but on any character that is invalid xml (\x19 for example). Because it's possible to have filenames that contain these characters, I have to wrap the set in a try.
-
Virgil Dupras
- State changed from accepted to fixed
(from [26609a3e57af]) [#95 Crash on saving results because of null bytes state:fixed] Fixed a crash on results save when it contained invalid characters. http://bitbucket.org/hsoft/dupeguru/changeset/26609a3e57af/
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.