-
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
git: failed to check if path is gitignored #6152
Comments
@gbmarc1 Hi. Could you show full |
Its already there. Last code block |
@gbmarc1 It is not full, the version is missing. E.g.
|
I modified the code block |
@gbmarc1 Thanks! Could you also show To clarify, the error happens when we try to check if a certain path is gitignored already or not. Not related to big fiels or hashes, really. |
|
@gbmarc1 are you using git worktrees or sparse checkouts? (or any other less commonly used/advanced git feature) (the error is in dulwich when it tries to load the git index, this usually means it's an unsupported git index version) |
🤦♂️I simply add a faulty index |
@gbmarc1 Were you able to confirm with other tools that it was faulty? Maybe |
I have a very similar issue. It happens as follow up issue after the problem described in #7186 . Index somehow gets broken. And it is unclear why, because a very similar workflow was working fine in the same settings.
Although
DVC doctor
|
@agrizzli are you using git worktrees or sparse checkout? Could you please run |
I am not using neither git worktrees not sparse checkout. However I figured out the true reason behind my error, which seems to be different to #7186. I was using some old dependency that has not received new outputs anymore. First, I was using for some stage1:
...
outs:
- path/to/store/big/model/
cache: false
stage2:
...
deps:
- path/to/store/big/model/ And later I removed the mentioning of the first The link to gbmarc1 is that I also used big binaries, but is was not the true reason, I guess. However, corresponding file is neither listed in any The traceback, which is only similar to #7186 in the final error message is the following: traceback.txt. The failure happens after the stage named |
Bug Report
Description
Repro fails at then end when calculating a hash for an output for both
dvc repro
anddvc exp
. I am not even sure the dvc.lock is updated appropriately.Reproduce
dvc repro train
Error stack Trace:
ls -al src/${projectName}/artifacts
:cat dvc.lock
:Expected
DVC should not fail and update the
dvc.lock
file.Environment information
Output of
dvc doctor
:Additional Information (if any):
The text was updated successfully, but these errors were encountered: