-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes for unicode in transfer names #500
Conversation
@@ -15,7 +15,7 @@ git+https://github.com/artefactual-labs/agentarchives.git#egg=agentarchives | |||
git+https://github.com/artefactual-labs/mets-reader-writer#egg=metsrw | |||
mysqlclient==1.3.7 | |||
# Required by storage-service component | |||
slumber==0.6.0 | |||
slumber |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you pin the dependency to the specific version you were testing?
Holly, what's the difference between this |
When matching between the file path on disk and the currentlocation stored in the database, ensure that both are bytestrings. By default, paths coming from the database are unicode. This fixes errors in finding filenames with unicode between when they're assigned a UUID and when filename sanitization happens.
Added some related unicode work. This fixes having filenames with unicode in the name (something I thought worked already?). It was failing to match the path-on-disk with the path-in-the-db because of a unicode/str mismatch. Encode the unicode as utf8 for the match. This will probably not work with non-unicode filenames. |
We haven't run into this issue recently, even though this fix hasn't been merged. This may not be required. |
I am closing this PR, we are not going to merge it now. There is an issue that has been opened on the acceptance-tests repo to define user stories for unicode transfer names, so we know what needs to be supported. artefactual-labs/archivematica-acceptance-tests#11 |
refs #9234
Edit: