Inconsistent progress bar between download and download_all
See original GitHub issueIn a notebook, I’ve observed that EODataAccessGateway.download_all
was automatically selecting the right progress bar while EODataAccessGateway.download
wasn’t.
It’d be nice if EODataAccessGateway.download
could also select automatically the right progress bar. We could then completely remove all the from eodag.utils import NotebookProgressCallback; dag.download(product, progress_callback=NotebookProgressCallback())
from the notebooks 👍
Issue Analytics
- State:
- Created 2 years ago
- Comments:5
Top Results From Across the Web
android - Multiple downloads and update progress bar for each
I created an interface and let the activity do the download instead of the fragment. I can do multiple downloads now but am...
Read more >Downloading: Why do loading bars always get stuck on 99%?
In many system-related activities, such as file downloads, the system may hang the updating of the progress bar at 99% when a security...
Read more >Onboarding - Inconsistent progress bar · Issue #1555 - GitHub
Loading of the progress bar will be consistent (same length) with each step. Actual Incosistency persists - as seen on video video: https:// ......
Read more >Why are Progress Bars so Inconsistent? - Solidarity IT
Well, it's because progress bars work by measuring the number of individual tasks needed to complete an operation, and then comparing how many ......
Read more >How to Download All Files from a SharePoint Site?
To download all files from a SharePoint document library or folder, Simply use the “Explorer View”. Navigate to your SharePoint On-premises or SharePoint...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
for this parameter, mixing all suggestions, we can use something like:
Not providing
progress_callback
will led to the creation of a default progress bar, but giving itFalse
,None
ot other False-evaluated value will create a disabled tqdm bar.My 2cents on this parameter:
progress_callback=None
, no progress barprogress_callback="auto"
, guess progress bar