Image is not supported as a dependency
See original GitHub issueVersion: 0.22.0+f9b30a
I ran this command:
dvc run -d 2018-12-12-13:32:56.png -o derp 'echo derp > derp'
Where the dependency is:
2018-12-12-13:32:56.png: PNG image data, 1228 x 494, 8-bit/color RGBA, non-interlaced
And I got this:
Error: Failed to run command: Dependency '2018-12-12-13:32:56.png' is not supported
Is this intended? Why we aren’t supporting images as dependencies?
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
image arm32v7/node:13.6-slim not working #1195 - GitHub
Since updating from v13.5 to v13.6 the image arm32v7/node:slim fails starting. Example: docker run -it arm32v7/node:13.6-slim results in ...
Read more >Error: Image Optimization using Next.js default loader is not ...
js' default loader is not compatible with next export . Possible solutions: Use next start to run a server, which includes the Image...
Read more >Add multi-density vector graphics - Android Developers
When you specify an SVG or PSD file, Vector Asset Studio gives immediate feedback about whether the graphics code is supported or not....
Read more >Troubleshoot Cloud Run issues
This page shows you how to resolve issues with Cloud Run. For other issues not listed below, check to see if they may...
Read more >Troubleshoot environment images - Azure Machine Learning
Conda dependencies; R; Spark. Location type not supported/Unknown location type. The following are accepted location types: Git.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
look like it’s a URL parser issue - ‘2018-12-12-13’ is considered as a schema (http, https, etc)
Turns out it was actually an issue on our side. Our regex for the local dependency was not smart enough. I will send a patch for this soon.
The
--no-exec
is a good example of that. But we also need to know which remote type to use for specific dependency/output(mind that this issue also affects outputs) beforehand. We should simply not use regex for local ones at all, and instead, use it as a default type if it doesn’t have some other supported schema.