-
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
import/get: improve message when we try to re-import an artifact #2710
Comments
@shcheklein , do you have an example? |
@MrOutis will do an example 👍 , should be quick and easy |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I would like to work on this issue |
Can't reproduce this issue @shcheklein |
@shcheklein We could totally import recursive outs as well, it just requires some refactoring. But let's forbid it for now, until we get a request for that. @kiranvinodcgs Sure! So to clarify, to fix this you need to put a check here https://github.com/iterative/dvc/blob/0.66.3/dvc/dependency/repo.py#L75 , that would look something like:
|
@kurianbenoy Indeed, the script provided by @shcheklein doesn't work. Here is a modified script:
|
@kurianbenoy @efiop sorry, guys! 🙏 will be more careful next time! |
If we are to push a model registry use case and to lesser extend a data registry one we might want to make it work actually. |
Closing as irrelevant since we now support chained imports. Feel free to reopen if I misunderstood. |
We need to check (and fail gracefully?) if someone tries to do import/get of an output from the imported stage.
Example:
outputs:
which is ugly and technically correct but can improved to warn that we are trying to re-import imported output which will always fail since we don't cache imports.
The text was updated successfully, but these errors were encountered: