download time missing in history for very fast/small jobs

Report & discuss bugs found in SABnzbd
Forum rules
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.
Post Reply
User avatar
jcfp
Release Testers
Release Testers
Posts: 1032
Joined: February 7th, 2008, 12:45 pm

download time missing in history for very fast/small jobs

Post by jcfp »

Downloaded a very small nzb today (664 KB), that completed fine. The history says:
Completed at 15:36:42 on Thursday 01 September 2011
Download:
Downloaded in at an average of 3.3 MB/s
Repair:
[JOBNAME] Quick Check OK
Unpack:
[JOBNAME] Unpacked 1 files/folders in 0 seconds
Category:
*
Path:
/home/jp/downloads/complete/JOBNAME
The html sources have two spaces between "in" and "at", but time taken ('0 seconds' ?) is missing, unlike in the Unpack line where it is present as expected despite also being zero. Happens in at least smpl and plush. Jobs that take somewhat longer display fine (i.e. a 10 seconds download time is shown in history view without problems). Version 0.6.8.
User avatar
sander
Release Testers
Release Testers
Posts: 9429
Joined: January 22nd, 2008, 2:22 pm

Re: download time missing in history for very fast/small job

Post by sander »

I can confirm this (running a cvs/git version of SAB pre-070):

"Size 3 KB
Downloaded in at an average of 140 KB/s"
User avatar
shypike
Administrator
Administrator
Posts: 19773
Joined: January 18th, 2008, 12:49 pm

Re: download time missing in history for very fast/small job

Post by shypike »

Fixed now in github 0.6.x branch (also fixed I18N)
Post Reply