-
Notifications
You must be signed in to change notification settings - Fork 44
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
Custom .salem_cache location (if any) #198
Comments
OK yes. Salem only writes once in this folder (unpacking after download), so a quick workaround would be to trigger download before multiprocessing is used as suggested in #196. That being said, I can see that preventing the automated download can be useful and I'll work on that in the next week(s) |
currently cache_dir is hard coded here: Line 42 in d3f2e5e
|
Thanks for a quick response. Unfortunately, when batch starts multiple processes automatically at the same time, if I trigger download in all processes (which are equal), it will again be triggered at the same time and the issue will persist. However, I just thought that I should be able to try/except my way out of this conundrum when importing salem. That should be a good enough workaround. |
FYI this is a traceback I am getting.
|
Hello,
The shared .salem_cache folder is causing an issue with parallel processing on the same machine under the same user (e.g. Azure Batch), when running two tasks using salem would fail simply because two processes would attempt to create the same folder and one of them may fail. I would, of course, prefer not to download extra (especially sample!) files as requested in #196. However, if that's more complicated, the location of the folder can be controlled by an environment variable for such cases.
Thank you,
Oleh Khoma
The text was updated successfully, but these errors were encountered: