feat: add a progress bar to download

[dabrain34]

In order to track the download progress,
add a download progress bar to the terminal output.

[mdimopoulos]

Thanks for the contribution. The progress bar doesn't seem to fulfill it's purpose.
I tried it with Python 3.9 and this is an extract of the results

./fluster.py d JVT-AVC_V1

I didn't check the code in detail, as far as i understand the new functions are not aware of the size of the file that is being downloaded in advance. Therefore it is impossible to calculate progress.
Can you check please?

[dabrain34]

This is expected as the total_size is unknown from the server. I updated the PR to display ??? . Instead of the downloaded/downloaded, it will be downloaded/???

[mdimopoulos]

Hmmmm, i miss the point of adding a progress bar, ETA and percentage that don't work though.
If what you are interested in is to display the downloaded data and download rate, can you please limit the PR to include code that does exclusively that?
I would also suggest to print every 10-15 seconds instead of after every chunk to avoid saturating terminal output.

[mdimopoulos]

See previous comment

[dabrain34]

I understand your disappointment but this is due to the server limitation not to the algorithm, we cant know the size in advance except if we add it to the json file. The algorithm is correct when the total size is reported by the server.
I tried another approach with a different log in the total_size==0 case but it was not that pretty in term of UX.
Here we can have the information about the downloaded size AND the download rate, telling the activity.

I initially used /r but it was kind of weired with the multiple jobs behavior that's why I came for a new line on each update.

I can decrease the frequence of updates if you like. I would recommend 5s instead to have a feeling of download progress when its working fine, are you okay ?

[mdimopoulos]

I understand your disappointment but this is due to the server limitation not to the algorithm, we cant know the size in advance except if we add it to the json file. The algorithm is correct when the total size is reported by the server. I tried another approach with a different log in the total_size==0 case but it was not that pretty in term of UX. Here we can have the information about the downloaded size AND the download rate, telling the activity.

I initially used /r but it was kind of weired with the multiple jobs behavior that's why I came for a new line on each update.

I can decrease the frequence of updates if you like. I would recommend 5s instead to have a feeling of download progress when its working fine, are you okay ?

Thanks for the clarifications. I agree to an update internal of 5 seconds.
For the rest, please check my individual comments. With a bit of cleanup we can remove the parts of the progress bar that make no sense. If in the future we are able to calculate ETA and correct download percentages we can add the code back.

[mdimopoulos]

As a general comment, please check my previous code comments using "Files changed" tab. Under "conversation" tab it is impossible to know which line of code each one refers to.