You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In order to download files while specifying desired file names, you must use the download_url function. However, when using download_url in concert with concurrent.future's ThreadPoolExecutor, the path to which each dataset is downloaded becomes mangled. Depending on the random order in which products are ready, the products are downloaded to a random one of the specified filenames.
Notably, using a separate session for every thread resolves the issue. However this solution is less than ideal because it creates a lot of unnecessary overhead.
Describe the bug
In order to download files while specifying desired file names, you must use the
download_url
function. However, when usingdownload_url
in concert withconcurrent.future
'sThreadPoolExecutor
, the path to which each dataset is downloaded becomes mangled. Depending on the random order in which products are ready, the products are downloaded to a random one of the specified filenames.To Reproduce
Expected behavior
The above should produce the same as:
The text was updated successfully, but these errors were encountered: