Bugs: UnicodeDecodeError: invalid continuation byte

Questions and bug reports for Beta releases should be posted here.
Forum rules
Help us help you:
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
firesale
Newbie
Newbie
Posts: 21
Joined: June 6th, 2015, 4:59 am

Re: Bugs: UnicodeDecodeError: invalid continuation byte

Post by firesale »

safihre wrote:So after this happens, the interface stops updating? Or it just a one time error and then it works fine?
Nope, error is continuous as long as there's an active download. I lose connection to the new Glitter skin, which is why I've set up Plush Gold as a secondary interface. When glitter "loses connection", Plush still works. The Glitter skin becomes active again after the download is finished, though.

Image

Image
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Bugs: UnicodeDecodeError: invalid continuation byte

Post by shypike »

Anything with diacriticals in the title?
Like ėçà ?
firesale
Newbie
Newbie
Posts: 21
Joined: June 6th, 2015, 4:59 am

Re: Bugs: UnicodeDecodeError: invalid continuation byte

Post by firesale »

In the title of the NZB file? Nope. I just grabbed a random NZB to download for testing.
firesale
Newbie
Newbie
Posts: 21
Joined: June 6th, 2015, 4:59 am

Re: Bugs: UnicodeDecodeError: invalid continuation byte

Post by firesale »

firesale wrote:In the title of the NZB file? Nope. I just grabbed a random NZB to download for testing.
Image
User avatar
safihre
Administrator
Administrator
Posts: 5361
Joined: April 30th, 2015, 7:35 am
Contact:

Re: Bugs: UnicodeDecodeError: invalid continuation byte

Post by safihre »

And it only messes up the queue API call, which is weird! So it's in the difference between the queue and the history..
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
User avatar
safihre
Administrator
Administrator
Posts: 5361
Joined: April 30th, 2015, 7:35 am
Contact:

Re: Bugs: UnicodeDecodeError: invalid continuation byte

Post by safihre »

Could you PM or email ([email protected]) me the direct link so I can try it in my Windows 10 setup?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
firesale
Newbie
Newbie
Posts: 21
Joined: June 6th, 2015, 4:59 am

Re: Bugs: UnicodeDecodeError: invalid continuation byte

Post by firesale »

safihre wrote:Could you PM or email ([email protected]) me the direct link so I can try it in my Windows 10 setup?
The direct link to what?
User avatar
safihre
Administrator
Administrator
Posts: 5361
Joined: April 30th, 2015, 7:35 am
Contact:

Re: Bugs: UnicodeDecodeError: invalid continuation byte

Post by safihre »

To the NZB from nzbs.org
But now I see you say it happens for any download, right? So we still don't know what causes it..
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
firesale
Newbie
Newbie
Posts: 21
Joined: June 6th, 2015, 4:59 am

Re: Bugs: UnicodeDecodeError: invalid continuation byte

Post by firesale »

safihre wrote:To the NZB from nzbs.org
But now I see you say it happens for any download, right? So we still don't know what causes it..
Yup, I can link it if you still need it. And yes, it does happen for every download. I'm on Windows 10 and there is no issue with my other installation on a Linux server. I'm using SickRage so I have Python 2.7.10 installed as well as pywin32. No idea if that makes any difference.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Bugs: UnicodeDecodeError: invalid continuation byte

Post by shypike »

We'll add some extra logging to the next release.
That way we may find out what's going on here.
I'll contact you when we have something to test.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Bugs: UnicodeDecodeError: invalid continuation byte

Post by shypike »

firesale wrote: Nope, error is continuous as long as there's an active download. I lose connection to the new Glitter skin, which is why I've set up Plush Gold as a secondary interface. When glitter "loses connection", Plush still works. The Glitter skin becomes active again after the download is finished, though.
Can you post a complete error message (obtainable from the log file)
and the version of SABnzbd you are using?
firesale
Newbie
Newbie
Posts: 21
Joined: June 6th, 2015, 4:59 am

Re: Bugs: UnicodeDecodeError: invalid continuation byte

Post by firesale »

shypike wrote:Can you post a complete error message (obtainable from the log file)
and the version of SABnzbd you are using?
I think I posted the whole error message from the log here. Is something missing from there? I'm using 0.8.0Beta3.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Bugs: UnicodeDecodeError: invalid continuation byte

Post by shypike »

Right, I missed that. Only saw the screenshots.
Chura
Newbie
Newbie
Posts: 17
Joined: December 28th, 2012, 11:41 am

Re: Bugs: UnicodeDecodeError: invalid continuation byte

Post by Chura »

I'm on win10 as well, and tried today and still have the problem.
To be sure, I cleared my download history and it still happen, the GUI say Lost connection and I can't do anything.
The worts thing, I configured PushBullet and I get non-stop notification of HTTP Error :(.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Bugs: UnicodeDecodeError: invalid continuation byte

Post by shypike »

There will be a work-around and additional logging in the next Beta release.
It will likely solve the problem and give us a chance to find the root cause.
Post Reply