-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Pull file with symbolic link in path doesn't work #10055
Comments
This has been introduced in 3.10.0 by @efiop commit 225814f
|
This is something that was supported accidentally. I don't think we should support symlink to a dvcfile at all. There are potential security concerns regarding that. |
Why accidentaly? There was explicit realpath everywhere in the code... Security? It's proper to understand when there is a symbolic link and explicitly support it or not with a correct support than doing undefined behavior like what's is happening now, no? |
The |
I can confirm that it was accidentally supported in the past, but we don't even know how broken it really was. @clementperon sure, we need to at least gracefully handle that, but I don't think we will support collecting .dvc files inside symlinked directories any time soon. Could you elaborate on your use case please, why do you need a symlink with .dvc files at all? Just trying to see if maybe we could propose a better solution. |
@efiop I have reorganized folder hierarchy where I store DVC files. Instead of rewriting path everywhere I have created symlinks for a smooth transition. |
Just sayin but all tools support properly symbolic link, not sure why DVC shouldn't. |
Bug Report
When I run:
dvc pull -f ./data_soft/file.dvc
Where data_soft is a symbolink link to "./data/software"
the ouput of dvc is wrong and think that the file is already pulled
When I run:
dvc pull -f ./data/software/file.dvc
the output of dvc is correct and pull the file
The text was updated successfully, but these errors were encountered: