[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] broken progressbar in 1.16

From: Noël Köthe
Subject: Re: [Bug-wget] broken progressbar in 1.16
Date: Thu, 06 Nov 2014 14:32:47 +0100


Am Montag, den 03.11.2014, 10:12 +0530 schrieb Darshit Shah:

> >e-flightgear-201411   0%[                      ]   1,05M   286KB/s   eta 1h 
> >41m
> >wget: progress.c:1161: create_image: Проверочное утверждение «count_cols 
> >(bp->buffer) <= bp->width» не выполнено.
> >zsh: abort      wget -c
> >
> >(it's [Assertion "count_cols (bp->buffer) <= bp->width" failed] I think)

> This bug keeps getting more interesting and surprising. While the progress 
> bar 
> draws correctly for the original file you mentioned, the assertion fails with 
> the new ISO (live-flightgear). The funny thing is, this bug is now firing 
> based 
> on the filename of the file being downloaded, which is not something I expect 
> since the filename section of the progress bar is isolated from the rest and 
> should not create such an effect.
> I'm going to spend some more time debugging this issue.

I applied the progress bar patch on 1.16 and run into the same problem.

Connecting to fly.osdn.org.ua (fly.osdn.org.ua)||:80... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length: 1599602688 (1.5G), 1590685248 (1.5G) remaining 
Saving to: 'live-flightgear-20141101-x86_64.iso'

ar-20141101-x86_64.   0%[                      ]  12.47M  1.41MB/s             
wget: progress.c:1161: create_image: Assertion `count_cols (bp->buffer) <= 
bp->width' failed.

Looks like shipping wget with the broken progress bar because the patch
could stop downloading.
Maybe the default could be the old but stable progress bar and when the
new feature works it could be changed to the new default?



Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]