Version: 0.5.0 (Latest on site)
OS: Windows XP SP2
Install-type: Windows Installer + Windows zip of latest on top (for testing)
Firewall Software: Zone Alarm
Are you using IPV6? no
Is the issue reproducible? yes
Problems:
1) yEnc decoding failure on some inline commented articles (no, not replies!)
If a Usenet article has many comment lines at the top, before the actual yEnc encoded "gibberish", SABnzbd fails to decode on all attempts.
I get a "WARNING: None -> Unknown encoding" error. Tried several times.
Download of affected article attachments verified to be working using a standard Usenet News Client (Xnews). The attachments are not corrupt and are downloaded perfectly without any errors. It may have something to do with the number of lines the comment consists of. But this is a wild guess. Other articles that have fewer comments at the top are decoded properly, so I can't really point at any one cause for the error.
2) Purging History deletes everything
Prior to version 0.5.0 when you flushed History, SABnzbd still kept a record of the total number of bytes downloaded. This was very useful for keeping track of your download habits, e.g., for those who don't have unlimited bytes per month to download, without having to keep everything in your history pane. Since 0.5.0 this feature/bug is gone. I miss it.
yEnc Decoding Failure + History Handling Issue
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- 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.
Re: yEnc Decoding Failure + History Handling Issue
1)
Known issue. We scan 10 lines now and we don't really want to encourage bad posting.
The problem is quite rare: your's is the first complaint in years.
2)
Already filed as a ticket.
Known issue. We scan 10 lines now and we don't really want to encourage bad posting.
The problem is quite rare: your's is the first complaint in years.
2)
Already filed as a ticket.