Page 2 of 2
Re: 2.3.2RC1 - PreQueue script not working anymore
Posted: December 15th, 2017, 10:15 am
by safihre
It's Windows specific, because only there we need to do a translation step between Windows-codepage and UTF8 used internally by SAB.
I can confirm on my Win10 box.
Re: 2.3.2RC1 - PreQueue script not working anymore
Posted: December 20th, 2017, 9:50 am
by safihre
Could you give this testing version a try and see if it works as expected?
https://github.com/sabnzbd/sabbuild/rel ... 2.3.2-preq
Re: 2.3.2RC1 - PreQueue script not working anymore
Posted: December 20th, 2017, 10:09 am
by jippo
I've installed the testing version and it seems if the problem is solved.
I will keep it running and see if the problem comes back.
Re: 2.3.2RC1 - PreQueue script not working anymore
Posted: January 4th, 2018, 5:46 am
by jippo
I found another faulty translation:
Code: Select all
2018-01-04 11:36:23,884::INFO::[__init__:613] Backing up \\?\D:\Incomplete\Ed_Sheeran_-_÷_Devide\__ADMIN__\Ed_Sheeran_-_÷_Devide.nzb.gz
2018-01-04 11:36:23,888::INFO::[newsunpack:2303] Running pre-queue script [u'C:\\PreQueue\\PreQueue.exe', u'Ed_Sheeran_-_\xf7_Devide', '', '', '', '', u'309588353', u'alt.binaries.mp3', '', '', '', '']
2018-01-04 11:36:25,089::INFO::[newsunpack:2313] Pre-queue script returns 0 and output=
1
Ed_Sheeran_-_��vide
music
Re: 2.3.2RC1 - PreQueue script not working anymore
Posted: January 4th, 2018, 5:56 am
by safihre
This is a Windows-specific problem.
Python 2.7 cannot really handle unicode-subprocesses. We have a work-around in place which allows us to send unicode (like the ÷) to the script, but then it's up to the script to correctly accept and parse it.
Then again there can be a mismatch between what the script send and how SAB parses it, if the encodings don't match you get stuff like this.
This should be fixed in Python 3, but we are still far away from getting that to work.