-
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
Improved experience when linking non-downloadable content #93
Comments
Partially addressing this in #103. Will give a message like this one:
|
Hi @seanmacavaney , may I know if how does this work in Windows OS? There's no such folder as How do I symlink the dataset I downloaded myself? I keep having issues with |
I'm not very experienced in Windows. But I think you can make the missing directory by:
And the download, you can use CURL, I think:
(where XXX is the hash provided in the message and URL is the target URL) Hope this helps! |
Hi @seanmacavaney , thanks for the prompt response. By using I tried creating the symbolic link by following the instructions here.
Then I rerun the Right now I am letting the process to finish and see what errors I will encounter after trying out this symlink method. |
Apparently the software downloads the dataset (again), and this time it kinda hits itself in the foot:
Full error message:
I am guessing that this is a legitimate bug - which is what you mentioned here Right now I am using soft link in Windows. Trying to see if things are better if I use hard link. |
Tried hard link in Windows via Restarted kernel and rerun the ipynb from top, but it seems that it still tries to download from the URL again 😅 :
|
Describe the solution you'd like
Have a separate file structure for non-downloadable files. Improve linking experience by providing a command line utility to link, or by giving the command to link to the user directly.
Will require a migration of existing files and (potentially) a plan for backward compatibility.
Additional context
As suggested here: #89 (comment)
The text was updated successfully, but these errors were encountered: