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
Quite commonly errors are thrown because long paths not enabled. This is especially common on Windows computational servers, which consist of virtual machines which have long paths disabled (usually this is standard, unfortunately). What makes this more annoying, is that the virtual machines not always print the actual paths (which are long, containing all kinds of hashes and words like "SNAPVOLUMES"), so little clues are left to the source of problems.
For example, I just had a colleague where Deltaforge threw a vague "Extraction failed" error (Miniconda installer as well), and the issue in the end was resolved by enabling long paths.
Quite commonly errors are thrown because long paths not enabled. This is especially common on Windows computational servers, which consist of virtual machines which have long paths disabled (usually this is standard, unfortunately). What makes this more annoying, is that the virtual machines not always print the actual paths (which are long, containing all kinds of hashes and words like "SNAPVOLUMES"), so little clues are left to the source of problems.
For example, I just had a colleague where Deltaforge threw a vague "Extraction failed" error (Miniconda installer as well), and the issue in the end was resolved by enabling long paths.
Relevant tip how to fix (can probably link):
https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/
The text was updated successfully, but these errors were encountered: