-
Notifications
You must be signed in to change notification settings - Fork 86
Byte Conversion Fix #483
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
Byte Conversion Fix #483
Conversation
MostlyKIGuess
commented
Feb 5, 2025
- Fixes reading activity.info with 'b[ at the start.
|
Does look strange. Couldn't find the problem being solved. If we have any info files that start with strange content, we should change the files. |
Yeah so this was really weird as well and I am not sure why it's happening either, I will share a video on this error on the byte character being present. |
|
No video required, just describe how to reproduce. |
|
Some commands which might make the process easier: sudo ./autogen.sh;sudo make clean;sudo make;sudo make install sudo rm -rf /usr/lib/python3.13/site-packages/sugar3;sudo cp -r ./src/sugar3 /usr/lib/python3.13/site-packages/sugar3 |
|
And the contents and sha256sum of the file? |
the activity info of hello world you mean? |
|
Oh, I have that repository, but I'm asking you to take the sha256sum of the file with the path in the error message on your affected system. |
|
|
Thanks, same here. I've used Python REPL to read the activity.info file using configparser, and don't get the same result. I think you need to dig deeper into why this is happening, rather than look for |
Hmm but isn't this is where we read activity info? |
|
I've dug deeper for you.
Yet ConfigParser.read_file documentation says the iterable must yield Unicode strings, "for example files opened in text mode". So this regression is introduced by your a3f9d76 which changed I've pushed revert as 4ef8a87. |