-
Notifications
You must be signed in to change notification settings - Fork 11
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
UnicodeEncodeError when running integrity check on file with emoji #38
Comments
Are you using the latest release? Those line number don't match master or the 1.0.0 release. |
I just updated to the latest release and I am still getting this error. It is trivially reproducible for me. I just need to append to a database with a filename that has emoji. Then, check will always fail on that file.
|
I am testing whether applying
before running scorch resolves the issue. I'll keep you updated. EDIT: Unfortunately that does not work. Checking via the CLI, I'm already running in utf8 anyway even without manually specifying the exports. |
Can you please provide the filename? I can't test things otherwise. |
I created a file named |
Hi, I did some more research and I believe the issue affects Synology task scheduled functions specifically: So this doesn't appear to be a bug with scorch but rather Synology. Unfortunately, I'm now getting this error instead:
I get this error even on a backup of my database. The DB file remains unchanged, so it's not corrupt; it's the reading of the file that seems to be corrupt when the proper utf8 encoding is set. I guess i might have to start over... |
Suggestion: as this is a script that may be commonly run on a Synology, and this issue would not be detected by the end user until there is a non-ASCII filename, it might be helpful to try and detect this condition on start by purposefully writing an non-ASCII file, |
How old was the version of scorch were you using? The DB has changed from a plain text file years ago to a gzipped file. I removed the non-gzip loading in the 1.0 release because it wasn't supported in a long while. I'm sure there is a transparent work around for the encoding stuff but need to know exactly what's going on. |
I see what's going on. Thanks for the link. Let me see what I can do. |
:bump: |
I get the following error when I try to run the integrity check on a file that includes an emoji in the name. This happens even after I renamed the file, I suspect it's baked in the database now. Here is the error:
The text was updated successfully, but these errors were encountered: