RSS - NZB name bugs in automated scripts
Posted: January 27th, 2010, 4:38 am
Version: 0.5.0RC3
OS: Ubuntu
Install-type: python source
Skin (if applicable): Plush
Firewall Software: None
Are you using IPV6? yes
Is the issue reproducible? yes
Hello, I've just noticed a bug linked to the new 0.5 release. I'm using RSS feeds in order to automate the DL of NZB (from binsearch).
The regexp is working fine and the different NZB are queued correctly. I'm using also a backup of the nzb using the .nzb backup folder.
At the end of each job, I execute a script which test if the dl/unpack is successful (by using the return code). If the DL is successful, then I remove the .nzb from the .nzb backup folder, if not, I move it to the nzb watched folder to be DL again a little bit later (using the $2 parameter provided by sabnzbd).
This script was working fine in 0.4 release. Since the new 0.5 release, the nzb name ($2) linked to a RSS feeds job is not reported correctly. In fact, the $2 parameter report the "real" name of the DL instead of the nzb job associated to the RSS feeds.
Here is a sample:
I want to DL through RSS feeds: "sabnzbd.zip". The RSS feeds will be executed and will find this particular DL. It will request the associated NZB to binsearch. Binsearch will prepare the NZB package containing sabnzbd.zip but will name the package: 123456.NZB
When executing the script at the end of the DL, the $2 will be equal to "sabnzbd.nzb.gz' instead of "123456.nzb.gz"
For your information, the $2 parameter is well reported during standard/manual downloads.
I hope I'm clear enough, sorry, as you noticed, English is not my native language
Do not hesitate to contact me if you need further details.
OS: Ubuntu
Install-type: python source
Skin (if applicable): Plush
Firewall Software: None
Are you using IPV6? yes
Is the issue reproducible? yes
Hello, I've just noticed a bug linked to the new 0.5 release. I'm using RSS feeds in order to automate the DL of NZB (from binsearch).
The regexp is working fine and the different NZB are queued correctly. I'm using also a backup of the nzb using the .nzb backup folder.
At the end of each job, I execute a script which test if the dl/unpack is successful (by using the return code). If the DL is successful, then I remove the .nzb from the .nzb backup folder, if not, I move it to the nzb watched folder to be DL again a little bit later (using the $2 parameter provided by sabnzbd).
This script was working fine in 0.4 release. Since the new 0.5 release, the nzb name ($2) linked to a RSS feeds job is not reported correctly. In fact, the $2 parameter report the "real" name of the DL instead of the nzb job associated to the RSS feeds.
Here is a sample:
I want to DL through RSS feeds: "sabnzbd.zip". The RSS feeds will be executed and will find this particular DL. It will request the associated NZB to binsearch. Binsearch will prepare the NZB package containing sabnzbd.zip but will name the package: 123456.NZB
When executing the script at the end of the DL, the $2 will be equal to "sabnzbd.nzb.gz' instead of "123456.nzb.gz"
For your information, the $2 parameter is well reported during standard/manual downloads.
I hope I'm clear enough, sorry, as you noticed, English is not my native language
Do not hesitate to contact me if you need further details.