-
Notifications
You must be signed in to change notification settings - Fork 394
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
user-guide: add troubleshooting entry for dvc-exp in shallow clones #3577
Conversation
d24e508
to
0b9b295
Compare
This PR adds a troubleshooting entry with specific instructions for resolving the problem in CML, github actions, and gitlab CI/CD. It does not touch any of the command reference docs suggested in #3416 (comment), but IMO this should be sufficient to close the original issue, given that this is an edge case that is mostly specific to CI. |
Gatsby Cloud Build Reportdvc.org 🎉 Your build was successful! See the Deploy preview here. Build Details🕐 Build time: 1m PerformanceLighthouse report
|
Is this intended to be in conjunction with iterative/dvc#7791? |
Yes, this can probably be merged without waiting for the DVC PR though |
Yes, if we're going with the error handling + troubleshooting section then there's probably no need to update other docs. Wouldn't hurt either but it's kind of a deep implementation detail. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the content, all the info is great. I'm rephrasing and using tabs to clarify the alternative fixes (committing).
Co-authored-by: Restyled.io <[email protected]>
Mind reviewing when you can @dberenbaum ? Need an approval (besides mine since I took it over). Thanks |
|
||
## DVC Experiments may fail in Git shallow clones {#git-shallow} | ||
|
||
`dvc exp` commands use internal Git operations which may not work properly in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe hyperlink to more info (presumably some section on reflog things?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't explain internal Git merges anywhere, not even in Peter's blog post. Too deep
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jorgeorpinel I'm fine with it as is, but please take a look at the suggestions from @casperdcl before merging 🙏 .
It looks like iterative/dvc#6154 (comment) may be a similar issue, in which case maybe we should broaden this entry beyond |
Turns out this was unrelated. @jorgeorpinel I think this is ready to be merged once the comments from @casperdcl are resolved. |
Co-authored-by: Restyled.io <[email protected]>
Co-authored-by: Casper da Costa-Luis <[email protected]>
Co-authored-by: Restyled.io <[email protected]>
All of their commends are resolved.
comments* |
Closes #3416 (via this #3416 (comment)).
In review app: https://dvcorg-troubleshootingshallow.gtsb.io/doc/user-guide/troubleshooting#git-shallow