-
-
Notifications
You must be signed in to change notification settings - Fork 150
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
Wrong error message encoding #624
Comments
Thanks, I'll take a look. |
sry, forgot about it. I'll see that later. |
Sorry but this issue seems more general. havn't got fixed. And it seems that are lots of similar encoding problems related to filename just like the PR mentioned. Also I don't know if there's a indentation at the begining of this line. |
It's likely that the error occurs in logging in various parts of the app since |
👍 Generalized to all logging, hopefully this'll fix display issues for good (in logs at least 🥲) |
In plugin page,
![image](https://user-images.githubusercontent.com/10560038/166636567-e31876df-1696-474a-92f4-6faf2a72bece.png)
![image](https://user-images.githubusercontent.com/10560038/166636636-e51a5a17-ca64-4426-b06c-b8c6ba9fd097.png)
When error occurs, it gives error with wrong encoding:
And the wrong encoding seems originates from the backend
I believe
https://github.com/Difegue/LANraragi/blob/dev/lib/LANraragi/Plugin/Metadata/Eze.pm#L78
is where this problem happens. Maybe it is due to its way to process Unicode.
Is there any way to check the way it passes path? It seems that other messages like "deleting the archive" also gives wrong path encoding.
off-topic:
Please have a look at #620 (comment) in case you missed it.
The text was updated successfully, but these errors were encountered: