-
Notifications
You must be signed in to change notification settings - Fork 86
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
Potential ASCII conversion regression in v0.19 #652
Comments
Hi @matthewarmand ! I have to apologize for such a slow response. I don't have a Google Music premium account at this point, so I can't test your scenario myself. As you might be aware, Tizonia was migrated to Python 3 in v0.19.0. Perhaps you could try exporting this variable inside your container. That would give us the exact location of the unicode issue.
The docker-tizonia repo has been a bit abandoned in recent times. I will try to give it some attention soon. |
No worries at all @tizonia . Yes, I'm aware of the Python 3 upgrade, and I know there were some big string changes in Python 3 vs 2. When I get some time I'll set that variable and see what I can find. I've been using docker-tizonia a lot lately because the AUR package is pretty bulky to build and I don't prefer snaps in general. I have an open PR over there for a small improvement, and I've been slowly working on building a version that uses Python 3 and v0.19.0. When I get that stable I'll open a PR for that as well |
Here's the stack trace info:
Looks like the Exception is coming from the The As a small design point, it could make sense for functions like |
thanks for the backtrace. I've looked at the code but I can't see anything obvious, or at least I have no idea how to fix it. If you know of a solution for that, would you like to submit a PR? Regarding the code duplication, yes, you are absolutely right. There is quite a bit of code that has been duplicated between the clients. The reason is that I'm not good with Python, and even less good with debian packaging of Python modules :-). So I thought about it but I did not come out with a good/easy solution to package the common code to re-use it across all the clients. So I decided to duplicate it in every client. But I'm sure it could be reused. Again, I would be more than happy to accept PRs for an attempt to do that. |
Thanks for checking it out, I'll continue investigating it as I have time and will definitely open a PR when I have a solution. That makes perfect sense. I work with python in my day job, so maybe one of these days I'll take a crack at reorganising that a bit and give you a PR for that as well |
I've noticed this SO thread: At the bottom, there is a comment that has some interesting information. Do you think something like this might be affecting you?
|
@tizonia that led me down the right path, implementing this answer in its entirety ended up working for me. With that I think I'm satisfied with my Python 3 / Tizonia 20 upgrade of Thanks a ton for the assist on that, that issue was bugging me for a long time 👏 👏 👏 |
For the curious, after the fix the output for the test case mentioned in the first comment is now:
|
Description
I've been playing around with
v0.19.0
in a fork of thedocker-tizonia
repo (find my fork linked below in Installation Method), and I've noticed an issue I suspect might be a problem with the main codebase.Steps to Reproduce
tizonia v0.19.0
, make a call which will give back non-ASCII characters. My test case for this istizonia --gmusic-unlimited-album Nivalis
, which will return the album Nivalis by the band Árstíðir.Expected behavior: In previous versions, the software is able to convert some characters and ignore others, shown below (from
v0.18.0
):Note the accentless
A
and the ignoredð
.Actual behaviour: When running
v0.19.0
, I get the error message shown below:Reproduces how often: 100% of the time when encountering these special characters in any way in the response from the remote service.
Versions
Installation Method Used
This was from a specific branch of my fork of
docker-tizonia
in which I was playing around with an upgrade of that project to Python3 and Tizonia 0.19.0.Additional Information
I wonder if its possible whether this is related to the Python3 upgrade, and if there are any notable differences in Unicode/ASCII parsing between Python 2.7 and 3.6. I haven't been able to find anything specific yet to that effect, but its possible.
It's yet still possible that its due to how I've configured the container; in which case this is more of a "how did i screw up" question.
The text was updated successfully, but these errors were encountered: