Skip to content

Add progress indication to wget #2474

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

zacuke
Copy link

@zacuke zacuke commented Jan 9, 2025

Nextcloud has a history of slow downloads and I encounter this occasionally when upgrading maib. The setup script appears to stall. Perhaps we can add this indication to wget? The giga parameter keeps it from blowing up the output length.

See here #1725 for older ticket where this was originally logged. The ticket starts with complaints that the download server is just down, which is better because then it immediately fails, but when the download starts going at 10kb/s it can take a long time to finish.

Example output when I tested this parameter combo:

ubuntu@box:~$ wget -q --show-progress --progress=dot:giga  -O /tmp/nextcloud.tmp https://download.nextcloud.com/server/releases/nextcloud-26.0.13.zip

     0K ........ ........ ........ ........ 16% 10.1M 15s
 32768K ........ ........ ........ ........ 33% 11.2M 12s
 65536K ........ ........ ........ ........ 50% 9.13M 9s
 98304K ........ ........ ........ ........ 67% 4.36M 8s
131072K ........ ........ ........ ........ 84% 1.95M 6s
163840K ........ ........ ........ ....    100%  923K=65subuntu@box:~$

Let me know I can add a new download function so it only shows up on the main nextcloud download, but it might not hurt to show progress anywhere wget occurs.

@kiekerjan
Copy link
Contributor

kiekerjan commented Feb 20, 2025

I tested this and it works. However, I think it's better to only show this for the big downloads, which in the case of MiaB is only the nextcloud download.

@zacuke
Copy link
Author

zacuke commented Feb 20, 2025

I propose we keep the change as small as possible to align best with the project's low maintenance aspect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants