investigate error handlling 'dvc metrics show -a' fetch remote branch
See original GitHub issueExecuting 'dvc metrics show -a` ask for github credentials in loop. If there is an ssh key for github the command work but is really slow (more than a minute). If no remote is set for git all work without problem.
Please provide information about your setup
DVC version 0.50.1
, Installed with pip3 on ubuntu 18.04
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Error with metrics show -a - Bug Reports - Community Forum
I have been working on a small ML project for a week now. But when I tried to get all the metrics results...
Read more >Git Custom References for ML Experiments - Iterative.ai
In this post, we'll show how DVC leverages the power of Git references to track each experiment, while also completely abstracting away the...
Read more >The DataLad Handbook
the handbook will show you the principles of DataLad, and from chapter 1 ... a branch with git checkout <branch-name> to explore how...
Read more >A Beginner's Guide to DAGsHub and DVCs in Machine Learning
It also doesn't solve the issue of handling tons of data manually in a spreadsheet. ... repository. Now, let's get acquainted with DVC...
Read more >Intel® VTune™ Profiler User Guide
Get Started with Intel® VTune™ Profiler . ... Error Message: Cannot Collect GPU Hardware Metrics for the Selected GPU. Adapter.
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
Diagnose:
show-ref --verify
requires exact ref path likerefs/heads/some-branch
and we use non-qualified branch names got fromrepo.scm.list_branches()
.I suggest to never fetch anything as a side effect. We should always work with working tree and git repo state in its actual state. @efiop do we still need that
._try_fetch_from_remote()
?@Suor Indeed, after https://github.com/iterative/dvc/pull/2218 we don’t need
_try_fetch_from_remote()
at all. Thank you for investigating!