-
-
Notifications
You must be signed in to change notification settings - Fork 398
pygit2 does not respect a global setting of safe.directory='*' #1156
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
Comments
Thanks to @onew4y there seems to be a workaround for
Here's how it can be done when working with
It is unclear why the global safe.directory setting of |
Related: libgit2/libgit2#6391? |
@skshetry seems related to me yes. so therefore the problem lies in libgit2 and not even in pygit2? |
@skshetry I just noticed that libgit2/libgit2#6429 was merged in libgit2, which seems to be a duplicate of libgit2/libgit2#6391 |
@skshetry I have tried pygit2==1.13.1 and confirmed this issue has gone. |
pygit2==1.13.0 So it's not a pure pygit2 issue |
We are currently working with dvc for multiple projects and the
dvc exp run
leads to a pygit2 exception on a azure machine learning instance. This leads to problems since folders on mounted drives in azure belong to userroot
whilst the working user isazureuser
The exception looks like following:A workaround for this problem should be setting the git safe.directory to ='*'.
But unfortunately this does not work with dvc resp. pygit2.
I narrowed the problem down and was able to reproduce it with pure pygit2.
Since it seems to be a pygit2 problem, I am opening the issue directly here.
FYI @efiop, @skshetry, @dmpetrov
My git config looks as follows:
With my normal git (
git version 2.36.1
) everything works great with the wildcard*
. But pygit2 seems to ignore this config.But the config seems to be loaded:
Used Versions:
pygit2 1.10.0
Any help would be really appreciated, since we can't run experiments anymore.
The text was updated successfully, but these errors were encountered: